User-specifiable Control Plane IP for TripleO Routed Isolated Networks
This blueprint is part of the series of blueprints covered by the bp:tripleo-
In a routed network environment, it may be desired to have specific control over which nodes receive which IP addresses according to their geographic location. Eventually this may be possible using location awareness in Ironic and Neutron, but those features are still in the design phase.
Predictable placement of the control plane IP addresses is currently not possible. This will be required for some deployments, but will also allow for testing of routed networks deployments prior to a fully automated approach. The changes required will be at the role-level. The end result will be the ability to set the Control Plane IP using a map, similar to environments/
Blueprint information
- Status:
- Complete
- Approver:
- Alex Schultz
- Priority:
- Medium
- Drafter:
- Dan Sneddon
- Direction:
- Approved
- Assignee:
- Dan Sneddon
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
-
Implemented
- Milestone target:
-
rocky-3
- Started by
- Alex Schultz
- Completed by
- Alex Schultz
Related branches
Related bugs
Sprints
Whiteboard
[2018-07-25] (aschultz) Marking as implemented as https:/
[2018-07-11] one patch merged, 2 abandoned
[2017-12-08] Moving out to Rocky. If necessary please request FFE to explain why this is needed for Queens.
Gerrit topic: https:/
Addressed by: https:/
blueprint tripleo-
Gerrit topic: https:/
Addressed by: https:/
blueprint tripleo-
Addressed by: https:/
Add pre-selected Control Plane IP support.
Work Items
Dependency tree

* Blueprints in grey have been implemented.