Andrea Frittoli | 5e714d3 | 2018-02-17 22:21:26 +0000 | [diff] [blame] | 1 | Orchestrate a devstack |
| 2 | |
| 3 | Runs devstack in a multinode scenario, with one controller node |
| 4 | and a group of subnodes. |
| 5 | |
| 6 | The reason for this role is so that jobs in other repository may |
| 7 | run devstack in their plays with no need for re-implementing the |
| 8 | orchestration logic. |
| 9 | |
| 10 | The "run-devstack" role is available to run devstack with no |
| 11 | orchestration. |
| 12 | |
| 13 | This role sets up the controller and CA first, it then pushes CA |
| 14 | data to sub-nodes and run devstack there. The only requirement for |
| 15 | this role is for the controller inventory_hostname to be "controller" |
| 16 | and for all sub-nodes to be defined in a group called "subnode". |
| 17 | |
Andrea Frittoli | 02bb57b | 2018-03-09 17:12:38 +0000 | [diff] [blame] | 18 | This role needs to be invoked from a playbook that uses a "linear" strategy. |
Andrea Frittoli | 5e714d3 | 2018-02-17 22:21:26 +0000 | [diff] [blame] | 19 | |
| 20 | **Role Variables** |
| 21 | |
| 22 | .. zuul:rolevar:: devstack_base_dir |
| 23 | :default: /opt/stack |
| 24 | |
| 25 | The devstack base directory. |