Devstack - Can no longer enable qos with neutron-qos

[Martin André]

The neutron-qos functions were moved away from neutron devstack plugin with [1] and added to devstack directly with [2] and [3]. However, when one would previously enable neutron-qos in devstack with `neutron-qos`, this is no longer the case as the functions were added to the neutron-legacy file that is only sourced when legacy (quantum era) neutron services are enabled.

[1] https://review.opendev.org/#/q/I7b70d6281d551a88080c6e727e2485079ba5c061
[2] https://review.opendev.org/#/q/I48f65d530db53fe2c94cad57a8072e1158d738b0
[3] https://review.opendev.org/#/q/Icf459a2f8c6ae3c3cb29b16ba0b92766af41af30

[Bence Romsics (bence-romsics)]

Hi,

There's a long history here, but I would actually recommend that you switch back to using the legacy devstack plugin.

The new neutron devstack plugin AFAICT worked quite well in a simple dev environment. Despite the legacy one being deprecated for a long time, the work on the new one stalled and it never completely replaced the legacy plugin (mostly for use cases in the gate). For a time both were maintained. And at some point we acknowledged that the new devstack plugin will never be completed and un-deprecated the legacy plugin:

https://review.opendev.org/c/openstack/devstack/+/704829

Some of these changes were clearly unexpected and probably we could have done a better job communicating which plugin is the preferred. And now maybe we should deprecate the new plugin. I think I'll ask the team about that on our next meeting.

But until then the best I can recommend is that you switch back to using the legacy devstack plugin.

Regards,
Bence

[Bence Romsics (bence-romsics)]

The neutron team discussed this topic on its last meeting and the agreement was that use of the legacy devstack plugin is preferred and the new plugin will be likely deprecated. So please switch to the legacy plugin, that should work. Sorry for not documenting this better, soon we will have a deprecation message in the new plugin, helping with this, I hope.

https://meetings.opendev.org/meetings/networking/2022/networking.2022-01-04-14.04.log.html#l-47