[openstack-dev] [nova][neutron] SR-IOV networking patches available
Robert Li (baoli)
baoli at cisco.com
Wed Feb 26 14:45:07 UTC 2014
Hi,
The following two Work In Progress patches are available for end-to-end SR-IOV networking:
nova client: https://review.openstack.org/#/c/67503/
nova: https://review.openstack.org/#/c/67500/
Please check the commit messages for how to use them.
Neutron changes required to support SR-IOV have already been merged. Many thanks to the developers working on them and having them merged in a very short time! They are:
https://blueprints.launchpad.net/neutron/+spec/vif-details
https://blueprints.launchpad.net/neutron/+spec/ml2-binding-profile
https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type
The above patches combined can be used to develop a neutron plugin that supports SR-IOV. Please note that Although the nova patches are WIP patches, they can be used for your integration testing if you are developing a sr-iov capable neutron plugin.
If you use devstack, you may need the following patch for devstack to define the PCI whitelist entries:
diff --git a/lib/nova b/lib/nova
index fefeda1..995873a 100644
--- a/lib/nova
+++ b/lib/nova
@@ -475,6 +475,10 @@ function create_nova_conf() {
iniset $NOVA_CONF DEFAULT ${I/=/ }
done
+ if [ -n "$PCI_LIST" ]; then
+ iniset_multiline $NOVA_CONF DEFAULT "pci_passthrough_whitelist" "${PCI_LIST[@]}"
+ fi
+
# All nova-compute workers need to know the vnc configuration options
# These settings don't hurt anything if n-xvnc and n-novnc are disabled
if is_service_enabled n-cpu; then
And define something like the following in your localrc file:
PCI_LIST=('{"vendor_id":"1137","product_id":"0071","address":"*:0a:00.*","physical_network":"physnet1"}'
'{"vendor_id":"1137","product_id":"0071"}')
Basically it's a bash array of strings with each string being a json dict. Checkout https://review.openstack.org/#/c/67500 for the syntax.
Thanks,
Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140226/8ca9ed43/attachment.html>
More information about the OpenStack-dev
mailing list