9909e00ede
Bifrost intiially had support for parsing ZUUL_CHANGES, however due to changes in it's gate CI jobs, these steps are no longer necessary. As a result of this change, we also need to support copying files directly and not forcibly resetting the git status since the repositories are provided to us in the way they are needed without additional work. As a result, added logic to the preparation and git download role to support local file copies instead of git downloads. Also changed default source location for CI testing repos to leverage the WORKSPACE environment variable. Change-Id: I23e902c8637e142fba23d71467225d48ee265253 Depends-On: I01c16990dc66988fab29c41ec4b4e6094213b2ca
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