We need to setup publictest01 to be a puppet server and have 1-2 publictest boxes going from it. There is a new version of puppet and this needs to be tested before deployment.
Suggestion: We will need puppet 2.6.3 packaged up for installation. anybody has worked on it?
{{{ 02:40:26 < ricky> Do we really want to test puppet on publictest01? 02:40:42 < ricky> It seems kind of overboard for a simple upgrade, especially since there's no nice way to export our entire puppet configs to test there. 02:41:59 < ricky> I'd just update the server whenever it hits the repos, make sure thing breaks, then do the same with clients. 02:42:30 < ricky> The server is very easy to revert if needed (which I doubt it will be) }}}
(also, the latest version is 2.6.4)
I'm one of the puppet maintainers for Fedora/EPEL. I have a public repo on fedorapeople with the latest puppet packages. We've tried to be conservative with this update as there were a lot of changes under the hood between 0.25.x and 2.6.x. I've been soliciting feedback on the puppet-users list and #puppet on freenode since 2.6.x was in beta. The relatively few people that have responded have said the update went smoothly for them. I think it's soon time to push 2.6.4 into epel-testing. But having infrastructure test this prior to that would be very welcome.
My repository is at:
http://tmz.fedorapeople.org/repo/puppet/
There are yum repo files for Fedora and EPEL there.
Replying to [comment:1 ricky]:
{{{ 02:40:26 < ricky> Do we really want to test puppet on publictest01? 02:40:42 < ricky> It seems kind of overboard for a simple upgrade, especially since there's no nice way to export our entire puppet configs to test there. 02:41:59 < ricky> I'd just update the server whenever it hits the repos, make sure thing breaks, then do the same with clients. 02:42:30 < ricky> The server is very easy to revert if needed (which I doubt it will be) }}} (also, the latest version is 2.6.4)
Ok, thanks Ricky, I will be chatting this subject with smooge. Thanks for your advice.
Replying to [comment:3 hvivani]:
Replying to [comment:1 ricky]: {{{ 02:40:26 < ricky> Do we really want to test puppet on publictest01? 02:40:42 < ricky> It seems kind of overboard for a simple upgrade, especially since there's no nice way to export our entire puppet configs to test there. 02:41:59 < ricky> I'd just update the server whenever it hits the repos, make sure thing breaks, then do the same with clients. 02:42:30 < ricky> The server is very easy to revert if needed (which I doubt it will be) }}} (also, the latest version is 2.6.4) Ok, thanks Ricky, I will be chatting this subject with smooge. Thanks for your advice.
Thanks tmz for your contribution. I'll be in touch for any doubt.
Just FYI, I updated the packages on my fedorapeople repo today to fix an update problem with the scriptlets that could leave an older copy of puppetd/puppetmasterd running. I'm not sure what the status is with testing any updates on infrastructure, but I thought this was worth noting.
The fellow who reported the problem to me was from answers.com, where they recently updated from the current EPEL 0.25.5 packages to my 2.6.4 packages. He reports the update was pretty smooth, but with a few of the clients needing a puppetd restart after the package update (<10%).
Not to be done now.
Login to comment on this ticket.