Bifrost Guide¶

Prepare the Control Host¶

Follow the Install dependencies section of the Quick Start guide instructions to set up kolla and kolla-ansible dependencies. Follow the instructions in either the Install kolla for development section or the Install kolla for deployment or evaluation section to install kolla and kolla-ansible.

Prepare the Deployment Host¶

RabbitMQ requires that the system’s hostname resolves to the IP address that it has been configured to use, which with bifrost will be 127.0.0.1. Bifrost will attempt to modify /etc/hosts on the deployment host to ensure that this is the case. Docker bind mounts /etc/hosts into the container from a volume. This prevents atomic renames which will prevent Ansible from fixing the /etc/hosts file automatically.

To enable bifrost to be bootstrapped correctly, add an entry to /etc/hosts resolving the deployment host’s hostname to 127.0.0.1, for example:

cat /etc/hosts
127.0.0.1 bifrost localhost

The following lines are desirable for IPv6 capable hosts:

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
192.168.100.15 bifrost

Prepare Kolla-Ansible Inventory¶

Kolla-ansible will deploy bifrost on the hosts in the bifrost Ansible group. In the all-in-one and multinode inventory files, a bifrost group is defined which contains all hosts in the deployment group. This top level deployment group is intended to represent the host running the bifrost_deploy container. By default, this group contains localhost. See Multinode Deployment of Kolla for details on how to modify the Ansible inventory in a multinode deployment.

Bifrost does not currently support running on multiple hosts so the bifrost group should contain only a single host, however this is not enforced by kolla-ansible. Bifrost manages a number of services that conflict with services deployed by kolla including OpenStack Ironic, MariaDB, RabbitMQ and (optionally) OpenStack Keystone. These services should not be deployed on the host on which bifrost is deployed.

Prepare Kolla-Ansible Configuration¶

Follow the instructions in Quick Start to prepare kolla-ansible’s global configuration file globals.yml. For bifrost, the bifrost_network_interface variable should be set to the name of the interface that will be used to provision bare metal cloud hosts if this is different than network_interface. For example to use eth1:

bifrost_network_interface: eth1

Note that this interface should typically have L2 network connectivity with the bare metal cloud hosts in order to provide DHCP leases with PXE boot options.

Since bifrost only supports the source image type, ensure that this is reflected in globals.yml

kolla_install_type: source

Prepare Bifrost Configuration¶

Kolla ansible custom configuration files can be placed in a directory given by the node_custom_config variable, which defaults do /etc/kolla/config. Bifrost configuration files should be placed in this directory or in a bifrost subdirectory of it (e.g. /etc/kolla/config/bifrost). Within these directories the files bifrost.yml, servers.yml and dib.yml can be used to configure Bifrost.

Deploy Bifrost using Kolla-Ansible¶

For development:

cd kolla-ansible
tools/kolla-ansible deploy-bifrost

For Production:

kolla-ansible deploy-bifrost

Deploy Bifrost manually¶

1. Start Bifrost Container

   docker run -it --net=host -v /dev:/dev -d \
   --privileged --name bifrost_deploy \
   kolla/ubuntu-source-bifrost-deploy:3.0.1
   

2. Copy Configuration Files

   docker exec -it bifrost_deploy mkdir /etc/bifrost
   docker cp /etc/kolla/config/bifrost/servers.yml bifrost_deploy:/etc/bifrost/servers.yml
   docker cp /etc/kolla/config/bifrost/bifrost.yml bifrost_deploy:/etc/bifrost/bifrost.yml
   docker cp /etc/kolla/config/bifrost/dib.yml bifrost_deploy:/etc/bifrost/dib.yml
   

3. Bootstrap Bifrost

   docker exec -it bifrost_deploy bash
   

4. Generate an SSH Key

   ssh-keygen
   

5. Bootstrap and Start Services

   cd /bifrost
   ./scripts/env-setup.sh
   . env-vars
   cat > /etc/rabbitmq/rabbitmq-env.conf << EOF
   HOME=/var/lib/rabbitmq
   EOF
   ansible-playbook -vvvv \
   -i /bifrost/playbooks/inventory/target \
   /bifrost/playbooks/install.yaml \
   -e @/etc/bifrost/bifrost.yml \
   -e @/etc/bifrost/dib.yml \
   -e skip_package_install=true
   

By Kolla-Ansible¶

For Development:

tools/kolla-ansible deploy-servers

For Production:

kolla-ansible deploy-servers

Manually¶

docker exec -it bifrost_deploy bash
cd /bifrost
. env-vars
export BIFROST_INVENTORY_SOURCE=/etc/bifrost/servers.yml
ansible-playbook -vvvv \
-i /bifrost/playbooks/inventory/bifrost_inventory.py \
/bifrost/playbooks/enroll-dynamic.yaml \
-e "ansible_python_interpreter=/var/lib/kolla/venv/bin/python" \
-e @/etc/bifrost/bifrost.yml

docker exec -it bifrost_deploy bash
cd /bifrost
. env-vars
export BIFROST_INVENTORY_SOURCE=/etc/bifrost/servers.yml
ansible-playbook -vvvv \
-i /bifrost/playbooks/inventory/bifrost_inventory.py \
/bifrost/playbooks/deploy-dynamic.yaml \
-e "ansible_python_interpreter=/var/lib/kolla/venv/bin/python" \
-e @/etc/bifrost/bifrost.yml

At this point Ironic should clean down the nodes and install the default OS image.

Bring Your Own Image¶

TODO

Bring Your Own SSH Key¶

To use your own SSH key after you have generated the passwords.yml file update the private and public keys under bifrost_ssh_key.

SSH daemon not running¶

By default sshd is installed in the image but may not be enabled. If you encounter this issue you will have to access the server physically in recovery mode to enable the sshd service. If your hardware supports it, this can be done remotely with ipmitool and Serial Over LAN. For example

ipmitool -I lanplus -H 192.168.1.30 -U admin -P root sol activate