9d8e8de589
We previously had four separate test scripts to control basic tests, tests where bifrost and its dependencies install into a virtual environment, tests where bifrost builds a deployment image, and tests where bifrost uses DHCP. This resulted in the scripts getting out of sync with one another as changes were made. In order to increase consistency in testing and improve maintainability, consolidate the three scripts into test-bifrost.sh, add symlinks where the other scripts were, and update the documentation. Change-Id: Ic005960d00a145fc7b28ed423fb8f92e41d7ef0b
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 up