TripleO Split Control Plane from Compute/Storage Support

Registered by John Fulton on 2018-04-30

Introduces support for a mode of deployment where the controlplane nodes are deployed and then batches of compute/storage nodes can be added independently without any update of the controlplane stack.

Blueprint information

Status:
Complete
Approver:
Alex Schultz
Priority:
Medium
Drafter:
Steven Hardy
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
Accepted for train
Implementation:
Implemented
Milestone target:
milestone icon train-1
Started by
Giulio Fidente on 2018-08-07
Completed by
Alex Schultz on 2019-06-07

Related branches

Sprints

Whiteboard

[2019-04-15] (aschultz) As this is not completely implemented, moving to Train.

https://review.openstack.org/#/q/topic:split-controlplane+(status:open+OR+status:merged)

Gerrit topic: https://review.openstack.org/#q,topic:bp/split-controlplane,n,z

Addressed by: https://review.openstack.org/581080
    Add AllNodesExtraMapData parameter

Addressed by: https://review.openstack.org/638002
    Add external_resource_vip_id property to network_data.yaml

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.