Difference between revisions of "Neutron/Quantum-floating-ips"
< Neutron
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
= Quantum Floating IPs = | = Quantum Floating IPs = | ||
| − | |||
== Summary == | == 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. | 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 |
| − | https://www.ibm.com/developerworks/mydeveloperworks/blogs/e93514d3-c4f0-4aa0-8844-497f370090f5/entry/openstack_s_floating_ips7?lang=en | ||
| − | This page describes how | + | This page describes how this feature is implemented in quantum. |
== User stories == | == User stories == | ||
| Line 17: | Line 14: | ||
* associate an floating IP to a given instance | * associate an floating IP to a given instance | ||
* disassociate an floating IP from a certain instance | * disassociate an floating IP from a certain instance | ||
| + | |||
== Assumptions == | == Assumptions == | ||
| + | N/A | ||
| − | + | == Components to consider == | |
| + | To implement floating IPs in quantum, we have to consider: | ||
| + | |||
| + | * Quantum client floating features, just like the one in nova client | ||
| + | * Quantum API for floating features | ||
| + | * Agent to implement IP table rules and bind floating IP to public interface. | ||
| − | + | In addition, we need to integrate: | |
| − | + | * Nova network API floating features | |
| − | + | == Design == | |
| − | |||
| − | |||
| − | |||
== Unresolved issues == | == Unresolved issues == | ||
| − | + | * Can a Floating IP be an IPv6 address? | |
| − | |||
---- | ---- | ||
[[Category:Spec]] | [[Category:Spec]] | ||
Revision as of 01:43, 8 July 2012
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 this feature 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
Components to consider
To implement floating IPs in quantum, we have to consider:
- Quantum client floating features, just like the one in nova client
- Quantum API for floating features
- Agent to implement IP table rules and bind floating IP to public interface.
In addition, we need to integrate:
- Nova network API floating features
Design
Unresolved issues
- Can a Floating IP be an IPv6 address?
