8a4d9ff32a
The DHCP test ultimately relies upon bifrost putting in place the correct DHCP configuration to reliably boot machines, and then (hopefully) ensure that no unknown machines are given leases. This is in order to help simulate the Infracloud configuration. In order to do this, and hopefully get the CI test into a passing state, I have increased the amount of memory allocated to each VM as the realistic minimum for IPA is 1 GB, and introduced specific stops and starts to VMs present during the test sequence in order to limit the number of concurrent running virtual machines. Change-Id: Ia612414edd80d154200e9df12b410a327db19cff
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