I've read up on this a bit more and I am now beginning to understand how
custom facts work. It did surprise me actually that all custom facts get
instantiated at runtime - I also understand that you can write your ruby
scripts in a way that your custom facts scripts do not necessarily need to
apply
Vaidas and Matt - thats perfect information. Yum it is for me...
Thanks for your posts!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...
Hi,
I have tried this config. One thing I have noticed is that my puppet master
is not listening on port 8081. When I put the puppet master, in my case
puppet-server1, in to /usr/share/puppet-dashboard/config/settings.yml on
the dashboard server as follows:
# Hostname of the inventory server.
in
Great - that makes sense.
How would I use multiple puppet-masters?
Thanks,
Oli
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
p
Great to hear that Jeff. Confirmed, 3.0.1 it is. Is there a bug list I can
track?
On Mon, Nov 19, 2012 at 6:53 PM, Jeff McCune wrote:
> On Fri, Nov 16, 2012 at 7:13 AM, vioilly wrote:
> > That's a another reason for me to go toward 3.0.1. I assume it is a
> stable
> > release?
>
> The long answ
This sounds like what I want. I have different production networks and I
was hoping I could have one master looking after each production network
and all masters using the 1 dashboard. Each of the masters could be their
own ca for their respective production networks which could work well. How
woul
