Julia Kreger 09cda5ec9c Improve logging for VMs to identify IPA issues
Since the coreos config drive issue has been solved elsewhere
we shall re-use the line to improve our logging so we can have
useful configdrive logs.

Change-Id: I0e044121e146f3036aa6b1830983dd9d7a68e9ac
Depends-On: I76a2a23e2a75022bae3511700c81145b5cbeae77
2015-09-08 17:06:58 -04:00
2015-08-05 11:09:35 -07:00
2015-05-25 13:52:46 +00:00
2015-04-16 15:58:23 -04:00
2015-08-28 13:42:02 +03:00
2015-07-15 17:04:11 -04:00
2015-04-20 16:06:20 -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 with in 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 in to the bifrost directory
    cd bifrost/tools/vagrant_dev_env

edit Vagrantfile:
    change public_key to correct key name
    change network_interface to match your needs
    change bridged adaptor

Boot the vm with:
    vagrant up
Description
Ansible roles and playbooks to enable a standalone Ironic install
Readme 27 MiB
Languages
Python 55.4%
Jinja 27%
Shell 17.6%