On Tue, Aug 30, 2011 at 00:43, Francis GALIEGUE <[email protected]> wrote: > On Mon, Aug 29, 2011 at 19:36, Daniel Pittman <[email protected]> wrote: >> On Mon, Aug 29, 2011 at 00:51, Martin Alfke <[email protected]> wrote: >>> On 08/29/2011 09:10 AM, Francis GALIEGUE wrote: >>>> >>>> First, we want to use push from the server, not pull from the clients: >>>> is that feasible? >>> >>> Yes, that is possible. >>> The client has to run in listen mode. >>> On the master you use puppet kick <dns client name> >>> http://docs.puppetlabs.com/man/kick.html >> >> That really only triggers the client to poll the server. Out of the >> box, it isn't possible to use a server push mode, though you can fake >> it by triggering poll on demand using any number of tools. >> (MCollective, for example, is pretty awesome at doing this, and I used >> that quite frequently at my previous job.) >> >> Why do you want to do this? Perhaps there is a better way to achieve >> the outcome you are after? > > Well, we have an Apache/Tomcat setup which serves 50+ sites total, a > part of which is production and the other testing. Right now we have > tools on Apache which handles upgrades for one particular site. What > we want to do is having puppet manage all this instead.
Ah, and you want to run Puppet on the machines at the same time, to control when they get upgraded, right? If so, you don't really care if Puppet pulls configuration from the master, you just want to run it at the right time. Anything can do it, but either `puppet kick`, mcollective, or just ssh in a "for loop" would be fine. Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
