At work, it's finally quiet enough to start (re)rolling out our jenkins staging environment.
Our unmanaged puppet server exploded, so the obvious choice is bringing it back up.
But, the exploded puppet server didn't have any config management information associated with it. Being the config management server in an unmanaged environment, I didn't know which OS variant and what configuration details. Too much irony: to bring puppet back up, I needed puppet for the config management server. And all I had were partial backups.
(╯°□°)╯︵ ┻━┻
Start over. Since down the road I need improved windows support, and the python-based config management tools (fabric, ansible) are variants of 'run some ssh commands on the target' (Windows, Y U NO SSH?), I figured Chef had enough traction to make it worth while. Lots of new improvements.
My plan?
- Spin up chef server in debian stable
- Spin up dev VM(s) in Vagrant that match my deploy environment
- Work with chef provisioning until I can replicate my current environment base.
- Fork configs for dev, staging, and production.
How's that going?
