Red Hat Bugzilla – Bug 1266104
OSP director should support Neutron QoS
Last modified: 2016-04-07 17:40:03 EDT
Description of problem: As described in [1], a new Neutron QoS feature is introduced with RHEL OSP 8. We need to make sure several configuration changes are applied by default from director to make sure the feature is usable. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1093829
notes: for controller, I mean "where neutron-server runs" for networker, I mean, "where the neutron-l3-agent and dhcp agents run" for compute, I mean, "where nova compute runs". Sorry for the excessive details, but I'm still unfamiliar about how OSPd deploys. So, in the compute and networker nodes: * /etc/neutron/plugins/ml2/openvswitch_agent.ini [agent] extensions = qos If SR-IOV is enabled: * /etc/neutron/plugins/ml2/sriov_agent.ini [agent] extensions = qos in the controller node (could be in the same host as the networker): * /etc/neutron/neutron.conf [DEFAULT] add "qos" to the comma separated list of service_plugins option. There generally we have router, firewall, lbaas, etc... (add qos). * /etc/neutron/plugins/ml2/ml2_conf.ini [ml2] extension_drivers = qos # here we generally have port_security too "port_security, qos" @ihar, could you help me review what I'm saying here ^ ? Thanks, Miguel Ángel.
All said in comment #3 is correct. I would only avoid referring to nodes but instead talk about services, but that's just a stylistic thing for better understanding.
The bug moved to QA but it's not clear whether all the pieces have been merged.
Verified with openstack-tripleo-heat-templates-0.8.8-2.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0604.html