jedi4ever / veewee

Easing the building of vagrant boxes
MIT License
4.29k stars 779 forks source link

Building openstack images #173

Open jedi4ever opened 12 years ago

jedi4ever commented 12 years ago

Now that veewee support creation of kvm images, it would be interesting to create openstack kvm images.

In general it seems to require:

  1. ext4
  2. fstab no UUID labels + set uec-.. label for root filesystem
  3. only 1 filesystem (no swap)
  4. cloud-init or homebrew cloud-init

We could change the templates to do 1&2 but 3 (no swap) would not be a good default. Step 4. could be done in an additional/default non-activated _openstack.sh script

Now I need to learn more about openstack

jedi4ever commented 12 years ago

maybe @dysinger would be interested in this :)

miketheman commented 12 years ago

I'd be interested in this.

anotherjesse commented 12 years ago

If you want to get an openstack environment going fast -

This installs the dashboard (django webapp), nova (virtualization), glance (image catalog) and CLI (novaclient)

You can then run exercise.sh (and read the exercise directory for how to launch a VM, interact with glance, ...)

anotherjesse commented 12 years ago

@vishvananda and @dtroyer might be interested in helping as well

jedi4ever commented 12 years ago

Great for the help!

Yeah, devstack looks great but when I would run it in a VM, I can't test KVM as that does not work in a VM? I tried and libvirt does a fallback to qemu , but that's akwardly slow in virtualbox ....

And I don't have any 'iron' left anymore :)

dysinger commented 12 years ago

We tried devstack inside vagrant last week while we were visiting Hyves. I then started messing with trying to get a bridged network setup which led me to a blog post by Patrick :)

jedi4ever commented 12 years ago

@dysinger nice :) What virtualization did you use, I'm guessing lxc ?

anotherjesse commented 12 years ago

devstack defaults to kvm but drops to qemu if the VM doesn't support hardware virt.

If you run KVM in KVM on linux 3.2 or above you get hardware virt in virt ;)

jedi4ever commented 12 years ago

So are you saying that if I have access to a kvm machine, that kvm will be working inside the vm as well?

agh commented 12 years ago

Nested virtualization. Yes indeed.

vishvananda commented 12 years ago

@dysinger devstack inside of vagrant: https://github.com/vishvananda/vagrant_devstack