e3d42dc851
In a previous commit, we erroniously removed the setting to disable CoreOS from loading configuration drive files. Turns out that the solution in Ironic was to update the template files, and to await for CoreOS to remedy the issue, which has not occured. This ultimately results in every other deployment to a machine to be missing a configuration drive since we removed the setting. As such, we need to put the setting back, this time in the template file we utilize. Previous commit: I0e044121e146f3036aa6b1830983dd9d7a68e9ac Change-Id: I7d4a9c165f069865a26f6900f64046485f00cdee
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