Thursday, April 02, 2009

New Whitepaper: Achieving Fully Automated Provisioning

Working with our friends at Reductive Labs, we've just finished a whitepaper called "Web Ops 2.0: Achieving Fully Automated Provisioning"(pdf).

There is a live example of our joint ControlTier and Puppet solution, naturally. However, the main point of the paper is much broader than that. What we are proposing is an outline of an open source toolchain for fully automated provisioning.

What's the criteria for "fully automated provisioning"?

That details are in the whitepaper but here's the list we came up with:
  1. Be able to automatically provision an entire environment -- from "bare-metal" to running business services -- completely from specification
  2. No direct management of individual boxes
  3. Be able to revert to a "previously known good" state at any time
  4. It’s easier to re-provision than it is to repair
  5. Anyone on your team with minimal domain specific knowledge can deploy or update an environment
Here's the proposed open source toolchain (with ControlTier and Puppet highlighted):




Read the whitepaper and let us know what you think. I imagine that we'll get some objection to either the criteria or the toolchain... but that's fine. Sparking a conversation is actually what we want.

The point of all of this is to encourage discussion on how open source provisioning tools fit together to provide real world solutions. It's all too often that we meet people looking to improve their operations but they are befuddled by all of the various open source choices that don't seem to have much relation to each other. Hopefully this paper will be a first step towards greater public discussion. Educating the public lifts all boats.

All of the content in the whitepaper is licensed under the Creative Commons (Attribution - Share Alike) license.

Update: See this post on the dev2ops.org for more information and progress on the next version

8 comments:

Anonymous said...

You have a typo in your white paper on page 6; the word should be "complementary," not "complimentary." Great and timely paper though!

Damon Edwards said...

Thanks for the heads up! It's been fixed.

Lewis said...

Excellent paper - I couldn't agree more. I was thinking about similar stuff when I wrote about CML: freeze dried IT in my blog.

Anonymous said...

Can anyone recommend the top performing Remote Desktop program for a small IT service company like mine? Does anyone use Kaseya.com or GFI.com? How do they compare to these guys I found recently: [url=http://www.n-able.com] N-able N-central remote management
[/url] ? What is your best take in cost vs performance among those three? I need a good advice please... Thanks in advance!

slideshowblob said...

Error on page 7, second bullet point:

"...diverted attention away from strategic work the would deliver higher.."

I believe it should be s/the/that/

hankoudan said...

Best blog post title of the year.Great comments all around. I like how there are a variety voices coming through.
by Air Jordan 6

fantutu said...

I think its a pretty good idea not that there aren't other sites out there that already do something similar but I think it might catch on here pretty well.Monogram Multicolor

fantutu said...

hey,this is one of the best posts that I’ve ever seen; you may include some more ideas in the same theme.Christmas gifts I’m still waiting for some interesting thoughts from your side in your next post.
louis Vuitton