On Monday, October 20, 2014 7:02:36 PM UTC-5,
[email protected] wrote:
>
> So are you saying that running puppet apply site.pp shouldn't propagate
> changes to the agents?
>
>
Yes, that is exactly what I am saying. The "puppet apply" command causes a
catalog to be compiled *by* the machine on which it runs, *for* the machine
on which it runs, and applies it *to* (only) the machine on which it runs.
To configure a different machine based on the manifests and data on your
master, you run "puppet agent" on the machine you want to configure. The
master can manage itself that way, too. The agent runs in daemon mode by
default, periodically requesting a fresh catalog from the master and
applying it. The agent can also run in one-time mode, which some people
leverage to launch it via an external scheduler such as cron.
If it runs as a daemon, the agent can be configured to listen for messages
("kicks") from the master, and to respond to them by initiating a catalog
run. It seems more in vogue, however, to use an external remote-control
framework if you want to do that. In particular, mcollective is typically
suggested for that purpose.
John
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/c865e7c6-4257-4e8b-8dfc-855f16dff82c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
