Hi Lajos,

Thanks for bringing it up, I moved the code here with the tests (tested locally).

https://review.opendev.org/c/openstack/python-neutronclient/+/960846

As a follow-up as well, the following removes the client code and tests from the original repository:

https://review.opendev.org/c/openstack/tap-as-a-service/+/960849

Thanks.

Mohammed

---

From: Lajos Katona <katonalala@gmail.com>
Sent: September 12, 2025 11:18 AM
To: Mohammed Naser <mnaser@vexxhost.com>
Cc: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>
Subject: Re: [neutron][taas][taap-as-a-service] moving client to seperate package

 

Hi,

We discussed this topic on the drivers meeting, see [1].

The team agreed to move the current CLI code to python-neutronclient.

Another point was to move all the remaining CLI code (mostly for Neutron Stadium projects) to OSC.

We will have some more discussion on this topic during the PTG, and I really hope that in the 

coming cycle we can work on it (perhaps even finish the full migration, but perhaps that is too optimistic...)

Best wishes

Lajos Katona (lajoskatona)

[1]: https://meetings.opendev.org/meetings/neutron_drivers/2025/neutron_drivers.2025-09-12-14.00.log.html#l-142

Lajos Katona <katonalala@gmail.com> ezt írta (időpont: 2025. szept. 11., Cs, 9:35):

Hi Mohammed,

The reason I think is that taas was not a Neutron Stadium project for years and the team obviously not allowed

CLI code to be merged to python-neutronclient or to python-openstackclient, and the cheapest solution at that time

was to have it in the server repository.

The x/networking-l2gw has similar setup and for the same reason I suppose.

As taas is under Neutron governance I suppose the CLI code can be moved to neutronclient

(https://opendev.org/openstack/python-neutronclient/src/branch/master/neutronclient/osc/v2 )

I can bring this topic to he Drivers meeting (I am not sure I can participated this week, but on a coming one )

Best wishes

Lajos Katona

Mohammed Naser <mnaser@vexxhost.com> ezt írta (időpont: 2025. szept. 10., Sze, 16:56):

Hi there,

It seems that at the moment, tap-as-a-service package contains both the
server and the client components, which means that if you are trying to
pull in the CLI components, you end up with Neutron as well, which is
quite heavy.

Is there a reason behind it that decision or is this something that
someone needs to get around doing but no one has?

Thanks,
Mohammed