Neutron/IPv6/PrefixDelegation - Revision history

Scollins at 14:11, 5 November 2014

2014-11-05T14:11:16Z

Scollins at 16:29, 20 March 2014

2014-03-20T16:29:28Z

Scollins: /* API Resource Design */

2014-03-20T16:22:48Z

‎API Resource Design

Scollins: /* Design */

2014-03-20T16:18:54Z

‎Design

Scollins at 16:17, 20 March 2014

2014-03-20T16:17:56Z

Scollins at 16:12, 20 March 2014

2014-03-20T16:12:32Z

Scollins: /* Design */

2014-03-20T16:11:19Z

‎Design

Scollins: Created page with "=== Prefix Delegation API Extension === This is an API extension to Neutron, to create IPv6 prefix delegation functionality in the Neutron API. https://blueprints.launchpad...."

2014-03-20T16:04:01Z

Created page with "=== Prefix Delegation API Extension === This is an API extension to Neutron, to create IPv6 prefix delegation functionality in the Neutron API. https://blueprints.launchpad...."

New page

=== 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

=== Design ===

← Older revision		Revision as of 14:11, 5 November 2014
Line 1:		Line 1:
		+	=== Etherpad ===
		+
		+	Kilo - https://etherpad.openstack.org/p/neutron-kilo-prefix-delegation
		+
	=== Prefix Delegation API Extension ===		=== Prefix Delegation API Extension ===

← Older revision		Revision as of 16:29, 20 March 2014
Line 29:		Line 29:

	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.		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.

← Older revision		Revision as of 16:22, 20 March 2014
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.

@@ Line 5: / Line 5: @@
 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:

← Older revision		Revision as of 16:17, 20 March 2014
Line 27:		Line 27:
	\| Child Subnet 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) 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.

@@ Line 9: / Line 9: @@
 One possible implementation is to create a new API Extension to Neutron, that creates a new resource:
-{| border="1" cellpadding="2" cellspacing="0"
+{| class="wikitable"
 | '''Resource'''
 |-

← Older revision		Revision as of 16:11, 20 March 2014
Line 6:		Line 6:

	=== Design ===		=== Design ===
		+
		+	One possible implementation is to create a new API Extension to Neutron, that creates a new resource:
		+
		+	{\| border="1" cellpadding="2" cellspacing="0"
		+	\| '''Resource'''
		+	\|-
		+	\| PrefixDelegation
		+	\|}
		+
		+	The PrefixDelegation resource would contain the following attributes:
		+
		+	{\| class="wikitable"
		+	\|-
		+	! PrefixDelegation
		+	\|-
		+	\| UUID
		+	\|-
		+	\| Parent Port UUID
		+	\|-
		+	\| Child Subnet UUID
		+	\|}