Use Split Stack (deployed-server) by default
Once Split Stack phase 2 is implemented, we should move to a model where we make use of the deployed-server template by default, and always deploy 2 separate stacks during every deployment. We should have a mistral workflow to tie the 2 stacks together so that it is transparent to the operator that we're deploying 2 stacks (it's still just one command to deploy the overcloud).
Blueprint information
- Status:
- Complete
- Approver:
- Emilien Macchi
- Priority:
- Medium
- Drafter:
- James Slagle
- Direction:
- Approved
- Assignee:
- James Slagle
- Definition:
- Approved
- Series goal:
- Accepted for pike
- Implementation:
-
Implemented
- Milestone target:
-
pike-3
- Started by
- James Slagle
- Completed by
- James Slagle
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add os-collect-config data as an output
Addressed by: https:/
Add DeploymentSwift
Addressed by: https:/
Add DeploymentSwift
Addressed by: https:/
Add split-stack environments
Addressed by: https:/
Add VipMap output
Addressed by: https:/
Add DeployedServerE
Addressed by: https:/
Add documentation for split-stack
Addressed by: https:/
Use ServerOsCollect
Addressed by: https:/
Document using current-tripleo
Work Items
Dependency tree
* Blueprints in grey have been implemented.
