[openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th
Robert Li (baoli)
baoli at cisco.com
Wed Jan 29 14:46:41 UTC 2014
I'd like to do a recap on today's meeting, and if possible we should continue the discussion in this thread so that we can be more productive in tomorrow's meeting.
Bob suggests that we have these BPs:
One generic covering implementing binding:profile in ML2, and one specific to PCI-passthru, defining the vnic-type (wherever it goes) and any keys for binding:profile.
Irena suggests that we have three BPs:
1. generic ML2 support for binding:profile (corresponding to Bob's covering implementing binding:profile in ML2 ?)
2. add vnic_type support for binding Mech Drivers in ML2 plugin
3. support PCI slot via profile (corresponding to Bob's any keys for binding:profile ?)
Both proposals sound similar, so it's great that we are converging. I think that it's important that we put more details in each BP on what's exactly covered by it. One question I have is about where binding:profile will be implemented. I see that portbinding is defined/implemented under its extension and neutron.db. So when both of you guys are saying that implementing binding:profile in ML2, I'm kind of confused. Please let me know what I'm missing here. My understanding is that non-ML2 plugin can use it as well.
Another issue that came up during the meeting is about whether or not vnic-type should be part of the top level binding or part of binding:profile. In other words, should it be defined as binding:vnic-type or binding:profile:vnic-type.
We also need one or two BPs to cover the change in the neutron port-create/port-show CLI/API.
Another thing is that we need to define the binding:profile dictionary.
On 1/29/14 4:02 AM, "Irena Berezovsky" <irenab at mellanox.com<mailto:irenab at mellanox.com>> wrote:
From: Robert Li (baoli) [mailto:baoli at cisco.com]
Sent: Wednesday, January 29, 2014 12:55 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th
Can we have one more meeting tomorrow? I'd like to discuss the blueprints we are going to have and what each BP will be covering.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev