Jump to: navigation, search

Difference between revisions of "Quantum-802-1qbh-scheduler"

 
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 +
* '''Launchpad Entry''': https://code.launchpad.net/~cisco-openstack/nova/quantum-802-1qbh-scheduler
 +
* '''Created''': Aug 10 2011
 +
 +
= Network Refactoring =
 +
 +
Sumit Naiksatam <[[mailto:snaiksat@cisco.com]]> <<BR>>
 +
 +
== Abstract ==
 +
 
In a cluster comprising of 802.1Qbh-based systems, the decision of where to place the VM depends on the availability of a "dynamic" nic on a patricular system (to which the VIF plugs into). This availability information can be obtained from Quantum network service (supporting the 802.1Qbh extensions). The scheduler interfaces with Quantum using a Quantum client library, and obtains the "dynamic" nic and hostname information. The VM is then scheduled on this host.
 
In a cluster comprising of 802.1Qbh-based systems, the decision of where to place the VM depends on the availability of a "dynamic" nic on a patricular system (to which the VIF plugs into). This availability information can be obtained from Quantum network service (supporting the 802.1Qbh extensions). The scheduler interfaces with Quantum using a Quantum client library, and obtains the "dynamic" nic and hostname information. The VM is then scheduled on this host.

Revision as of 19:28, 10 August 2011

Network Refactoring

Sumit Naiksatam <[[1]]> <
>

Abstract

In a cluster comprising of 802.1Qbh-based systems, the decision of where to place the VM depends on the availability of a "dynamic" nic on a patricular system (to which the VIF plugs into). This availability information can be obtained from Quantum network service (supporting the 802.1Qbh extensions). The scheduler interfaces with Quantum using a Quantum client library, and obtains the "dynamic" nic and hostname information. The VM is then scheduled on this host.