Julia Kreger 0bcdeaf0e7 CORS configuration support
Since CORS support has landed in Ironic, we should enable a bifrost
user to be able to turn CORS on.

Note: Presently the ironic-webclient sends an x-client header which
causes the oslo middlewear portion that supplies CORS to reject the
request.  A change is pending to remove that from the webclient,
however if a user wishes to perform testing with the webclient,
x-client will need to be added to the list of allowed headers.

Depends-On: I23e902c8637e142fba23d71467225d48ee265253
Change-Id: I487a57c54995e0572072aa54193e985ea257ed70
2015-09-27 09:30:38 -04:00
2015-09-14 08:44:24 -04:00
2015-09-27 09:30:38 -04:00
2015-05-25 13:52:46 +00:00
2015-04-16 15:58:23 -04:00
2015-09-11 10:11:48 -07:00
2015-09-14 08:44:24 -04:00
2015-07-15 17:04:11 -04:00
2015-07-29 13:51:28 -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 27 MiB
Languages
Python 55.3%
Jinja 27.1%
Shell 17.6%