Public bug reported: Currently, Neutron supports the creation of network QoS policies and allows networks to be associated with them. Any port connected to such a network will automatically adopt the corresponding QoS policy (refer to this document https://docs.openstack.org/neutron/latest/admin/config- qos.html#:~:text=You%20can%20attach%20networks%20to%20a%20QoS%20policy.%20The%20meaning%20of%20this%20is%20that%20any%20compute%20port%20connected%20to%20the%20network%20will%20use%20the%20network%20policy%20by%20default%20unless%20the%20port%20has%20a%20specific%20policy%20attached%20to%20it for details).
We propose enhancing this functionality by introducing more granular, project-specific QoS controls. This new feature would enable the association of QoS policies with specific projects. As a result, all ports—whether newly created or existing—within a project would adopt the assigned policy live. This capability would empower teams and applications to better manage and optimize performance. We have already proposed similar ideas to the Cinder and Nova communities (see blueprints https://blueprints.launchpad.net/cinder/+spec/enhanced-granularity-and- live-application-of-frontend-qos-policies and https://blueprints.launchpad.net/nova/+spec/enhanced-granularity-and- live-application-of-qos) and received positive feedback. We aim to extend this functionality to Neutron as well, enabling per-project QoS control across all critical resources—CPU, memory, disk, and network—for instances. ** Affects: neutron Importance: Undecided Assignee: Mengyang Zhang (mzhang741) Status: New ** Tags: rfe ** Summary changed: - Project-Specific QoS Controls for Granular Resource Management + [RFE] Project-Specific QoS Controls for Granular Resource Management ** Changed in: neutron Assignee: (unassigned) => Mengyang Zhang (mzhang741) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2102184 Title: [RFE] Project-Specific QoS Controls for Granular Resource Management Status in neutron: New Bug description: Currently, Neutron supports the creation of network QoS policies and allows networks to be associated with them. Any port connected to such a network will automatically adopt the corresponding QoS policy (refer to this document https://docs.openstack.org/neutron/latest/admin/config- qos.html#:~:text=You%20can%20attach%20networks%20to%20a%20QoS%20policy.%20The%20meaning%20of%20this%20is%20that%20any%20compute%20port%20connected%20to%20the%20network%20will%20use%20the%20network%20policy%20by%20default%20unless%20the%20port%20has%20a%20specific%20policy%20attached%20to%20it for details). We propose enhancing this functionality by introducing more granular, project-specific QoS controls. This new feature would enable the association of QoS policies with specific projects. As a result, all ports—whether newly created or existing—within a project would adopt the assigned policy live. This capability would empower teams and applications to better manage and optimize performance. We have already proposed similar ideas to the Cinder and Nova communities (see blueprints https://blueprints.launchpad.net/cinder/+spec/enhanced-granularity- and-live-application-of-frontend-qos-policies and https://blueprints.launchpad.net/nova/+spec/enhanced-granularity-and- live-application-of-qos) and received positive feedback. We aim to extend this functionality to Neutron as well, enabling per-project QoS control across all critical resources—CPU, memory, disk, and network—for instances. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2102184/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
