nodes.pp on puppetmaster vs. puppet agent on puppet client

[Stuart Cracraft]

If I change nodes.pp on the PM, do I have to do an /etc/init.d/puppet restart on the puppet client

to get it to receive the changes? I.e. does it have the old manifests/modules until the restart is done?

[Rahul Khengare]

Hi Stuart, 

    You don't have to do /etc/init.d/puppet restart on client machine, whenever "puppet agent" run/ fetches the catalog from PM using latest manifests. 

Thanks, 

Rahul Khengare

NTT DATA OSS Center, Pune, India.

[Stuart Cracraft]

But it has to be activated in nodes
to fetch, no?

--
You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/xtIWjZGNDKg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/51eb51d4-75a9-4e8d-abb1-79a3610a9aed%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Peter Bukowinski]

No. An agent need not be aware of what classes are assigned to it before it contacts the puppetmaster. As long as your agent is configured to run on a regular interval, it will automatically get the latest configuration on the very next run. If you want to manually run the agent to apply those latest changes immediately, you can use 'puppet agent -t' instead of restarting the service.

--

Peter Bukowinski

On Nov 26, 2013, at 12:08 AM, Stuart Cracraft <smcra...@me.com> wrote:

But it has to be activated in nodes
to fetch, no?

On Nov 25, 2013, at 9:05 PM, Rahul Khengare <rahul...@gmail.com> wrote:

Hi Stuart, 

    You don't have to do /etc/init.d/puppet restart on client machine, whenever "puppet agent" run/ fetches the catalog from PM using latest manifests. 

Thanks, 

Rahul Kheng

[jcbollinger]

On Monday, November 25, 2013 11:16:25 PM UTC-6, Peter Bukowinski wrote:

No. An agent need not be aware of what classes are assigned to it before it contacts the puppetmaster. As long as your agent is configured to run on a regular interval, it will automatically get the latest configuration on the very next run. If you want to manually run the agent to apply those latest changes immediately, you can use 'puppet agent -t' instead of restarting the service.

And there does not need to be any node block at all for an authenticated node in order for it to sync with the master.  If there isn't one, and if there is no other way that any resources are declared for that node, then it will receive an empty catalog.  Node blocks associate declarations with specific clients (nodes) or groups thereof.  They are not a security mechanism -- that's the role of cryptographic certificates and SSL.

Supposing the usual case in which nodes' certificate requests are handled through the master, the certificate signing process must be completed, once, for each node before that node can successfully retrieve catalogs from the master.  Even that does not require the agent to be restarted if it is running in daemon mode, however.


John