Difference between revisions of "Libvirt-direct-network"
(Created page with "=== Adding libvirt network interface to VIF Driver === This Wiki target is to clarify what is proposed in the [https://blueprints.launchpad.net/nova/+spec/libvirt-direct-netwo...") |
|||
| Line 2: | Line 2: | ||
This Wiki target is to clarify what is proposed in the [https://blueprints.launchpad.net/nova/+spec/libvirt-direct-network blueprint]. | This Wiki target is to clarify what is proposed in the [https://blueprints.launchpad.net/nova/+spec/libvirt-direct-network blueprint]. | ||
| − | The existing VIF drivers usually use one physical Interface | + | The existing VIF drivers usually use one physical Interface to connect to the network.<br /> |
When there is a need to use more than one Interface (such when using SR-IOV Virtual Functions) the VIF Driver can configure the vNIC | When there is a need to use more than one Interface (such when using SR-IOV Virtual Functions) the VIF Driver can configure the vNIC | ||
Revision as of 05:52, 20 May 2013
Contents
Adding libvirt network interface to VIF Driver
This Wiki target is to clarify what is proposed in the blueprint.
The existing VIF drivers usually use one physical Interface to connect to the network.
When there is a need to use more than one Interface (such when using SR-IOV Virtual Functions) the VIF Driver can configure the vNIC
with the device name.
A better solution is to create a Network pool as described here : http://libvirt.org/formatnetwork.html#examplesDirect
Configuring the vNIC
For Configuration - The Network pool name should be provided to the VIF Driver.
On the first phase - It will be provided by adding a configuration variable to the nova.conf named physical_network.
Next Phase should be to get it from Nova through the mapping Dictionary.
Creation of the Network Pool
The creation of the Network Pool will be done according to Physical Network mapping to physical interface(s) either Manually (First phase) or by the Quantum Plugin Agent.
Implementation
The Implementation is using LibvirtGenericVIFDriver
You can watch the review process here: https://review.openstack.org/#/c/29048/
