[RFE] Include neutron CLI floatingip port-forwarding support

Bug #1811352 reported by varocho on 2019-01-11
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Wishlist
LIU Yulong

Bug Description

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

varocho (alvarosimon) on 2019-01-11
description: updated
Boden R (boden) wrote :

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

Boden R (boden) on 2019-01-14
summary: - Include neutron CLI floatingip port-forwarding support
+ [RFE] Include neutron CLI floatingip port-forwarding support
tags: added: rfe
Lajos Katona (lajos-katona) wrote :

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) wrote :

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

Miguel Lavalle (minsel) on 2019-01-31
Changed in neutron:
importance: Undecided → Wishlist
importance: Wishlist → Medium
importance: Medium → Wishlist
tags: added: rfe-triaged
removed: rfe
Slawek Kaplonski (slaweq) wrote :

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) wrote :

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) wrote :

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) on 2019-02-27
Changed in neutron:
assignee: nobody → LIU Yulong (dragon889)
Akihiro Motoki (amotoki) on 2019-03-01
tags: added: rfe-approved
removed: rfe-triaged
LIU Yulong (dragon889) wrote :
Changed in neutron:
status: New → In Progress

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers