Puppet users - Nov 2008 - best practice for keeping keeping puppet up to date?

I''m planning to use Puppet to manage a rollout of Ubuntu 8.10
workstations.

Ubuntu 8.10 comes with an Puppet 0.24.4 package.  There''s a newer one
in testing, but they still aren''t up to 0.24.6.   Not surprisingly,
even something like Testing is going to lag behind the latest stable
Puppet release.

Thus, my question: what''s the best practice on keeping puppet itself
up to date?  The real issue is obviously the clients; I know about the
advice to update the server first, but you do that once.

The options I''ve read about are ..

* Build my own packages.  (I could learn how to do this, but for right
now, I really wanted to concentrate on Puppet..)
* Use Puppet to somehow use Ruby gems to install update Puppet clients
* build Puppet from source, but then I''m not sure how you keep this up
to date on client machines.

I''m sure this is a common problem, so I''m just wondering how
others
have done it.

-- Paul

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Backport via prevu into a local repository - I recommend reprepro for  
managing a repo, as it has a plethora of documentation. Micah and Thom  
have been doing a great job keeping the debian QA up to date with  
puppet (packages.qa.debian.org)

Regards,

Aj

On 20/11/2008, at 12:14 PM, Paul Holbrook <paul.holbrook@gmail.com>  
wrote:
>
> I''m planning to use Puppet to manage a rollout of Ubuntu 8.10
> workstations.
>
> Ubuntu 8.10 comes with an Puppet 0.24.4 package.  There''s a newer
one
> in testing, but they still aren''t up to 0.24.6.   Not
surprisingly,
> even something like Testing is going to lag behind the latest stable
> Puppet release.
>
> Thus, my question: what''s the best practice on keeping puppet
itself
> up to date?  The real issue is obviously the clients; I know about the
> advice to update the server first, but you do that once.
>
> The options I''ve read about are ..
>
> * Build my own packages.  (I could learn how to do this, but for right
> now, I really wanted to concentrate on Puppet..)
> * Use Puppet to somehow use Ruby gems to install update Puppet clients
> * build Puppet from source, but then I''m not sure how you keep
this up
> to date on client machines.
>
> I''m sure this is a common problem, so I''m just wondering
how others
> have done it.
>
> -- Paul
>
> >
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

I didn''t see this at first, but the thread

http://groups.google.com/group/puppet-users/browse_thread/thread/4dc80a396448b002/5dffc5fc4abc26f0?lnk=gst&q=upgrade#5dffc5fc4abc26f0

from this mailing list also has some useful suggestions.

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---