[RFE] Formalize use of subnet service-type for draining subnets
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Wishlist
|
Unassigned |
Bug Description
As documented in https:/
One use case for this is extending or reducing FIP pools in a deployment. Assume there is a /24 in use as public subnet which is running full. Adding a second /24 is possible, but will waste some IPs for network, gateway and broadcast address. So the better solution will be to add a /23, gradually migrate the existing users away from the /24 and finally remove the old /24. In order for this to be feasible, one must prevent allocation from the old subnet to happen during the migration phase. The same applies when an operator wants to reduce the size of a pool.
Since the above solution is undocumented, it would be useful to make it documented and thus ensure that this stays a dependable workflow for operators. Maybe one can also define a well-known "bogus" owner that could be added in case the verification of device owners was to be made more strict. Having some functional testing for this scenario might be an extra bonus.
summary: |
- Formalize use of subnet service-type for draining subnets + [RFE] Formalize use of subnet service-type for draining subnets |
Changed in neutron: | |
importance: | Undecided → Wishlist |
This RFE was approved in the drivers meeting celebrated today [1]. No spec is required (but a good documentation!).
Thanks for this proposal.
[1]https:/ /meetings. opendev. org/meetings/ neutron_ drivers/ 2023/neutron_ drivers. 2023-06- 30-14.00. log.html