de0a964e1a
os-client-config can work for standalone mode with specifically written clouds.yaml file providing auth_type as None. This patch changes `bifrost-keystone-client-config` role to write `clouds.yaml` file also when keystone is not installed, with a `bifrost` cloud configured, so that users can write automation scripts around ironic installed by bifrost in unified manner independently of whether keystone is installed or not, by using openstack --os-cloud bifrost ... command. This effectively mimics current `env-vars` file in bifrost, but using `clouds.yaml` configuration file. Change-Id: I4c27ffed20b3d02723f7be99ccd61d8cee74bea1
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/trusty64Clone bifrost repo:
git clone https://github.com/openstack/bifrost.gitChange into the bifrost directory:
cd bifrost/tools/vagrant_dev_envEdit the Vagrantfile:
- Change the
bifrost.vm.networkpublic_networkvalue to a valid network interface to allow Bare Metal connectivity - Change
public_keyto correct key name - Change
network_interfaceto match your needs
Boot the VM with:
vagrant upInstallation Options
Ansible is installed within the VM directly from source or from the
path set by ANSIBLE_GIT_URL. You can modify the path of
installation by setting ANSIBLE_INSTALL_ROOT environment
variable. The default value is /opt/stack. When set in the
host, this variable will also be set as an environment variable inside
the VM for use by test scripts.
Note:
Only the ansible installation path is configurable at this point using the environment variable. All other dependencies will still continue to cloned under
/opt/stack.