Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm looking for something similar to vagrant, but working with KVM. I'd like to setup a couple of machines with packages I point at using a single command, but I don't really want to write the whole script from scratch. The things which are required:

  • setting up a single network between those machines and a nat for the world
  • setting up groups of servers separately (for example I want a separate group of database-like servers and a group of app servers so that i can redeploy one of them)
  • some interaction with chef, so that I can push the right config at the beginning and spawn some machines only after another machine finished its first chef-client run
  • extensibility so that I can easily add missing functionality (I'd like a package rebuild / apt repository update as a part of the deployment)
share|improve this question

First rule of thumb with VMs (KVM or other) is that you can always treat them as normal physical machines. So chef, cobbler, puppet etc are all valid solutions for their purpose. Deploying VMs is easier than physical machines, because you have the option of creating a template of a certain generic setup, and simply clone or snapshot the existing image, turning it into a new VM.

share|improve this answer
I'm ok the low-level tools and could put a solution together myself, but I'm looking for some framework which will put those things together in one place (their generalised config, that is) – viraptor Oct 9 '11 at 23:53
I guess you'd want to look at when it finally opens up (should be by the end of the year), or at the higher end systems, like RHEV – dyasny Oct 10 '11 at 8:42
OpenStack is probably the closest you'll get, but it doesn't sound like you need any more configuration management than what Chef already gets you. You should only need to set up NAT once. – jgoldschrafe Oct 11 '11 at 15:37
@jgoldschrafe OpenStack isn't configuration management, it is APIs made of services that provide a utility computing platform for managing virtual machine images and instances. – jtimberman Nov 21 '11 at 5:56
I didn't mean to imply that it was; I was replying to viraptor's comment and question. – jgoldschrafe Nov 21 '11 at 17:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.