[RFE] Include neutron CLI floatingip port-forwarding support

[varocho]

The floating ip port-forwarding is supported since Rocky by neutron API:

https://developer.openstack.org/api-ref/network/v2/index.html?expanded=create-port-forwarding-detail#floating-ips-port-forwarding

but the neutron client does not include this option yet.
Also floatingip-update method is missing.

It should include an option similar to this for floatingip *-create/*-update

$ neutron floatingip-create <network> --port-forwarding protocol=tcp,internal_port_id=<neutron_port_id>,internal_port=<network_port>,external_port=<network_port>

You should be able to repeat --port-forwarding several times

Also for floatingip-update with and extra option:
--port-forwarding clean

To remove the current port-forwarding rules list.

* Version: OpenStack Rocky

[Boden R (boden)]

It's not clear to me if we should treat this as an "RFE" or a "bug".
Going to ask a driver team member.

[Lajos Katona (lajos-katona)]

I suppose we should change neutronclient to openstackclient, am I right? As I know neutronclient (the old component CLIs) were deprecated in Rocky as well.

[varocho (alvarosimon)]

Yes it should be the openstackclient, neutron client is deprecated.
It should be included within "openstack floating ip create/set" options

[Slawek Kaplonski (slaweq)]

If we are talking about OSC, we should be good to go to add such feature there. I don't see anything what could block this.

[Akihiro Motoki (amotoki)]

Yeah, this fits OSC and OpenStack SDK repositories.

Related to this, there is a thing to be discussed. OSC transition guideline in the neutronclient contributor guide [1] categorizes networking commands into several groups ("Core", "Extension" and "Others"). "Core" is defined as "network resources that provide core neutron project features (e.g. network, subnet, port, etc.)" and "Extension" is defined as "advanced features in the neutron project (e.g. trunk, etc.) or advanced services in separate projects (FWaaS, LBaaS, VPNaaS, dynamic routing, etc.)". This means features in "neutron" repo spread "Core" (OSC repo) and "Extension" (OSC plugin in neutronclient repo). This is confusing. My idea is to implement all features in "neutron" repo into OSC (and OpenStack SDK).

[1] "Where does my CLI belong?" in https://docs.openstack.org/python-neutronclient/latest/contributor/transition_to_osc.html#developer-guide

[Miguel Lavalle (minsel)]

This RFE really should be filed in python-openstackclient and openstack/openstacksdk. I filed a story there: https://storyboard.openstack.org/#!/story/2004924. We will keep the RFE open in Neutron to track the activity in the clients

[LIU Yulong (dragon889)]

Patches:
https://review.openstack.org/#/c/650062/
https://review.openstack.org/#/c/650063/

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstacksdk 0.28.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-openstackclient 4.0.0 release.

[Dr. Jens Harbott (j-harbott)]

I think it would be great to add some documentation from the user pov to neutron, I only found the admin docs describing how to enable the extension: https://docs.openstack.org/neutron/rocky/admin/config-fip-port-forwardings.html

Something similar to http://www.panticz.de/openstack-floating-ip-port-forward maybe.