Yolanda Robla 2d713268a3 Allow to populate the domain setting of dnsmasq
As shown in documentation: this is optional, but if it is set, it
does the following things.
1) Allows DHCP hosts to have fully qualified domain names, as long
    as the domain part matches this setting.
2) Sets the "domain" DHCP option thereby potentially setting the
   domain of all systems configured by DHCP
3) Provides the domain part for "expand-hosts"

Under certain cases, have FQDN in servers is a need.

Change-Id: Id8a109984c13e95841d9e0f283d55261d083542c
2016-01-13 15:03:59 +01: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-12-18 05:00:41 -05:00
2015-09-14 08:44:24 -04:00
2015-11-03 13:31:39 -05:00
2015-12-15 15:08:48 +05:30
2015-07-15 17:04:11 -04:00
2015-12-17 05:17:27 -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.3%
Jinja 27.1%
Shell 17.6%