On Tue, Jul 10, 2012 at 1:35 AM, Edison Su <edison...@citrix.com> wrote: > > On Jul 9, 2012, at 8:32 PM, "Chip Childers" <chip.child...@sungard.com> wrote: > >> On Mon, Jul 9, 2012 at 9:28 PM, Edison Su <edison...@citrix.com> wrote: >>> The known stuffs left are: >>> 1. Need to automate CloudStack management server installation. We need a >>> preinstalled CloudStack mgt server in DevCloud, for ordinary user. The main >>> issue is that on master branch, DEB build is broken, and mgt server doesn't >>> work on Ubuntu 12.04(such as tomcat6.conf is changed, some jar files are >>> changed, not include in the class path etc). I manually hacked the DEB >>> build and then changed a lot of files to get it work. >> >> That one sounds messy... Is there a reason that you started with >> 12.04 as the OS? Does Fedora perhaps work better for now? > > Only Ubuntu 12.04 supports Xen + xcp. Why choose Xen, not QEMU, or KVM? > 1. CloudStack has the best support for Xen for the known reason... > 2. DevCloud running in a VM, so KVM doesn't work as VirtualBox doesn't > support nested CPU virtualization. > 3. PV Xen vm will be faster than the QEMU, and lesser CPU overhead. > > If running DevCloud inside a VM, Ubuntu 12.04 is an ideal choice for now. > CloudStack supports Ubuntu 10.04, as 12.04 is already out for a while, it's > time to add the support for 12.04 now.
I'm working on the simple Vagrant configuration now, based on your image. However, the details above should probably be sorted out. Ideally, the base Vagrant box would be created from the point where you had completed the base OS install plus the Xen + xcp installs. Vagrant is most useful if it takes care of the initial installation of the software you are going to be working with. Do you happen to have: 1) steps to reach the Ubuntu + Xen + Xcp? 2) steps you took to hack together the CloudStack build / install? For point 2, are you perhaps already looking at fixing the master branch build within Ubuntu 12.04? If not, but you know the steps you generally took, I can start to look at this after the initial Vagrant work. >>> 4. Need to document or automate the VirtualBox image or ova creating >>> process, such as what's the hardware configuration for the VM, what's the >>> Port Forwarding rules we are using, etc. >> >> This is where Vagrant can help out, since one of it's main goals in >> life is to help configure the VirtualBox environment for a VM (or set >> of VMs). This includes all sorts of useful knobs. If you want to do >> the documentation, I wouldn't mind taking a shot at the vagrant >> configuration. > That will be great! If there anything I can help, feel free to email me. I'm working on the obvious bits now (again, based on a "base image" that is your already created / tweaked image). I'll send in a patch with a first pass vagrant config file when I'm done. Also, who would I talk to about being able to push this new vagrant image up into downloads.cloudstack.org once I have something working? -chip
