openstack/bifrost
Code Issues Proposed changes
Ansible roles and playbooks to enable a standalone Ironic install
560 Commits 10 Branches 51 Tags 27 MiB
Python 55.3%
Jinja 27.1%
Shell 17.6%
06c4f96a99
Go to file
Colleen Murphy 06c4f96a99 Move dnsmasq to the end of the Debian package list 
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
2015-09-15 14:15:33 -07:00
bifrost Add the rest of the cookiecutter-generated files for testing 2015-06-24 16:09:08 -07:00
doc/source Cleanups for README.vagrant 2015-09-14 08:44:24 -04:00
playbooks Move dnsmasq to the end of the Debian package list 2015-09-15 14:15:33 -07:00
scripts Merge "Allow Test VM RAM setting to be tunable" 2015-09-09 15:02:04 +00:00
tools Vagrantfile and vagrant.yml for testing 2015-07-23 11:09:03 -07:00
.gitignore Add `logs' from test-bifrost to .gitignore 2015-07-03 12:42:01 -04:00
.gitreview Add .gitreview file 2015-05-25 13:52:46 +00:00
.mailmap Add cookiecutter-generated files for project 2015-06-10 08:40:19 -07:00
.testr.conf Add the rest of the cookiecutter-generated files for testing 2015-06-24 16:09:08 -07:00
babel.cfg Add cookiecutter-generated files for project 2015-06-10 08:40:19 -07:00
CONTRIBUTING.rst Add cookiecutter-generated files for project 2015-06-10 08:40:19 -07:00
env-vars Blind stab at breaking things into more roles 2015-03-12 17:07:46 -04:00
HACKING.rst Fix HACKING.rst and canary test for merges 2015-09-08 21:49:02 +00:00
LICENSE Adding LICENSE file 2015-04-16 15:58:23 -04:00
MANIFEST.in Add cookiecutter-generated files for project 2015-06-10 08:40:19 -07:00
openstack-common.conf Add cookiecutter-generated files for project 2015-06-10 08:40:19 -07:00
README.rst README cleanups 2015-09-11 10:11:48 -07:00
README.vagrant.rst Cleanups for README.vagrant 2015-09-14 08:44:24 -04:00
requirements.txt Resync with openstack/requirements 2015-08-27 08:56:40 -04:00
setup.cfg Add cookiecutter-generated files for project 2015-06-10 08:40:19 -07:00
setup.py Sync with global requirements 2015-07-15 17:04:11 -04:00
test-requirements.txt Resync with openstack/requirements 2015-08-27 08:56:40 -04:00
tox.ini Activate pep8 check that _ is imported 2015-07-29 13:51:28 -05:00
troubleshooting.rst Clean up troubleshooting.rst markup 2015-09-11 14:22:20 -07:00

README.vagrant.rst

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/trusty64

Clone bifrost repo:

git clone https://github.com/openstack/bifrost.git

Change into the bifrost directory:

cd bifrost/tools/vagrant_dev_env

Edit the Vagrantfile:

  • Change the bifrost.vm.network public_network value to a valid network interface to allow Bare Metal connectivity
  • Change public_key to correct key name
  • Change network_interface to match your needs

Boot the VM with:

vagrant up