openstack/bifrost
Code Issues Proposed changes
Ansible roles and playbooks to enable a standalone Ironic install
569 Commits 10 Branches 51 Tags 27 MiB
Python 55.3%
Jinja 27.1%
Shell 17.6%
15e1c3f22e
Go to file
Julia Kreger 15e1c3f22e Ansible 2.0 compatibility 
These changes allow the various playbooks to be executed by
Ansible 1.9.x and 2.0. This was necessary as 2.0 has a number
of changes to the YAML processor, and certain ways of doing
things have naturally had to change.

- Removed pass-through variable when a role is explicitly defined
  with variables passed through to it as updated yaml parser fails
  to handle appropriately.
- Defined a default dib_packages variable of an empty string.
- Changed stray boolean compare to use an is defined check as
  the the parser in Ansible 2.0 does not equate undefined to
  false.
- Explicitly defined the testing_user for the syntax check
  as the check fails without it.
- Revised MySQL module syntax usage to be compatible between
  Ansible 1.9.x and 2.0 development branches.
- Updated some conditionals making string compares with lookups
  which is apparently problematic in Ansible 2.0.

Depends-On: I9d5fa719793896cce00a69dafba738755b45b068
Depends-On: I23e902c8637e142fba23d71467225d48ee265253
Change-Id: I4fec7f44dd9d591388f345b3f449cb44b8e50744
Closes-Bug: 1469862
2015-10-02 12:58:11 +00: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 Ansible 2.0 compatibility 2015-10-02 12:58:11 +00:00
scripts Ansible 2.0 compatibility 2015-10-02 12:58:11 +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