> On Dec. 15, 2012, 3:39 a.m., Rohit Yadav wrote:
> > Pfew, took me few hours to test and fix few issues.
> >
> > First of all I want to give you kudos for your work, Kudos!
> > That said, the patch fails on multiple cases. I'll commit that so we can
> > continue working on it.
> > I'm able to create a basebox but vagrant fails on xenbox. Pl. test it at
> > your end also.
> > Will try to fix this issue, next week in free time.
> >
> > Here are some of my reviews and comments:
> >
> >
> >
> > 0. I moved all the stuff in tools/devcloud/src/ and fixed the README.md
> > file for some of the things which failed for me.
> > 1. Is there a way we can use the default vagrant release without having to
> > use a fork?
> > 2. VirtualBox 4.2 was not supported, can you or Chip help fix vagrant?
> >
> >
> >
> > I did a workaround that worked for me:
> >
> > diff --git a/lib/vagrant/driver/virtualbox.rb
> > b/lib/vagrant/driver/virtualbox.rb
> > index baf462b..5a1dce2 100644
> >
> > --- a/lib/vagrant/driver/virtualbox.rb
> >
> > +++ b/lib/vagrant/driver/virtualbox.rb
> >
> > @@ -44,7 +44,8 @@ module Vagrant
> >
> > @logger.debug("Finding driver for VirtualBox version:
> > #{@version}")
> > driver_map = {
> >
> > "4.0" => VirtualBox_4_0,
> >
> > - "4.1" => VirtualBox_4_1
> >
> > + "4.1" => VirtualBox_4_1,
> >
> > + "4.2" => VirtualBox_4_1,
> >
> > }
> >
> >
> >
> > driver_klass = nil
> >
> >
> >
> > 3. The default basebox has only one NIC, which fails as DevCloud needs to
> > have
> > two nics; first one should be the host-only one and second one should be
> > the
> > NAT.
>
> Rohit Yadav wrote:
> Lastly, one more thing. We should move all the stuff that is not directly
> related to CloudStack in separate git repos which would make maintaining them
> more easy and distribution as well. But, since the code on devcloud build
> automation was already within the source code I'll commit the changes. (upto
> community to decide on this)
Thanks a lot for taking a look at it. I too am having an issue with the xenbox
build, it's not able to apt-get some packages. Is this the same problem you
were having?
1. As I understand it, the reason we have to use chip's fork of vagrant is
outlined here:
http://www.chipchilders.com/blog/2012/8/14/automatically-building-devcloud-images-for-apache-cloudstack.html.
(We actually use 2 versions of vagrant to get things working properly).
2. I'll talk to Chip about fixing his fork for Virtualbox 4.2 support.
3. The basebox does have only one nic, but the devcloud box has 2 nics. In
this case, eth1 is hostonly, and eth0 is NAT. The default NIC in vagrant is
eth0 and NAT, I could not find a way to change that, but I'll take another peak.
Thanks again.
- James
- James
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8399/#review14536
-----------------------------------------------------------
On Dec. 8, 2012, 5:31 p.m., James Martin wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/8399/
> -----------------------------------------------------------
>
> (Updated Dec. 8, 2012, 5:31 p.m.)
>
>
> Review request for cloudstack, Prasanna Santhanam and Rohit Yadav.
>
>
> Description
> -------
>
> This diff cleans up the devcloud build process.
>
> Please see tools/devcloud/README.md for more information.
>
> I also have a fork of cloudstack available with this change:
>
> https://github.com/jsmartin/incubator-cloudstack/tree/devcloud-cleanup
>
>
> Diffs
> -----
>
>
> Diff: https://reviews.apache.org/r/8399/diff/
>
>
> Testing
> -------
>
> Built the veewee basebox and the vagrant xenbox.
> Built a cloudstack vagrant box.
> Was able to reach cloudstack at http://192.168.56.10:8080/client
>
>
> Thanks,
>
> James Martin
>
>
