yahoo-eng-team team mailing list archive

[Andreas Scheuring <andreas.scheuring@xxxxxxxxxx>]

Public bug reported:

Add support to allow nova scheduler place instances along available
neutron properties.

Use case: 
- Scheduling along physical network: A certain network (e.g. your fast 100Gbit network) is only available to a subset of the nodes (e.g. per rack).
- Schedulding along QoS attributes: Schedule instances along available bandwidth

Proposal:
Integration might be challenging, as also nova needs to be enhanced with a new filter. Ihar talked to nova folks (Nikola Dipanov, Jay Pipes, Sylvain) but they seemed not to be interested in fulfilling this need right now. However they have a vague idea of a scheduler hook to influence scheduling decisions.

Alternative to nova scheduler hook:
Today scheduling decision is made on resource data reported from nova-cpu to nova scheduler via the message bus. What would be required is a similar reporting from neutron-agent to nova-scheduler. However such a private path might be against the decoupling of nova and neutron, introduce new message topics and so on. 


Note: This bug is intended to track all information from Neutron side. It's not meant as a requirement against nova.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1515311

Title:
  Instance scheduling based on Neutron properties

Status in neutron:
  New

Bug description:
  Add support to allow nova scheduler place instances along available
  neutron properties.

  Use case: 
  - Scheduling along physical network: A certain network (e.g. your fast 100Gbit network) is only available to a subset of the nodes (e.g. per rack).
  - Schedulding along QoS attributes: Schedule instances along available bandwidth

  Proposal:
  Integration might be challenging, as also nova needs to be enhanced with a new filter. Ihar talked to nova folks (Nikola Dipanov, Jay Pipes, Sylvain) but they seemed not to be interested in fulfilling this need right now. However they have a vague idea of a scheduler hook to influence scheduling decisions.

  Alternative to nova scheduler hook:
  Today scheduling decision is made on resource data reported from nova-cpu to nova scheduler via the message bus. What would be required is a similar reporting from neutron-agent to nova-scheduler. However such a private path might be against the decoupling of nova and neutron, introduce new message topics and so on. 

  
  Note: This bug is intended to track all information from Neutron side. It's not meant as a requirement against nova.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1515311/+subscriptions