Neutron/Quantum-floating-ips - Revision history

ThierryCarrez: ThierryCarrez moved page Quantum/Quantum-floating-ips to Neutron/Quantum-floating-ips

2013-06-21T15:54:50Z

ThierryCarrez moved page Quantum/Quantum-floating-ips to Neutron/Quantum-floating-ips

Corvus at 21:38, 16 February 2013

2013-02-16T21:38:21Z

Gongysh at 03:42, 30 August 2012

2012-08-30T03:42:59Z

AkihiroMotoki at 05:50, 9 July 2012

2012-07-09T05:50:53Z

Gongysh at 02:58, 8 July 2012

2012-07-08T02:58:53Z

Gongysh at 02:51, 8 July 2012

2012-07-08T02:51:25Z

Gongysh at 02:50, 8 July 2012

2012-07-08T02:50:41Z

Gongysh at 02:35, 8 July 2012

2012-07-08T02:35:46Z

Gongysh at 01:43, 8 July 2012

2012-07-08T01:43:37Z

Gongysh at 01:28, 8 July 2012

2012-07-08T01:28:48Z

New page

__NOTOC__
= Quantum Floating IPs =

== Summary ==

Nova has a concept of Fixed IPs and Floating IPs. Fixed IPs are assigned to an instance on creation and stay the same until the instance is explicitly terminated. Floating ips are ip addresses that can be dynamically associated with an instance. This address can be disassociated and associated with another instance at any time.

We can see how the Floating IPs are implemented by nova at:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/e93514d3-c4f0-4aa0-8844-497f370090f5/entry/openstack_s_floating_ips7?lang=en

This page describes how the Floating Ip is implemented in quantum.

== User stories ==
* create IP ranges under a certain group, only available for admin role.
* allocate an floating IP to a certain tenant, only available for admin role.
* deallocate an floating IP from a certain tenant
* associate an floating IP to a given instance
* disassociate an floating IP from a certain instance
== Assumptions ==

N/A

== Design ==

== Implementation ==

1. Nova network API floating features
2. Quantum client floating features, just like the one in nova client
3. Quantum API for floating features
4. Agent to implement IP table rules and bind floating IP to public interface.

== Unresolved issues ==

1. Can a Floating IP be an IPv6 address?

----
[[Category:Spec]]

@@ Line 1: / Line 1: @@
 = Quantum Floating IPs =
 [deprecated by https://blueprints.launchpad.net/quantum/+spec/quantum-l3-fwd-nat]
@@ Line 33: / Line 32: @@
 == Design ==
 === Overview ===
-[[Image:Quantum$$Quantum-floating-ips$floating-ips.png]]
+[[Image:floating-ips.png]]
 Just as shown by above fiture, we will have nova-network-api to support nova client floating commands. nova-network-api will invoke quantum cli lib to interactive with quantum server via API. The data about floating IPs will be store in to quantum DB. Quantum Agent, which is running on compute host will enforce the floating IP.

@@ Line 37: / Line 37: @@
 === floating-ip top level resource ===
 * create a range of floating ips
-−
 POST /v2.0/floating-ips/
 * list floating ips under certain tenant or all tenants
-−
 GET /v2.0/floating-ips/
 * delete a floating ip
-−
 DELETE /v2.0/floating-ips/{ipid}
 * allocate a floating IP to a certain tenant from a given IP pool
-POST /v2.0/floating-ips/action <<BR>> {"allocate": {"tenant_id": "xxxx"}} Note: tenant_id can be got from context if it is missing.
+ Note: tenant_id can be got from context if it is missing.
 * deallocate one floating IP from a certain tenant
-POST /v2.0/floating-ips/{ipid}/action<<BR>> {"deallocate": {"tenant_id": "xxx"}} Note: tenant_id can be got from context if it is missing.
+ Note: tenant_id can be got from context if it is missing.
 * associate a floating IP to a certain instance
-−
-POST /v2.0/floating-ips/{ipid}/action<<BR>> {"associate": {"instance_id": "xxx", "interface": "eth0"}}
+<pre><nowiki>
 * disassociate a floating IP from a certain instance
 === database table ===

@@ Line 90: / Line 90: @@
 | N
 | RUD
-| True
+| -
 |-
 | host

@@ Line 37: / Line 37: @@
 === floating-ip top level resource ===
 * create a range of floating ips
 POST /v2.0/floating-ips/
 * list floating ips under certain tenant or all tenants
 GET /v2.0/floating-ips/
 * delete a floating ip
 DELETE /v2.0/floating-ips/{ipid}
 * allocate a floating IP to a certain tenant from a given IP pool
 POST /v2.0/floating-ips/action <<BR>>
-{"allocate": {"tenant_id": "xxxx"}}
+POST /v2.0/floating-ips/action <<BR>> {"allocate": {"tenant_id": "xxxx"}} Note: tenant_id can be got from context if it is missing.
 Note: tenant_id can be got from context if it is missing.
 * deallocate one floating IP from a certain tenant
 POST /v2.0/floating-ips/{ipid}/action<<BR>>
-{"deallocate": {"tenant_id": "xxx"}}
+POST /v2.0/floating-ips/{ipid}/action<<BR>> {"deallocate": {"tenant_id": "xxx"}} Note: tenant_id can be got from context if it is missing.
 Note: tenant_id can be got from context if it is missing.
 * associate a floating IP to a certain instance
 POST /v2.0/floating-ips/{ipid}/action<<BR>>
-{"associate": {"instance_id": "xxx", "interface": "eth0"}}
+POST /v2.0/floating-ips/{ipid}/action<<BR>> {"associate": {"instance_id": "xxx", "interface": "eth0"}}
 * disassociate a floating IP from a certain instance
 POST /v2.0/floating-ips/{ipid}/action<<BR>>
-{"disassociate": {"instance_id": "xxx"}}
+POST /v2.0/floating-ips/{ipid}/action<<BR>> {"disassociate": {"instance_id": "xxx"}}
 === database table ===
 * floating_ips
 {| border="1" cellpadding="2" cellspacing="0"
 | attribute
@@ Line 99: / Line 106: @@
 | group
 | str
-| N
+| Y
 | CR
 | -

@@ Line 44: / Line 44: @@
 * allocate a floating IP to a certain tenant from a given IP pool
-POST /v2.0/floating-ips/action
+POST /v2.0/floating-ips/action <<BR>>
 {"allocate": {"tenant_id": "xxxx"}}
 Note: tenant_id can be got from context if it is missing.
 * deallocate one floating IP from a certain tenant
-POST /v2.0/floating-ips/{ipid}/action
+POST /v2.0/floating-ips/{ipid}/action<<BR>>
 {"deallocate": {"tenant_id": "xxx"}}
 Note: tenant_id can be got from context if it is missing.
 * associate a floating IP to a certain instance
-POST /v2.0/floating-ips/{ipid}/action
+POST /v2.0/floating-ips/{ipid}/action<<BR>>
 {"associate": {"instance_id": "xxx", "interface": "eth0"}}
 * disassociate a floating IP from a certain instance
-POST /v2.0/floating-ips/{ipid}/action
+POST /v2.0/floating-ips/{ipid}/action<<BR>>
 {"disassociate": {"instance_id": "xxx"}}
 == Unresolved issues ==
 * Can a Floating IP be an IPv6 address?

← Older revision	Revision as of 15:54, 21 June 2013
(No difference)

@@ Line 1: / Line 1: @@
 __NOTOC__
 = Quantum Floating IPs =
 == Summary ==
 Nova has a concept of Fixed IPs and Floating IPs. Fixed IPs are assigned to an instance on creation and stay the same until the instance is explicitly terminated. Floating ips are ip addresses that can be dynamically associated with an instance. This address can be disassociated and associated with another instance at any time.

@@ Line 1: / Line 1: @@
 __NOTOC__
 = Quantum Floating IPs =
 == Summary ==
 Nova has a concept of Fixed IPs and Floating IPs. Fixed IPs are assigned to an instance on creation and stay the same until the instance is explicitly terminated. Floating ips are ip addresses that can be dynamically associated with an instance. This address can be disassociated and associated with another instance at any time.
-We can see how the Floating IPs are implemented by nova at:
+We can see how the Floating IPs are implemented by nova at: https://www.ibm.com/developerworks/mydeveloperworks/blogs/e93514d3-c4f0-4aa0-8844-497f370090f5/entry/openstack_s_floating_ips7?lang=en
-This page describes how the Floating Ip is implemented in quantum.
+This page describes how this feature is implemented in quantum.
 == User stories ==
@@ Line 17: / Line 14: @@
 * associate an floating IP to a given instance
 * disassociate an floating IP from a certain instance
 == Assumptions ==
-N/A
+== Components to consider ==
-== Design ==
+In addition, we need to integrate:
-== Implementation ==
+* Nova network API floating features
-. Nova network API floating features
+== Design ==
 == Unresolved issues ==
+* Can a Floating IP be an IPv6 address?
 ----
 [[Category:Spec]]