Difference between revisions of "Neutron/IPv6/PrefixDelegation"
(→Design) |
(→API Resource Design) |
||
Line 28: | Line 28: | ||
|} | |} | ||
− | A PrefixDelegation would be linked to a large Subnet (say a /56) by having a port created on the parent subnet (that could serve as the gateway for the child subnet) which would be stored in the Parent Port UUID attribute - and the prefix that was delegated would be created as another Subnet, that the PrefixDelegation resource would store in the Child Subnet UUID attribute. | + | A PrefixDelegation would be linked to a large Subnet (say a /56) by having a port created on the parent subnet (that could serve as the gateway for the child subnet, and is a /128 address) which would be stored in the Parent Port UUID attribute - and the prefix that was delegated would be created as another Subnet, that the PrefixDelegation resource would store in the Child Subnet UUID attribute. |
Revision as of 16:22, 20 March 2014
Prefix Delegation API Extension
This is an API extension to Neutron, to create IPv6 prefix delegation functionality in the Neutron API.
https://blueprints.launchpad.net/neutron/+spec/ipv6-prefix-delegation
API Resource Design
One possible implementation is to create a new API Extension to Neutron, that creates a new resource:
Resource |
PrefixDelegation |
The PrefixDelegation resource would contain the following attributes:
PrefixDelegation |
---|
UUID |
Parent Port UUID |
Child Subnet UUID |
A PrefixDelegation would be linked to a large Subnet (say a /56) by having a port created on the parent subnet (that could serve as the gateway for the child subnet, and is a /128 address) which would be stored in the Parent Port UUID attribute - and the prefix that was delegated would be created as another Subnet, that the PrefixDelegation resource would store in the Child Subnet UUID attribute.