Ganesh Mahalingam
802cec490b
Make init element configurable for bifrost vagrant VM
Bifrost vagrant uses simple-init by default for post install modifications. This patch allows the use of an alternate init mechanism, eg: cloud-init Change-Id: If22416f48fbf43173f008c86b978f11d937a8a99 Co-Authored-By: John.L.Villalovos <john.l.villalovos@intel.com> Closes-Bug: #1541548
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
Languages
Python
55.3%
Jinja
27.1%
Shell
17.6%