On Feb 1, 2012, at 8:06 PM, Nan Liu wrote:
> On Wed, Feb 1, 2012 at 4:40 PM, Dustin Little <dlit...@toyatech.net> wrote:
>> Hoping to get some insight from the community. Can puppet/mcollective/
>> facter collect/store facts about hosts that are not actually running
>> puppet? I see that custom facts can be gathered via shell scripts.
>> Might this be used to build host resources and obtain facts? Also how
>> well do puppet/mcollective/facter function when the puppet client and
>> puppet master are separated by firewalls with only http/https access?
>
> Puppet uses REST, so you can run puppet master on 443 to work around
> firewalls. However content filters might not like the self signed
> certs and block access. I've had issues with things such as websense
> in the past where exceptions have to be added depending on how much
> the environment is locked down.
Would the controlling lines of /etc/puppet/puppet.conf be the following:
[master]
# Which port puppet agent listens on.
# The default value is '8139'.
# puppetport = 8139
# The port to communicate with the report_server.
# The default value is '$masterport'.
report_port = 8140
And could both of these be set to 443 ?
--
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
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
