Hi Chris, Would you mind raising a defect on the github page?
Many thanks, Chris On Thu, Feb 27, 2014 at 3:31 PM, SuichII, Christopher <chris.su...@netapp.com> wrote: > Chris, > > I tried pulling down the box this morning and playing around...a couple of > notes: > > 1) For anyone trying this, make sure to 'git checkout v0.4'. The changes on > master are breaking the Vagrantfile. > 2) When I run 'vagrant up xen', I can see in VirtualBox that the machine is > booted and appears to be sitting at the login prompt, but I end up with a > timeout message from Vagrant. Can you think of why Vagrant would timeout > after first boot? > > -Chris > -- > Chris Suich > chris.su...@netapp.com > NetApp Software Engineer > Data Center Platforms - Cloud Solutions > Citrix, Cisco & Red Hat > > On Feb 27, 2014, at 10:16 AM, Ian Duffy <i...@ianduffy.ie> wrote: > >> Hi Chris, >> >> Looking into it more it was because no primary storage was available. >> >> the devcloud.cfg enables localstorage but the global settings to use >> localstorage for system vms is not enabled. >> >> I enabled localstorage for system vms and hit issues noted over at: >> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201402.mbox/%3c8334166ab8f6e548a46205bd576b464f195fb...@sbpomb102.sbp.lan%3E >> >> Currently waiting on 4.3-forward to compile to test to see if the issue >> occurs on it. >> >> >> On 27 February 2014 15:13, chris snow <chsnow...@gmail.com> wrote: >> >>> Hi Ian, >>> >>> Many thanks for raising this. Would you also mind raising a defect >>> for this on github? >>> >>> I also got the InsufficientServerCapacity when I was testing, but I >>> also hit the error when running against the original devcloud2 ova, so >>> thought the error was due to my local development environment. >>> >>> I'll do some more investigation tonight. >>> >>> Many thanks, >>> >>> Chris >>> >>> On Thu, Feb 27, 2014 at 1:55 PM, Ian Duffy <i...@ianduffy.ie> wrote: >>>> Hi Chris, >>>> >>>> Just trying this out. I couldn't get the system vms started. >>>> >>>> I ran vagrant up xen, did the reload and seen my 192.168.56.10 adapter >>>> appear. >>>> >>>> I sshed into the machine, su-ed to root and: >>>> >>>> 1) Downloaded the 'cloudstack_dev_checkout.sh' and ran it >>>> 2) Copied vhd-util into scripts/vm/hypervisor/xenserver gave >>>> vagrant:vagrant ownership of it and executable rights. >>>> 3) Downloaded the 'cloudstack_dev_maven.sh' scripts and ran it >>>> >>>> Exited as root and dropped back to the vagrant user. Reloaded the >>> modified >>>> .profile file and brought up the jetty server. >>>> >>>> Executed deployDataCenter with devcloud.cfg, it completed successfully. >>>> >>>> The attempts to bring up system vms just keep cycling throwing >>>> InsufficientServerCapacity exceptions, not seeing any obvious reason for >>>> them. >>>> >>>> Is there something I'm missing? >>>> >>>> >>>> On 27 February 2014 08:19, chris snow <chsnow...@gmail.com> wrote: >>>> >>>>> btw - I've started cleaning up my devcloud github repo to get the code >>>>> ready to be commited back into the Cloudstack Apache git repository. >>>>> >>>>> On Thu, Feb 27, 2014 at 4:00 AM, chris snow <chsnow...@gmail.com> >>> wrote: >>>>>> There is a new version of devcloud (version 0.4) ready for testing. >>>>>> >>>>>> See here for more information: >>>>>> https://github.com/snowch/devcloud/releases/tag/v0.4 >>>>>> >>>>>> It would be great if this release could be tested and any defects >>>>>> raised on the github project. >>>>>> >>>>>> The ultimate goal is that this project will replace devcloud2 and that >>>>>> this project will be committed back into Cloudstack. >>>>> >>>>> >>>>> >>>>> -- >>>>> Check out my professional profile and connect with me on LinkedIn. >>>>> http://lnkd.in/cw5k69 >>>>> >>> >>> >>> >>> -- >>> Check out my professional profile and connect with me on LinkedIn. >>> http://lnkd.in/cw5k69 >>> > -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
