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