Rename "external" network to "public api" network
There is a lot of confusion around the intended use of what we currently label as the "external" network. Since we tend to "overload" this network for floating IPs for the overcloud workload for convenience in testing etc, the apparent purpose is that is what it is for. It would be more clear if the network were named "ExternalAPI" or "PublicAPI". As a separate issue we could look at how we could make a proper separate network for use in floating IP test in our default templates/CI.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Brent Eagles
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
This may end up being impractical since it makes upgrading difficult (impossible?) If this proves to be the case, perhaps we can look at introducing an explicitly "example for floating IP" provider networks in our default templates.
(jaosorior): changing this would be quite a change for a lot of deployments; Not too keen on this.
(beagles): Understood. After discussing this from time to time, I think this is unfortunately something we are just stuck with.
