Upgrade time
19 views
Skip to first unread message
Josh Vaughn
May 28, 2014, 1:15:10 PM5/28/14
to puppet...@googlegroups.com, David Shanley, kma...@crowdcompass.com
Hello-
Its puppet upgrade time. I'm running Puppet Master 3.2.3, with newer-ish agents. I'm also deeply invested in hiera and puppetdb with postgres on the back-end. My current puppet master was laid down with a tar ball, and was installed with ruby 1.8.7.blah, running out of Nginx and Rack/Passenger. I'm looking for anybody who has attempted to run through a similar upgrade for guidance. Here is the plan I have in my head:
1. Snapshot my current puppetmaster, make an AMI and upgrade it it off to the side.
2. Upgrade puppet DB to 2.0
3. Upgrade Factor to current, everywhere
4. Upgrade Hiera
5. Upgrade puppet master to 3.6.1
6. Upgrade ruby to 2.x so everything is migrated
7. Cut DNS over to the new instance
8. Hide and/or Profit.
If this is not correct, or if there is a better way to go about this can somebody please let me know? Along with pitfalls/etc would be fantastic.
-Josh
Its puppet upgrade time. I'm running Puppet Master 3.2.3, with newer-ish agents. I'm also deeply invested in hiera and puppetdb with postgres on the back-end. My current puppet master was laid down with a tar ball, and was installed with ruby 1.8.7.blah, running out of Nginx and Rack/Passenger. I'm looking for anybody who has attempted to run through a similar upgrade for guidance. Here is the plan I have in my head:
1. Snapshot my current puppetmaster, make an AMI and upgrade it it off to the side.
2. Upgrade puppet DB to 2.0
3. Upgrade Factor to current, everywhere
4. Upgrade Hiera
5. Upgrade puppet master to 3.6.1
6. Upgrade ruby to 2.x so everything is migrated
7. Cut DNS over to the new instance
8. Hide and/or Profit.
If this is not correct, or if there is a better way to go about this can somebody please let me know? Along with pitfalls/etc would be fantastic.
-Josh
Reply all
Reply to author
Forward
0 new messages