openstack team mailing list archive

[Salman Malik <salmanmk@xxxxxxxx>]

Dan, Salavatore and others, your input is sought here. Can any one provide little explanation please?

From: salmanmk@xxxxxxxx
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: OpenStack Quantum plugins
Date: Thu, 26 Apr 2012 19:55:20 +0000





Hi All,



I am trying to learn the functionality of Quantum plugins used in 
OpenStack. I have read through the Quantum Admin Guide and had few 
basic/quick question about quantum and OVS interaction with it:




1) OVS can have ports in which vNICS can be plugged, so why does it need
 to use an integration bridge for connecting all VMs on the same node to
 a network?



2) The OVS quantum plugin seems to implement the core API functions and 
(viewing the code) I concluded that it just makes maintains the logical 
mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this 
mapping implemented on the actual ports of OVS? Is it the OVS quantum 
agent responsible for directing the packets to correct input/output 
ports based on the updates that it gets from the database?



3) The quantum admin guide says that the nova client will be the main
 user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens.

Thanks,
Salman

PS: What is the purpose of Quantum Manager in this architecture and where should I look for its code?