d5896025b7
This patch enables the adoption of existing subnets into a subnetpool. Adoption of a subnet is done by passing the ID of the hosting network and the address family (ip_version) which causes all subnets in the specified address family on the given network to be adopted by the subnet pool. This continues to work within the constraints on subnet pool membership of subnets on the same network. This also ensures prefix uniqueness across an address scope before comitting the adoption of subnets. Change-Id: I5d3c07beb7f109142d2e3633e69f86ca39edc450 Partially-Implements: blueprint subnet-onboard Co-Authored-By: Ryan Tidwell <rtidwell@suse.com> Co-Authored-By: Reedip <reedip.banerjee@nectechnologies.in> Co-Authored-By: Trevor McCasland <TM2086@att.com> Co-Authored-By: Bernard Caffarelli <bcafarel@redhat.com>
14 lines
709 B
YAML
14 lines
709 B
YAML
---
|
|
prelude: >
|
|
Existing subnets that were created outside of a subnet pool can know
|
|
be moved, or "onboarded" into an existing subnet pool. This provides
|
|
a way for subnets to be brought under the management of a subnet pool
|
|
and begin participating in an address scope. By enabling onboarding,
|
|
existing subnets can be used with features that build on subnet pools
|
|
and address scopes. Subnet onboarding is subject to all the same
|
|
restrictions as and guarantees currently enforced by subnet pools
|
|
and address scopes.
|
|
features:
|
|
- Existing subnets can now be moved into a subnet pool, and by extension
|
|
can be moved into address scopes they were not initially participating in.
|