Ian,
I hope that you guys are in agreement on this. But take a look at the wiki:
https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support and see if it has
any difference from your proposals. IMO, it's the critical piece of the
proposal, and hasn't been specified in exact term yet. I'm
Hi Yongli,
Thank you for addressing my comments, and for adding the encryption card
use case. One thing that I want to point out is that in this use case, you
may not use the pci-flavor in the --nic option because it's not a neutron
feature.
I have a few more questions:
1. pci-flavor-attrs is
My proposals:
On 29 January 2014 16:43, Robert Li (baoli) ba...@cisco.com wrote:
1. pci-flavor-attrs is configured through configuration files and will be
available on both the controller node and the compute nodes. Can the cloud
admin decide to add a new attribute in a running cloud? If
Document updated to talk about network aware scheduling (
https://docs.google.com/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU/edit#-
section just before the use case list).
Based on yesterday's meeting, rkukura would also like to see network-aware
scheduling to work for non-PCI cases
as VM vNIC.
Regards,
Irena
-Original Message-
From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
Sent: Friday, January 17, 2014 9:06 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Robert
Yunhong,
Just try to understand your use case:
-- a VM can only work with cards from vendor V1
-- a VM can work with cards from both vendor V1 and V2
So stats in the two flavors will overlap in the PCI flavor solution.
I'm just trying to say that this is something that needs to be
-
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Saturday, January 18, 2014 12:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Yunhong,
I'm hoping that these comments can be directly
On 20 January 2014 09:28, Irena Berezovsky ire...@mellanox.com wrote:
Hi,
Having post PCI meeting discussion with Ian based on his proposal
https://docs.google.com/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU/edit?pli=1#
,
I am not sure that the case that quite usable for SR-IOV
: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Friday, January 17, 2014 7:08 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Yunhong,
Thank you for bringing that up on the live migration
Yunhong,
Thank you for bringing that up on the live migration support. In addition
to the two solutions you mentioned, Irena has a different solution. Let me
put all the them here again:
1. network xml/group based solution.
In this solution, each host that supports a provider
Li (baoli) [mailto:ba...@cisco.com]
Sent: Friday, January 17, 2014 7:08 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Yunhong,
Thank you for bringing that up on the live migration support
network scenario in that framework.
Thanks
--jyh
-Original Message-
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Friday, January 17, 2014 7:08 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through
On Fri, 2014-01-17 at 22:30 +, Robert Li (baoli) wrote:
Yunhong,
I'm hoping that these comments can be directly addressed:
a practical deployment scenario that requires arbitrary
attributes.
I'm just strongly against to support only one attributes (your PCI
group) for scheduling
On 2014?01?16? 08:28, Ian Wells wrote:
To clarify a couple of Robert's points, since we had a conversation
earlier:
On 15 January 2014 23:47, Robert Li (baoli) ba...@cisco.com
mailto:ba...@cisco.com wrote:
--- do we agree that BDF address (or device id, whatever you call
it), and
/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU/edit?pli=1#heading=h.308b0wqn1zde
BR,
Irena
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Thursday, January 16, 2014 2:34 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron
On 16 January 2014 09:07, yongli he yongli...@intel.com wrote:
On 2014年01月16日 08:28, Ian Wells wrote:
This is based on Robert's current code for macvtap based live migration.
The issue is that if you wish to migrate a VM and it's tied to a physical
interface, you can't guarantee that the
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Ian,
Thank you for putting in writing the ongoing discussed specification.
I have
On Thu, 2014-01-16 at 01:28 +0100, Ian Wells wrote:
To clarify a couple of Robert's points, since we had a conversation
earlier:
On 15 January 2014 23:47, Robert Li (baoli) ba...@cisco.com wrote:
--- do we agree that BDF address (or device id, whatever
you call it), and
To clarify a couple of Robert's points, since we had a conversation earlier:
On 15 January 2014 23:47, Robert Li (baoli) ba...@cisco.com wrote:
--- do we agree that BDF address (or device id, whatever you call it),
and node id shouldn't be used as attributes in defining a PCI flavor?
Note
)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Comments with prefix [yjiang5_2] , including the double confirm.
I think we (you and me) is mostly on the same page, would you please give a
summary, and then we can have community , including Irena/Robert, to check
that integrate with
neutron APIs from item 3.
Regards,
Irena
-Original Message-
From: John Garbutt [mailto:j...@johngarbutt.com]
Sent: Friday, January 10, 2014 4:34 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass
, January 13, 2014 2:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Irena, have a word with Bob (rkukura on IRC, East coast), he was talking about
what would be needed already and should be able
As I have responded in the other email, and If I understand PCI flavor
correctly, then the issue that we need to deal with is the overlapping issue. A
simplest case of this overlapping is that you can define a flavor F1 as
[vendor_id='v', product_id='p'], and a flavor F2 as [vendor_id = 'v'] .
...@cisco.com]
Sent: Monday, January 13, 2014 8:22 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
As I have responded in the other email, and If I understand PCI flavor
correctly, then the issue that we
*From:* Robert Li (baoli) [mailto:ba...@cisco.com]
*Sent:* Monday, January 13, 2014 8:22 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
As I have responded in the other email, and If I
To: OpenStack Development Mailing List (not for usage questions)
Cc: Jiang, Yunhong; He, Yongli; Robert Li (baoli) (ba...@cisco.com); Sandhya
Dasu (sadasu) (sad...@cisco.com); ijw.ubu...@cack.org.uk; j...@johngarbutt.com
Subject: RE: [openstack-dev] [nova] [neutron] PCI pass-through network support
flavor, i.e. pci
requests, to the pci stats.
Thanks
--jyh
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Monday, January 13, 2014 10:57 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
It's worth
*From:* Ian Wells [mailto:ijw.ubu...@cack.org.uk]
*Sent:* Monday, January 13, 2014 10:57 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
It's worth noting that this makes the scheduling
: [openstack-dev] [nova] [neutron] PCI pass-through network support
Apologies for this top post, I just want to move this discussion towards action.
I am traveling next week so it is unlikely that I can make the meetings. Sorry.
Can we please agree on some concrete actions, and who will do the coding
On 10 January 2014 07:40, Jiang, Yunhong yunhong.ji...@intel.com wrote:
Robert, sorry that I’m not fan of * your group * term. To me, *your
group” mixed two thing. It’s an extra property provided by configuration,
and also it’s a very-not-flexible mechanism to select devices (you can only
In any case, we don't have to decide this now. If we simply allowed the
whitelist to add extra arbitrary properties to the PCI record (like a group
name) and return it to the central server, we could use that in scheduling
for the minute as a group name, we wouldn't implement the APIs for flavors
Apologies for this top post, I just want to move this discussion towards action.
I am traveling next week so it is unlikely that I can make the meetings. Sorry.
Can we please agree on some concrete actions, and who will do the coding?
This also means raising new blueprints for each item of work.
+1 PCI Flavor.
From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
Sent: January-10-14 1:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
BTW, I like the PCI flavor :)
From: Jiang, Yunhong
To: OpenStack Development Mailing List (not for usage questions); Irena
Berezovsky; Sandhya Dasu (sadasu); Jiang, Yunhong; Itzik Brown;
j...@johngarbutt.commailto:j...@johngarbutt.com; He, Yongli
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi Folks,
With John joining
Hi Yongli,
Please also see my response to Yunhong. Here, I just want to add a comment
about your local versus global argument. I took a brief look at your patches,
and the PCI-flavor is added into the whitelist. The compute node needs to know
these pci-flavors in order to report PCI stats
Ian, thanks for your reply. Please check my response prefix with 'yjiang5'.
--jyh
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Friday, January 10, 2014 4:08 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through
, and it may even various in different
distribution.
Thanks
--jyh
From: Brian Schott [mailto:brian.sch...@nimbisservices.com]
Sent: Thursday, January 09, 2014 11:19 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network
On 10 January 2014 15:30, John Garbutt j...@johngarbutt.com wrote:
We seemed happy with the current system (roughly) around GPU passthrough:
nova flavor-key three_GPU_attached_30GB set
pci_passthrough:alias= large_GPU:1,small_GPU:2
nova boot --image some_image --flavor three_GPU_attached_30GB
Hey Yunhong,
The thing about 'group' and 'flavor' and 'whitelist' is that they once
meant distinct things (and I think we've been trying to reduce them back
from three things to two or one):
- group: equivalent devices at a host level - use any one, no-one will
care, because they're either
Ian, thanks for your reply. Please check comments prefix with [yjiang5].
Thanks
--jyh
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Friday, January 10, 2014 12:17 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass
I have to use [yjiang5_1] prefix now :)
--jyh
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Friday, January 10, 2014 3:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
On 11 January 2014
Hi Folks,
With John joining the IRC, so far, we had a couple of productive meetings in an
effort to come to consensus and move forward. Thanks John for doing that, and I
appreciate everyone's effort to make it to the daily meeting. Let's reconvene
on Monday.
But before that, and based on our
I think I'm in agreement with all of this. Nice summary, Robert.
It may not be where the work ends, but if we could get this done the rest
is just refinement.
On 9 January 2014 17:49, Robert Li (baoli) ba...@cisco.com wrote:
Hi Folks,
With John joining the IRC, so far, we had a
Ian,
The idea of pci flavors is a great and using vendor_id and product_id make
sense, but I could see a case for adding the class name such as 'VGA compatible
controller'. Otherwise, slightly different generations of hardware will mean
custom whitelist setups on each compute node.
01:00.0
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
I think I'm in agreement with all of this. Nice summary, Robert.
It may not be where the work ends, but if we could get this done the rest is
just refinement.
On 9 January
On 9 January 2014 20:19, Brian Schott brian.sch...@nimbisservices.comwrote:
Ian,
The idea of pci flavors is a great and using vendor_id and product_id make
sense, but I could see a case for adding the class name such as 'VGA
compatible controller'. Otherwise, slightly different generations
On 9 January 2014 22:50, Ian Wells ijw.ubu...@cack.org.uk wrote:
On 9 January 2014 20:19, Brian Schott brian.sch...@nimbisservices.comwrote:
On the flip side, vendor_id and product_id might not be sufficient.
Suppose I have two identical NICs, one for nova internal use and the
second for
: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi Folks,
With John joining the IRC, so far, we had a couple of productive meetings in an
effort to come to consensus and move forward. Thanks John for doing that, and I
appreciate everyone's effort to make it to the daily meeting
Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
I think I'm in agreement with all of this. Nice summary, Robert.
It may not be where the work ends, but if we could get this done the rest is
just refinement.
On 9 January
BTW, I like the PCI flavor :)
From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
Sent: Thursday, January 09, 2014 10:41 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi, Ian, when you
On 2014?01?10? 00:49, Robert Li (baoli) wrote:
Hi Folks,
HI, all
basiclly i flavor the pic-flavor style and against massing the
white-list. please see my inline comments.
With John joining the IRC, so far, we had a couple of productive
meetings in an effort to come to consensus and
On 22 December 2013 12:07, Irena Berezovsky ire...@mellanox.com wrote:
Hi Ian,
My comments are inline
I would like to suggest to focus the next PCI-pass though IRC meeting on:
1.Closing the administration and tenant that powers the VM use
cases.
2. Decouple the nova and
Hi John,
We had one on 12/14/2013 with the log:
http://eavesdrop.openstack.org/meetings/pci_passthrough_meeting/2013/pci_pa
ssthrough_meeting.2013-12-24-14.02.log.html
The next one will be at UTC 1400 on Jan. 7th, Tuesday.
--Robert
On 1/2/14 10:06 AM, John Garbutt j...@johngarbutt.com wrote:
Hi,
I would just like to share my idea on somehow managing sr-iov networking
attributes in neutron (e.g. mac addr, ip addr, vlan). I've had experience
implementing this and that was before pci-passthrough feature in nova
existed. Basically, nova still did the plugging and the unplugging of vifs
On 12/17/2013 10:09 AM, Ian Wells wrote:
Reiterating from the IRC mneeting, largely, so apologies.
Firstly, I disagree that
https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support is an
accurate reflection of the current state. It's a very unilateral view,
largely because the rest of us
: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Friday, December 20, 2013 2:50 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
On 19 December 2013 15:15, John Garbutt
j...@johngarbutt.commailto:j
Apologies for being late onto this thread, and not making the meeting
the other day.
Also apologies this is almost totally a top post.
On 17 December 2013 15:09, Ian Wells ijw.ubu...@cack.org.uk wrote:
Firstly, I disagree that
https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support is an
John:
At a high level:
Neutron:
* user wants to connect to a particular neutron network
* user wants a super-fast SRIOV connection
Administration:
* needs to map PCI device to what neutron network the connect to
The big question is:
* is this a specific SRIOV only (provider) network
*
On 19 December 2013 12:21, Ian Wells ijw.ubu...@cack.org.uk wrote:
John:
At a high level:
Neutron:
* user wants to connect to a particular neutron network
* user wants a super-fast SRIOV connection
Administration:
* needs to map PCI device to what neutron network the connect to
The
On 19 December 2013 12:54, John Garbutt j...@johngarbutt.com wrote:
On 19 December 2013 12:21, Ian Wells ijw.ubu...@cack.org.uk wrote:
John:
At a high level:
Neutron:
* user wants to connect to a particular neutron network
* user wants a super-fast SRIOV connection
Administration:
*
Garbutt [mailto:j...@johngarbutt.com]
Sent: Thursday, December 19, 2013 1:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Apologies for being late onto this thread, and not making the meeting
use cases.
Please see my comments inline.
Cool.
Regards,
Irena
-Original Message-
From: John Garbutt [mailto:j...@johngarbutt.com]
Sent: Thursday, December 19, 2013 1:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron
On 19 December 2013 15:15, John Garbutt j...@johngarbutt.com wrote:
Note, I don't see the person who boots the server ever seeing the
pci-flavor, only understanding the server flavor.
[IrenaB] I am not sure that elaborating PCI device request into server
flavor is the right approach for
Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi,
Regarding physical network mapping, This is what I thought.
consider the following
On Wed, Oct 30, 2013 at 04:14:40AM +,
Jiang, Yunhong yunhong.ji...@intel.com wrote:
But how about long term direction?
Neutron should know/manage such network related resources on
compute nodes?
So you mean the PCI device management will be spited between Nova and
Neutron? For
List; Brian Bowen (brbowen); Kyle Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi Irena,
This is Robert Li from Cisco Systems. Recently, I was tasked to investigate
such support for Cisco's systems that support VM-FEX
(kmestery); Sandhya Dasu (sadasu)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi Irena,
Thank you very much for your comments. See inline.
--Robert
On 10/27/13 3:48 AM, Irena Berezovsky
ire...@mellanox.commailto:ire...@mellanox.com wrote:
Hi Robert,
Thank you very
...@windriver.com; He, Yongli; Itzik Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: RE: [openstack-dev] [nova] [neutron] PCI pass-through network support
Robert, is it possible to have a IRC meeting? I'd prefer to IRC
(brbowen); Kyle Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Hi Irena,
Thank you very much for your comments. See inline.
--Robert
On 10/27/13 3:48 AM, Irena Berezovsky ire...@mellanox.com wrote:
Hi
...@windriver.commailto:chris.frie...@windriver.com; He, Yongli;
Itzik Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: RE: [openstack-dev] [nova] [neutron] PCI pass-through network support
Robert, is it possible to have a IRC
(brbowen); Kyle Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi Irena,
Thank you very much for your comments. See inline.
--Robert
On 10/27/13 3:48 AM, Irena Berezovsky
ire...@mellanox.commailto:ire...@mellanox.com wrote
, Yongli; Itzik Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle
Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: RE: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Robert, is it possible to have a IRC meeting? I¹d prefer to IRC meeting
because it¹s
; prashant.upadhy...@aricent.com;
chris.frie...@windriver.com; He, Yongli; Itzik Brown
*Cc:* OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle
Mestery (kmestery); Sandhya Dasu (sadasu)
*Subject:* Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Hi
...@aricent.com;
chris.frie...@windriver.com; He, Yongli; Itzik Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle
Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: RE: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Robert, is it possible
...@aricent.com;
chris.frie...@windriver.com; He, Yongli; Itzik Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: RE: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi Jiang, Robert,
IRC meeting option works
(kmestery); Sandhya Dasu (sadasu)
*Subject:* Re: [openstack-dev] [nova] [neutron] PCI pass-through
network support
Hi Yunhong,
I haven't looked at Mellanox in much detail. I think that we'll get more
details from Irena down the road. Regarding your question, I can only
answer
Message-
From: Henry Gessau [mailto:ges...@cisco.com]
Sent: Tuesday, October 29, 2013 8:10 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
Lots of great info and discussion going on here.
One
-Original Message-
From: Henry Gessau [mailto:ges...@cisco.com]
Sent: Tuesday, October 29, 2013 2:23 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network
support
On Tue, Oct 29, at 4:31 pm
] [neutron] PCI pass-through network
support
On Tue, Oct 29, at 4:31 pm, Jiang, Yunhong yunhong.ji...@intel.com
wrote:
Henry,why do you think the service VM need the entire PF instead of a
VF? I think the SR-IOV NIC should provide QoS and performance
isolation.
I was speculating. I just
,
Yunhong;
chris.frie...@windriver.com; He, Yongli; Itzik Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen);
Kyle
Mestery
(kmestery); Sandhya Dasu (sadasu)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through
network
support
Hi Irena
...@windriver.com;
yongli...@intel.com mailto:yongli...@intel.com
*Cc:* OpenStack Development Mailing List; Brian Bowen (brbowen);
Kyle Mestery (kmestery); Sandhya Dasu (sadasu)
*Subject:* Re: [openstack-dev] [nova] [neutron] PCI pass-through
network support
Hi Irena
Hi Irena,
This is Robert Li from Cisco Systems. Recently, I was tasked to investigate
such support for Cisco's systems that support VM-FEX, which is a SRIOV
technology supporting 802-1Qbh. I was able to bring up nova instances with
SRIOV interfaces, and establish networking in between the
82 matches
Mail list logo
