Difference between revisions of "Quantum-802-1qbh-scheduler"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | * '''Launchpad Entry''': https://code.launchpad.net/~cisco-openstack/nova/quantum- | + | * '''Launchpad Entry''': https://code.launchpad.net/~cisco-openstack/nova/802dot1qbh-quantum-support |
* '''Created''': Aug 10 2011 | * '''Created''': Aug 10 2011 | ||
| − | = Quantum-interfaced Scheduler to support 802. | + | = Quantum-interfaced Scheduler to support 802.1qbh = |
Sumit Naiksatam <[[mailto:snaiksat@cisco.com]]> <<BR>> | Sumit Naiksatam <[[mailto:snaiksat@cisco.com]]> <<BR>> | ||
| Line 11: | Line 11: | ||
== Abstract == | == Abstract == | ||
| − | In a cluster comprising of 802. | + | 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 hostname information. The VM is then scheduled on this host. On the Quantum side, a corresponding "dynamic" vnic is reserved for this VM, which is made available to the VIF driver on request. This scheduler is in fact not limited to 802.1qbh, and can be used as a generic Quantum-interfaced scheduler since it delegates the scheduling decision to Quantum. |
| + | |||
| + | == Design == | ||
| + | nova/scheduler/quantum_aware_scheduler.py implements this scheduler which communicates with the Quantum network service and obtain the hostname information on which to schedule the next instance. This information is obtained on the basis of the instance information (id, project_id, and user_id) information supplied by the scheduler to Quantum. | ||
| + | |||
| + | The following configuration needs to be added/edited to the /etc/nova/nova.conf file: | ||
| + | --scheduler_driver=nova.scheduler.quantum_aware_scheduler.[[QuantumScheduler]] | ||
| + | --quantum_host=<quantum_service_IP_ADDR> | ||
| + | --quantum_port=9696 | ||
Revision as of 08:39, 15 August 2011
- Launchpad Entry: https://code.launchpad.net/~cisco-openstack/nova/802dot1qbh-quantum-support
- Created: Aug 10 2011
Quantum-interfaced Scheduler to support 802.1qbh
Sumit Naiksatam <[[1]]> <
>
<<TableOfContents()>>
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 hostname information. The VM is then scheduled on this host. On the Quantum side, a corresponding "dynamic" vnic is reserved for this VM, which is made available to the VIF driver on request. This scheduler is in fact not limited to 802.1qbh, and can be used as a generic Quantum-interfaced scheduler since it delegates the scheduling decision to Quantum.
Design
nova/scheduler/quantum_aware_scheduler.py implements this scheduler which communicates with the Quantum network service and obtain the hostname information on which to schedule the next instance. This information is obtained on the basis of the instance information (id, project_id, and user_id) information supplied by the scheduler to Quantum.
The following configuration needs to be added/edited to the /etc/nova/nova.conf file: --scheduler_driver=nova.scheduler.quantum_aware_scheduler.QuantumScheduler --quantum_host=<quantum_service_IP_ADDR> --quantum_port=9696
