[tacker][neutron] Need help in setting up QOS for Neutron Service in Devstack CI Job

Patil, Tushar Tushar.Patil at nttdata.com
Mon Apr 13 00:23:20 UTC 2020

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

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://review.opendev.org/#/c/717530/18

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.

More information about the openstack-discuss mailing list