Support the use of an external load balancer as frontend for the Overcloud
Make it possible to use optionally an external load balancer as frontend for the Overcloud.
Spec review is at: https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Giulio Fidente
- Direction:
- Needs approval
- Assignee:
- Giulio Fidente
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Giulio Fidente
- Completed by
- Giulio Fidente
Related branches
Related bugs
Sprints
Whiteboard
https:/
Gerrit topic: https:/
Addressed by: https:/
external loadbalancer: Add net_vip_
Addressed by: https:/
Make load balancer deployment optional via template param
Addressed by: https:/
Allow for usage of pre-allocated IPs for the Controller nodes
Gerrit topic: https:/
Addressed by: https:/
Add sample environment to document usage of pre-defined IPs
Addressed by: https:/
Do not rename the nested port resource name for the VIPs
Addressed by: https:/
Add net_vip_
Addressed by: https:/
Allow for usage of pre-allocated IPs for the controller nodes
Addressed by: https:/
Make load balancer deployment optional via template param
Addressed by: https:/
Add sample environment file to document usage of predictable IPs
