06c4f96a99
On Ubuntu, apt automatically starts dnsmasq upon installing it. This temporarily causes a blip in the system's ability to resolve domain names. In a bifrost install, this becomes apparent when the next package ansible attempts to install, rabbitmq-server, fails with the error "Could not resolve 'archive.ubuntu.com'", while subsequent packages and subsequent runs of the bifrost install step succeed. This patch moves the dnsmasq to the end of the required package list so that its installation does not interfere with the installation of the rest of the required packages. An alternative to this fix could be to configure policy-rc.d to not start services by default. This would require making sure all services are managed in bifrost-ironic-install/tasks/main.yml and would be a bit more dramatic of a change. Change-Id: If1558d76ce3f652c0798b459678baea9f8b26fb0
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