Go to file
stephane 11a1944cfd Fixing virtualenv issues
A couple of issues relating to virtualenv arose while
testing on Ubuntu 15.10. Adjust the virtualenv setting
in the pip install phase to work correctly and simplify
the check and install of virtualenv so we get the right
package.

Change-Id: I09fb604ec6667aa45c3c2063adf3d760114aa65a
2016-02-23 13:46:10 -08:00
2016-01-25 17:46:46 +08:00
2016-02-23 13:46:10 -08:00
2016-02-23 13:46:10 -08:00
2015-12-17 05:17:27 -05:00
2015-05-25 13:52:46 +00:00
2015-04-16 15:58:23 -04:00
2015-09-14 08:44:24 -04:00
2015-12-15 15:08:48 +05:30
2016-01-22 11:39:17 -05:00
2015-12-17 05:17:27 -05:00

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
Description
Ansible roles and playbooks to enable a standalone Ironic install
Readme 31 MiB
Languages
Python 57.4%
Jinja 24.6%
Shell 18%