Puppet
\nby Andrew Shafer, works for Reductive Labs<\/p>\n
Code, Tribes, Dawn of Time, Clouds, evolution, opportunity, and triumph<\/p>\n
It’s difficult to automate the download ruby gems because the URL paths are
\nnot friendly. Isn’t it interesting that RubyForge.org uses PHP to run?<\/p>\n
Idempotence: an important property to have<\/p>\n
He likes Debian’s setup of apache. It’s easier to work with for setting up
\nmultiple sites than the way most Linux distributions do it.<\/p>\n
He showed several examples of using Puppet to install packages from gem
\nrepositories and packages.<\/p>\n
How do you test your puppet deployment code? The best he’s come up with is to
\nuse RSpec to make sure a machine is in the correct configuration, and run
\ncontinuous integration tests on it with your puppet code.<\/p>\n
The Cloud. Anyone can bring up a server for 10 cents per hour, and when you’re
\ndone, you turn it off.<\/p>\n
Conversation with the audience:<\/p>\n
Things get complicated when you’re using puppet to manage deployment to
\ndifferent distributions or even platforms. E.g. Debian has two packages for
\nsomething that is a single package on another. The only way to make sure your
\npuppet deployment works is to try it and make sure the machine is in the
\ncorrect state afterward.<\/p>\n
Does puppet help you to remove packages? Some providers purge unrequested
\npackages. It’s hard to back out a messed up install, and is easier to start
\nover with a clean slate.<\/p>\n","protected":false},"excerpt":{"rendered":"
Puppet by Andrew Shafer, works for Reductive Labs Code, Tribes, Dawn of Time, Clouds, evolution, opportunity, and triumph It’s difficult to automate the download ruby gems because the URL paths are not friendly. Isn’t it interesting that RubyForge.org uses PHP to run? Idempotence: an important property to have He likes Debian’s setup of apache. It’s … <\/p>\n