CI scenario for TripleO Split Control Plane
[Feb 2020: abandoned because we don't want to depend on a multinode job]
In order to support the Split Control Plane blueprint [1] a CI job should be added which deploys two heat stacks on separate nodes and does a basic test of the deployment by launching an instance.
- reprovision three-node job upstream to deploy 1 uc, 1 all-in-one controller, 1 remote compute node
- deploy glance swift backend on controller node
- verify job can launch instance
- add storage features to CI job as they are implemented in TripleO, e.g. ceph on compute node, cinder-volume on compute node
[1] https:/
Blueprint information
- Status:
- Complete
- Approver:
- Alex Schultz
- Priority:
- Undefined
- Drafter:
- John Fulton
- Direction:
- Approved
- Assignee:
- John Fulton
- Definition:
- Obsolete
- Series goal:
- Accepted for ussuri
- Implementation:
-
Deferred
- Milestone target:
- None
- Started by
- Completed by
- John Fulton
Related branches
Related bugs
Sprints
Whiteboard
https:/
Gerrit topic: https:/
Addressed by: https:/
WIP/DNM: Add featureset 57 for split controlplane
Addressed by: https:/
WIP/DNM: Add split_control_
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Add split-controlpl
Addressed by: https:/
Add featureset 59 for split controlplane
Work Items
Dependency tree
* Blueprints in grey have been implemented.
