[openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class
Miguel Angel Ajo Pelayo
majopela at redhat.com
Fri Apr 8 13:17:15 UTC 2016
In the context of  (generic resource pools / scheduling in nova) and
 (minimum bandwidth guarantees -egress- in neutron), I had a talk a few
weeks ago with Jay Pipes,
The idea was leveraging the generic resource pools and scheduling
mechanisms defined in  to find the right hosts and track the total
available bandwidth per host (and per host "physical network"), something
in neutron (still to be defined where) would notify the new API about the
total amount of "NIC_BW_KB" available on every host/physnet.
That part is quite clear to me,
From  I'm not sure which blueprint introduces the ability to schedule
based on the resource allocation/availability itself,
("resource-providers-scheduler" seems more like an optimization to the
schedule/DB interaction, right?)
And, that brings me to another point: at the moment of filtering hosts,
nova I guess, will have the neutron port information, it has to somehow
identify if the port is tied to a minimum bandwidth QoS policy.
That would require identifying that the port has a "qos_policy_id"
attached to it, and then, asking neutron for the specific QoS policy ,
then look out for a minimum bandwidth rule (still to be defined), and
extract the required bandwidth from it.
That moves, again some of the responsibility to examine and understand
external resources to nova.
Could it make sense to make that part pluggable via stevedore?, so we
would provide something that takes the "resource id" (for a port in this
case) and returns the requirements translated to resource classes
(NIC_BW_KB in this case).
Miguel Ángel Ajo
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev