| 1 |
--- |
| 2 |
prelude: > |
| 3 |
Added support for floating IPs port forwarding. |
| 4 |
features: |
| 5 |
- | |
| 6 |
Support for floating IPs port forwarding has been added. |
| 7 |
|
| 8 |
* Users can now forward the traffic from a TCP/UDP/other protocol |
| 9 |
port of a floating IP address to a TCP/UDP/other protocol port |
| 10 |
associated to one of the fixed IP addresses of a Neutron port. |
| 11 |
* This is accomplished by associating ``port_forwarding`` |
| 12 |
sub-resources to floating IPs. |
| 13 |
* To create a ``port_forwarding``, the user specifies: a floating |
| 14 |
IP ID, the floating IP's ``external_port`` number, the Neutron |
| 15 |
port ID ``internal_port_id``, an ``internal_ip_address`` (one of |
| 16 |
the Neutron port's fixed IPs), the ``internal_port`` number and |
| 17 |
the ``protocol`` to be used (TCP or UDP for example). |
| 18 |
* CRUD operations for ``port_forwardings`` are implemented by a Neutron |
| 19 |
API extension and a service plugin. Please refer to the Neutron API |
| 20 |
reference documentation for details. |
| 21 |
* A user cannot create ``port_forwardings`` for a floating IP |
| 22 |
that is already associated with a Neutron port. |
| 23 |
* A floating IP can have many ``port_forwardings``. |
| 24 |
* Port forwardings can only be created for floating IPs that are |
| 25 |
managed by centralized routers in the network node: legacy, HA, |
| 26 |
DVR+HA. |