openstack/bifrost
Code Issues Proposed changes

Merge "Addition of dynamic enrollment and deployment playbooks"

Browse Source
This commit is contained in:
Jenkins 2015-06-26 17:12:14 +00:00 committed by Gerrit Code Review
commit 47abf7780e
3 changed files with 48 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
README.rst
View File

@ -263,9 +263,17 @@ An example file can be found at inventory/baremetal.csv.example.
How this works? How this works?
--------------- ---------------
The enroll.yaml playbook requires a variable (baremetal_csv_file) be set or Utilizing the dynamic inventory module, enrollment is as simple as setting
passed into the playbook execution. NOTE: This MUST be the full path to the the BIFROST_INVENTORY_SOURCE environment variable to your inventory data
CSV file to be consumed by the Ansible playbooks and loaded into ironic. source, and then executing the the enrollment playbook.::
export BIFROST_INVENTORY_SOURCE=/tmp/baremetal.json
ansible-playbook -vvvv -i inventory/bifrost_inventory.py enroll-dynamic.yaml
The legacy enroll.yaml playbook requires a variable (baremetal_csv_file) be
set or passed into the playbook execution. NOTE: This MUST be the full path
to the CSV file to be consumed by the Ansible playbooks and loaded into
ironic.
Example:: Example::
@ -281,18 +289,20 @@ split into three separate playbooks based up the setting of ipmi_bridging.
Hardware Deployment Hardware Deployment
=================== ===================
Requirements:
- The baremetal.csv file that was utilized for the enrollment process.
How this works? How this works?
--------------- ---------------
The deploy.yaml playbook is intended to create configdrives for servers, and After the nodes are enrolled, they can be deployed upon. Bifrost is geared to
initiate the node deployments through Ironic. IPs are injected into the config utilize configuration drives to convey basic configuration information to the
drive and are statically assigned. each host. This case is the same between the newer deploy-dynamic.yaml
playbook and the older legacy deploy.yaml playbook.
Example:: To utilize the newer dynamic inventory based deployment::
export BIFROST_INVENTORY_SOURCE=/tmp/baremetal.json
ansible-playbook -vvvv -i inventory/bifrost_inventory.py enroll-dynamic.yaml
To utilize the legacy csv file based playbook::
ansible-playbook -i inventory/localhost -vvvv deploy.yaml -e baremetal_csv_file=inventory/baremetal.csv ansible-playbook -i inventory/localhost -vvvv deploy.yaml -e baremetal_csv_file=inventory/baremetal.csv
@ -311,8 +321,8 @@ Note:
- Cleaning mode is explicitly disabled in the test-bifrost.yaml playbook due to the fact that is an IO intensive operation that can take a great deal of time. - Cleaning mode is explicitly disabled in the test-bifrost.yaml playbook due to the fact that is an IO intensive operation that can take a great deal of time.
Testing with Virtual Machines Legacy - Testing with Virtual Machines
============================= ======================================
Bifrost supports using virtual machines to emulate the hardware. All of the Bifrost supports using virtual machines to emulate the hardware. All of the
steps mentioned above are mostly the same. steps mentioned above are mostly the same.

13
playbooks/deploy-dynamic.yaml Normal file
View File

@ -0,0 +1,13 @@
---
- hosts: localhost
connection: local
name: "Collect facts"
sudo: no
gather_facts: yes
- hosts: baremetal
name: "Create configuration drive files and deploy machines from inventory"
sudo: no
connection: local
roles:
- role: bifrost-configdrives-dynamic
- role: bifrost-deploy-nodes-dynamic

12
playbooks/enroll-dynamic.yaml Normal file
View File

@ -0,0 +1,12 @@
---
- hosts: localhost
connection: local
name: "Collect facts"
sudo: no
gather_facts: yes
- hosts: baremetal
connection: local
name: "Enroll hardware from inventory into Ironic"
sudo: no
roles:
- role: ironic-enroll-dynamic