Open Stack

>> So adding "neutron-qos" to enabled services on all hosts should be enough.
>> Please check how it is done e.g. in neutron-tempest-plugin's jobs at [1].

> Yes, that's one option but from the beginning we were installing neutron legacy way. I will check this option and see if it solves my problem.

QOS was getting overwritten during the post-config phase of tacker in which it was explicitly setting [ml2].extension_drivers to port_security.

I have fixed this issue in PS 22 [1] and now I can see qos is configured in Neutron as expected.

[1] : https://review.opendev.org/#/c/717530

Regards,
Tushar Patil


________________________________________
From: Patil, Tushar <Tushar.Patil at nttdata.com>
Sent: Monday, April 13, 2020 4:32 PM
To: Slawek Kaplonski
Cc: openstack-discuss at lists.openstack.org
Subject: Re: [tacker][neutron] Need help in setting up QOS for Neutron Service in Devstack CI Job

Hi,

> So adding "neutron-qos" to enabled services on all hosts should be enough.
> Please check how it is done e.g. in neutron-tempest-plugin's jobs at [1].
Yes, that's one option but from the beginning we were installing neutron legacy way. I will check this option and see if it solves my problem.

Thank you.

Regards,
tpatil

________________________________________
From: Slawek Kaplonski <skaplons at redhat.com>
Sent: Monday, April 13, 2020 3:12 PM
To: Patil, Tushar
Cc: openstack-discuss at lists.openstack.org
Subject: Re: [tacker][neutron] Need help in setting up QOS for Neutron Service in Devstack CI Job

Hi,

I'm not sure what exactly removes "qos" from extension_drivers list but in
Neutron we have simple plugin to enable qos. So adding "neutron-qos" to enabled
services on all hosts should be enough.
Please check how it is done e.g. in neutron-tempest-plugin's jobs at [1].

[1] https://urldefense.com/v3/__https://github.com/openstack/neutron-tempest-plugin/blob/master/.zuul.yaml*L101__;Iw!!AKgNyAfk550h-spHnEo!JN727DQwgeQqFsji-emGQgCsGXelhfiC-WzvhtCyTWlR5F61mpjaLfBF80-R8b4Vu9g$

On Mon, Apr 13, 2020 at 12:23:20AM +0000, Patil, Tushar wrote:
> Hi OpenStackers,
>
> In tacker project, we need to setup QOS plugin in devstack CI job (tacker-functional-devstack-multinode-python3) to run our functional tests.
> I have checked what config options are needed to enable QOS in neutron and updated .zuul.yaml accordingly as you can see in patch [1] PS 18.
>
> Mainly, I have enabled following environment variables in .zuul.yaml:-
> Q_SERVICE_PLUGIN_CLASSES: router,neutron.services.metering.metering_plugin.MeteringPlugin,networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin,neutron.services.qos.qos_plugin.QoSPlugin,
> Q_ML2_PLUGIN_EXT_DRIVERS: port_security,qos
> L2_AGENT_EXTENSIONS: qos
> NEUTRON_PORT_SECURITY: False
>
> Problem:
> Main point is service_plugins config option is configured with qos but the [ml2].extension drivers doesn't include qos.
> I hav set qos" in  Q_ML2_PLUGIN_EXT_DRIVERS but still it's not set in the /etc/neutron/plugins/ml2/ml2_conf.ini in Section [ml2].extension_drivers on the controller node and because of this reason the q-svc service is not starting on the controller node.
>
> I have scoured devstack.log to find out where it's overwriting extension_drivers with "port_security" instead of "port_security, qos" but I couldn't find one.
>
> On the controller node, we can see this log statement:-
>   2020-04-10 13:07:23.388678 | controller | +   lib/neutron_plugins/ml2:populate_ml2_config:59 :   iniset /etc/neutron/plugins/ml2/ml2_conf.ini ml2 extension_drivers port_security,qos
>
> It's clear from above log, qos is set properly but where exactly it's overwritten with just port_security or qos is removed is not clear to me.
>
> Any pointers where I can debug to solve this problem or how to set QOS correctly?
>
> [1]: https://urldefense.com/v3/__https://review.opendev.org/*/c/717530/18__;Iw!!AKgNyAfk550h-spHnEo!JN727DQwgeQqFsji-emGQgCsGXelhfiC-WzvhtCyTWlR5F61mpjaLfBF80-RRQzEWuo$
>
> Regards,
> tpatil
> Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.
>

--
Slawek Kaplonski
Senior software engineer
Red Hat

Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.

Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.