Workflow to deploy split-controlplane architecture
- Create split-control-plane mistral workflow which: [do we want to have mistral orchestrate this?]
- deploys control-plane stack
- extracts data from control-plane stack
- deploys N edge stacks with heat:
- assumption: nodes are in ironic OR are setup for already deployed servers
- Hook new mistral workflow into tripleo-client option
- Update CI to trigger split-control-plane mistral workflow in place of scripts
Blueprint information
- Status:
- Complete
- Approver:
- Emilien Macchi
- Priority:
- Medium
- Drafter:
- James Slagle
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- James Slagle
Related branches
Related bugs
Sprints
Whiteboard
Not going to implement this one as originally planned. The code for the export data between stacks was added in "openstack overcloud export", however there is no plan for a overall workflow for deploying mulit-stack.
[2019-09-18] (aschultz): Not implemented by the end of Train, moving out to Ussuri
[2019-04-15] (aschultz) As this is not completely implemented, moving to Train.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
