cloud-certification-team team mailing list archive
-
cloud-certification-team team
-
Mailing list archive
-
Message #00015
Re: [Merge] lp:~jeffmarcom/cloud-testing/devstack_vagrant into lp:cloud-testing/cloudbox
Review: Needs Fixing
There needs to be a readme for vagrant to avoid some issues such as:
1: Use VBox 4.2.16 (or at least something other than 4.2.14 which has a regression that causes the import to fail).
2: if run on a laptop, the process isn't as smooth initially:
# bladernr@klaatu:~/development/devstack_vagrant$ VAGRANT_LOG=error vagrant up
# [default] Importing base box 'cloudbox'...
# [default] The guest additions on this VM do not match the install version of
# VirtualBox! This may cause things such as forwarded ports, shared
# folders, and more to not work properly. If any of those things fail on
# this machine, please update the guest additions and repackage the
# box.
#
# Guest Additions Version: 4.2.0
# VirtualBox Version: 4.2.16
# [default] Matching MAC address for NAT networking...
# [default] Clearing any previously set forwarded ports...
# [default] Forwarding ports...
# [default] -- 22 => 2222 (adapter 1)
# [default] Creating shared folders metadata...
# [default] Clearing any previously set network interfaces...
# [default] Available bridged network interfaces:
# 1) eth0
# 2) virbr0
# 3) wlan0
# What interface should the network bridge to?
This happens on every boot for me and could be confusing to people who are not familiar with vagrant or virtualbox.
3: Warn that initially it will take a long while to set up. Downloading the initial box will take a bit, and installing cloudbox and devstack will take a long while as well.
4: Additional warning: All the steps in vagrant_test.sh are run every time you boot the vm. So you may have to wait nearly 40 minutes (Actual time was 38m and some change) or longer every time you try this out while it re-installs all the toolset stuff, cloudbox, and devstack, which is a significant time.
Aside from that, I don't know that the defaults in Vagrantfile or 4096M and 4 CPUs will cause a real issue, but MAY on a laptop that doesn't physically meet those limits, or could cause issues on a laptop that doesn't go beyond those limits.
--
https://code.launchpad.net/~jeffmarcom/cloud-testing/devstack_vagrant/+merge/180974
Your team Cloud Certification is subscribed to branch lp:cloud-testing/cloudbox.
References