devstack/roles/orchestrate-devstack
Lee Yarwood e11d367d8e orchestrate-devstack: Copy controller ceph.conf and keyrings to subnode
This change introduces a basic role to copy the contents of /etc/ceph
between the controller and subnodes during orchestrate-devstack allowing
a multinode ceph job to be introduced by
I9ffdff44a3ad42ebdf26ab72e24dfe3b12b1ef8b.

Note that this role is only used when devstack-plugin-ceph is enabled.

Change-Id: I324c0f35db34f8540ca164bf8c6e3dea67c5b1b4
2021-02-10 16:01:04 +00:00
..
defaults Fix multinode mode for devstack 2018-03-07 12:47:55 +00:00
tasks orchestrate-devstack: Copy controller ceph.conf and keyrings to subnode 2021-02-10 16:01:04 +00:00
README.rst Enforce linear strategy for orchestrate-devstack 2018-03-11 11:17:42 +00:00

README.rst

Orchestrate a devstack

Runs devstack in a multinode scenario, with one controller node and a group of subnodes.

The reason for this role is so that jobs in other repository may run devstack in their plays with no need for re-implementing the orchestration logic.

The "run-devstack" role is available to run devstack with no orchestration.

This role sets up the controller and CA first, it then pushes CA data to sub-nodes and run devstack there. The only requirement for this role is for the controller inventory_hostname to be "controller" and for all sub-nodes to be defined in a group called "subnode".

This role needs to be invoked from a playbook that uses a "linear" strategy.

Role Variables