9629270987
We should avoid using six.iteritems/keys achieve iterators. We can use dict.items/keys instead, as it wil l return iterators in PY3 as well. And dict.items/keys will more readable. In py2, the performance about list should be negligible, see https://wiki.openstack.org/wiki/Python3 and http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html Change-Id: I6f8ee2ed36ed94e2ef8347463f56eed44464a605
Vagrant support for developers
Bifrost vagrant file for developers can be found in the
tools/vagrant_dev_env directory. Running
vagrant up from within this folder will bring up an Ubuntu
Trusty box with Bifrost installed.
By default, the VM will have three interfaces:
- eth0 - connected to a NAT network
- eth1 - connected to Host-only network named: vboxnet1
- eth2 - bridged - adapter must be set in Vagrantfile
Walkthrough done on OS X
Setup vagrant by:
- Installing git
- Installing virtualbox
- Installing vagrant
- Installing ansible
Configure Vagrant with the correct box:
vagrant box add ubuntu/trusty64Clone bifrost repo:
git clone https://github.com/openstack/bifrost.gitChange into the bifrost directory:
cd bifrost/tools/vagrant_dev_envEdit the Vagrantfile:
- Change the
bifrost.vm.networkpublic_networkvalue to a valid network interface to allow Bare Metal connectivity - Change
public_keyto correct key name - Change
network_interfaceto match your needs
Boot the VM with:
vagrant upInstallation Options
Ansible is installed within the VM directly from source or from the
path set by ANSIBLE_GIT_URL. You can modify the path of
installation by setting ANSIBLE_INSTALL_ROOT environment
variable. The default value is /opt/stack. When set in the
host, this variable will also be set as an environment variable inside
the VM for use by test scripts.
Note:
Only the ansible installation path is configurable at this point using the enviroment variable. All other dependencies will still continue to cloned under
/opt/stack.