Bug 1463838 - [RFE] Guaranteed minimum bandwidth
Summary: [RFE] Guaranteed minimum bandwidth
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: Upstream M2
: 16.0 (Train on RHEL 8.1)
Assignee: smooney
QA Contact: James Parker
URL:
Whiteboard:
: 1396265 (view as bug list)
Depends On:
Blocks: 1235009 1281573 1416067 1419948 1419954 1476902 1624465 1634058 1669584 1769723 1780733 1991746
TreeView+ depends on / blocked
 
Reported: 2017-06-21 21:01 UTC by JP Jung
Modified: 2022-08-10 15:20 UTC (History)
28 users (show)

Fixed In Version: openstack-nova-20.0.1-0.20191025043858.390db63.el8ost
Doc Type: Technology Preview
Doc Text:
In Red Hat OpenStack Platform 16.0, it is now possible to specify QoS minimum bandwidth rules when creating network interfaces. This feature ensures that the instance is guaranteed a specified portion of a network's available bandwidth. Currently, the only supported operations are resize and cold migrate. For guidance on creating a guaranteed minimum bandwidth QoS policy, see https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/networking_guide/sec-qos#guaranteed-min-bw. Note that some of the configuration requires directly editing OpenStack Networking (neutron) initialization files, as heat parameters are not yet available. For guidance on creating an instance that requests a guaranteed minimum bandwidth, see https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/instances_and_images_guide/ch-manage_instances#section-guaranteed-min-bw
Clone Of:
: 1634058 1780733 (view as bug list)
Environment:
Last Closed: 2020-02-06 14:37:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 652608 0 'None' MERGED Server move operations with ports having resource request 2021-02-18 11:38:18 UTC
Red Hat Issue Tracker OSP-6958 0 None None None 2022-08-10 15:20:01 UTC
Red Hat Product Errata RHEA-2020:0283 0 None None None 2020-02-06 14:39:51 UTC

Internal Links: 1788974

Description JP Jung 2017-06-21 21:01:52 UTC
Description of problem:

* Some VNF requires the use of SRIOV for dataplane interfaces, specifying also a BW for that interface. The BW required for each interface is a requirement specified in the VNF descriptor.
* PCI SRIOV allows multiplexing a single physical interface into several virtual interfaces called Virtual Functions (VF) or SRIOV interfaces. This means that from a single 10G physical interface we should be able to split it in several virtual functions each one consuming a different BW:
    * Example 1: 4 virtual functions with 5Gbps, 2Gbps, 2Gbps and 1Gbps
    * Example 2: 10 virtual functions, each one with 1Gbps
* The number of VF configured in a physical interface can be high, for instance 64, but the number of actually used VF in a physical interface depends on the actual BW reserved for each VF and the total BW of the physical interface.
* When searching a host to deploy a VM, nova scheduler should take into account the amount of BW reserved by the previous VMs on each physical interface. Today, BW is not taken into consideration.
* Moreover, BW occupied on each physical interface is an important driver for host selection. It might make sense for nova to have some policy that prefers deploying on a host whose physical interfaces have less available BW in order to make a better use of the network resources.

Comment 2 Stephen Gordon 2017-11-22 19:14:40 UTC
I think we still need a deeper discussion on this, unfortunately not anything happening from a Compute POV for Queens/RHOSP 13.

Comment 3 Franck Baudin 2017-12-04 12:17:23 UTC
This is part of RHOSP14 QoS EPIC, that will be internally available before the end of the calendar year.

Comment 12 Erwan Gallen 2019-05-15 13:27:30 UTC
*** Bug 1396265 has been marked as a duplicate of this bug. ***

Comment 27 errata-xmlrpc 2020-02-06 14:37:21 UTC
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://access.redhat.com/errata/RHEA-2020:0283


Note You need to log in before you can comment on or make changes to this bug.