openstack/neutron
Code Issues Proposed changes

Add release note for port forwardings.

Browse Source 
This patch adds a release note for the floating IPs port forwarding
functionality.

Change-Id: I2e0069148cd2551d4534d8a2fd8799f432ffb5e3
Partially-Implements: blueprint port-forwarding
Partial-Bug: #1491317
This commit is contained in:
Miguel Lavalle 2018-08-01 16:15:09 -05:00
parent 765fd4d7b8
commit 66c8ed9c97
1 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
releasenotes/notes/floatingips-port-forwarding-65efd8c17a16dffc.yaml Normal file
View File

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