neutron/releasenotes/notes/add-subnet-service-types-bc81f6df9834f96e.yaml
John Davidge de3a3cda74 IP allocation with Service Subnets
This changes the way that IPAM decides which subnets to use when
assigning IPs to newly created ports. If the port has a defined
device_owner, this is used to filter available subnets to choose
from only those with a matching service_type or no service_type
at all.

If the given network has no service subnets, then the existing
behaviour is used.

A new IPAM exception is introduced to handle the following scenarios:
1. A port is created with a device_owner and only non-matching service
   subnets exist.
2. A port is created without a device owner, and no subnets exist
   without a service_type.

With this patch, service subnets are now usable.

Implements: blueprint service-subnets
APIImpact: subnet-create and subnet-update with service_types
DocImpact: IPs assigned to new ports will now come from a service subnet
matching the port device_owner, if one exists.

Closes-Bug: 1544768
Change-Id: If3dd94a46bdee24c13d1f17c4f2e69af0cb8af63
2016-08-24 20:03:22 +01:00

16 lines
640 B
YAML

---
features:
- Subnets now have a new property 'service_types'.
This is a list of port device owners, such that
only ports with a matching device owner will be
given an IP from this subnet. If no matching
service subnet exists for the given device owner,
or no service subnets have been defined on the
network, the port will be assigned an IP from a
subnet with no service-types. This preserves
backwards compatibility with older deployments.
upgrade:
- A new table 'subnet_service_types' has been added
to cater for this feature. It uses the ID field
from the 'subnets' table as a foreign key.