Difference between revisions of "Neutron/IPv6/PrefixDelegation"
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | === Etherpad === | ||
| + | |||
| + | Kilo - https://etherpad.openstack.org/p/neutron-kilo-prefix-delegation | ||
| + | |||
=== Prefix Delegation API Extension === | === Prefix Delegation API Extension === | ||
| Line 5: | Line 9: | ||
https://blueprints.launchpad.net/neutron/+spec/ipv6-prefix-delegation | https://blueprints.launchpad.net/neutron/+spec/ipv6-prefix-delegation | ||
| − | === Design === | + | === API Resource Design === |
One possible implementation is to create a new API Extension to Neutron, that creates a new resource: | One possible implementation is to create a new API Extension to Neutron, that creates a new resource: | ||
| Line 28: | Line 32: | ||
|} | |} | ||
| − | 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. |
| + | |||
| + | An alternative to the Parent Port UUID - could be to store the UUID of a Neutron Router that is created when the prefix is delegated, and ensure that the Neutron Router has a port created on the subnet that is a /128 address. | ||
Latest revision as of 14:11, 5 November 2014
Etherpad
Kilo - https://etherpad.openstack.org/p/neutron-kilo-prefix-delegation
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.
An alternative to the Parent Port UUID - could be to store the UUID of a Neutron Router that is created when the prefix is delegated, and ensure that the Neutron Router has a port created on the subnet that is a /128 address.
