Hi Jason, At the moment, I'm investigating using devcloud2 as an option for the stratos developer environment.
I have managed to convert devcloud2 to packer and vagrant [1], but I have run into some issues, in particular a problem with xen [2]. If you have xen debugging skills and are able to suggest some things to look at for the above bug that would be really appreciated. Many thanks, Chris --- [1] https://github.com/snowch/devcloud [2] http://lists.xenproject.org/archives/html/xen-users/2014-02/msg00001.html On Fri, Jan 31, 2014 at 11:20 PM, Jason Daly <[email protected]> wrote: > Hi Chris, > > We use CloudStack quite a bit an I'd be glad to help. Feel free to email > any questions. > > Jason Daly > VP, Product Development > SystemBind Consulting & IT Services Inc. > 5115 Maingate Drive, Unit #1 | Mississauga | Ontario > Tel: 416.848.0980 x 850 > Mobile: 416.388.4070 > Toll: 1.877.SYS.BIND > www.systembind.com > > On Jan 27, 2014, at 8:23 AM, "chris snow" <[email protected]> wrote: > > In addition to Openstack, I'm taking a look at Cloudstack as an option for > the stratos developer VM machine > > As a reminder, Cloudstack will be used in the VM by Stratos to support local > Stratos development. > > I have followed the installation guide on the Cloudstack wiki, but as a > Cloudstack newbie, I'm getting a bit lost with the network configuration. > > Is anyone on this list able to help with the defining what the network > architecture should look like for a single, self-contained Cloudstack VM? > > The Cloudstack setup script that I have so far is here: > > https://github.com/snowch/stratos-developer-tools/blob/cloudstack/scripts/cloudstack_setup.sh > > The development environment is currently built using vagrant and > (optionally) packer. The goal is to have two outputs: > > - a vagrant box > - a virtualbox virtual machine appliance > > Both vagrant box and virtualbox appliance will contain openstack or > cloudstack, stratos source code and stratos runtimes. > > Some users may prefer to use virtualbox, whereas others may prefer to use > vagrant. > > Many thanks, > > Chris -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
