stephane c785d947f6 Improve log collection
Logs from test runs on systemd systems were not being
collected properly. Allow logs to be collected from
systemd if available and fall back to the upstart
location. Also, only collect information from netstat
and iptables if present.

Change-Id: I000c3d0c7d576eeb4ab051f68a6fef8a83dc06fb
Closes-Bug: #1470128
2016-02-23 17:28:57 -08:00
2016-01-25 17:46:46 +08:00
2016-02-23 17:28:57 -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 27 MiB
Languages
Python 55.4%
Jinja 27%
Shell 17.6%