Puppet users - Oct 2006 - pushing updates

The Big Picture doc says:

	When configuration needs to be "pushed" to the clients, the Server
	can be asked to attempt to trigger each client to request "pull" a
	new host configuration.

How does this work?  I''ve been using ''puppetd --test''
on the clients
while building the manifest, but I''m getting close to going into
production, and I need to figure out how to kick off updates rather than
waiting for puppetd to pull them down.

Thanks,
Christian

Christian G. Warden wrote:
> The Big Picture doc says:
> 
> 	When configuration needs to be "pushed" to the clients, the
Server
> 	can be asked to attempt to trigger each client to request "pull"
a
> 	new host configuration.
> 
> How does this work?  I''ve been using ''puppetd
--test'' on the clients
> while building the manifest, but I''m getting close to going into
> production, and I need to figure out how to kick off updates rather than
> waiting for puppetd to pull them down.
There are two ways, currently.

You can send puppetd a USR1 signal via whatever mechanism you want 
(e.g., good old SSH and a for loop), or you can use puppetrun:

     puppetrun --host myhost --host otherhost --tag mytest

Puppetrun was developed for nodes stored in ldap, and if you do that 
then you can trigger whole classes of hosts, but without ldap, there''s 
no way for puppetrun to collect a list of hosts.  As the Rails 
integration matures, I am sure that Puppetrun will support triggering 
based on that database, too.