devstack/roles/orchestrate-devstack
Andrea Frittoli afe1414019 Ensure passwordless ssh with stack between nodes
For compute migration to work, the stack user needs to be configured
with passwordless ssh between all hosts involved in the migration.

Reuse the build ssh-key for this, which is already distributed for
user root.

Depends-on: https://review.openstack.org/563584

Change-Id: Id07f55fea06509466add35315c135dbfba6aa714
2018-04-23 11:44:33 +00:00
..
defaults Fix multinode mode for devstack 2018-03-07 12:47:55 +00:00
tasks Ensure passwordless ssh with stack between nodes 2018-04-23 11:44:33 +00:00
README.rst Enforce linear strategy for orchestrate-devstack 2018-03-11 11:17:42 +00:00

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