cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <>
Subject Re: [RFC] DevCloud, an all-in-one-box CloudStack development environment
Date Tue, 10 Jul 2012 03:31:27 GMT
On Mon, Jul 9, 2012 at 9:28 PM, Edison Su <> 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?

> 2. Minor one: such as setting root password to "password", set dom0 mem to 512M

Patch submitted via reviewboard.

Any others like this?

> 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,

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

>> Two other thoughts / questions:
>> 1 - Did you consider using puppet recipes to configure the system?
>> 2 - Did you consider wrapping the configuration / setup process with
>> Vagrant?
> I thought about it before, but I am not familiar with both of these tools, so if the
community can help, that will be great!
> Based on what did, it should be doable if we move to puppet/Vagrant?

Looking at the script, absolutely.  Perhaps we can start with vagrant
at the beginning (using your existing script within the Vagrant
configuration process), and then look at shifting from the shell
provisioner type to a puppet manifest approach.  Sound reasonable?

View raw message