Open Stack

On 2013?10?27? 15:48, Irena Berezovsky wrote:
>
> Hi Robert,
>
> Thank you very much for sharing the information regarding your 
> efforts. Can you please share your idea of the end to end flow? How do 
> you suggest  to bind Nova and Neutron?
>
> The blueprints you registered make sense. On Nova side, there is a 
> need to bind between requested virtual network and PCI 
> device/interface to be allocated as vNIC.
>
> On the Neutron side, there is a need to  support networking 
> configuration of the vNIC. Neutron should be able to identify the PCI 
> device/macvtap interface in order to apply configuration. I think it 
> makes sense to provide neutron integration via dedicated Modular Layer 
> 2 Mechanism Driver to allow PCI pass-through vNIC support along with 
> other networking technologies.
>
> During the Havana Release, we introduced Mellanox Neutron plugin that 
> enables networking via SRIOV pass-through devices or macvtap interfaces.
>
Hi, Irena & Robert

I'm very intresting on your work Mellanox Neutron plugin, which enable 
SRIOV devices or mactap interfaces. and could you provide more 
infomation about it: bp/patches/current work flow/what is expect from 
nova pci passthourgh.  and then, plus Robert's requements/discuss, i 
know the more detail about what's expected from nova pci, what pci next 
will to be.

in current stats i got:

a) fine classify of devices by auto discovery and request
     1) enable white list specify the address
     2) enable white list append group info like (IN/OUT/... anything)
     3) enable pci request can apppend  more infomation into the extra info
         i need input here, what is it? eventhough pci don't care the 
extra info, but clear is better.
         i.e. Robet's
              . direct pci-passthrough/macvtap
               port profile

b) extra info awawness allocation ('feature pci' by Robert)
<https://launchpad.net/%7Ebaoli>

    1) had API and code level interface to access extra info
    2) Scheduler awawa ness about extra info/or device type so vNIC can 
be differentiated.
    3) boot/interface-attach APIs:  API interface for convertneutron NIC 
info to PCI request. :
from binding:capabilities binding:profile  to
            PCI alias(request)/
            direct pci-passthrough/macvtap  ( is it need store into pci 
device extra info?)
            port profile( is it need store into pci device extra info?)
    4) scheduler enhancement to meet NIC requements

Yongli He at intel

> We want to integrate our solution with PCI pass-through Nova support. 
>  I will be glad to share more details if you are interested.
>
> The PCI pass-through networking support is planned to be discussed 
> during the summit: http://summit.openstack.org/cfp/details/129. I 
> think it's worth to drill down into more detailed proposal and present 
> it during the summit, especially since it impacts both nova and 
> neutron projects.
>
> Would you be interested in collaboration on this effort? Would you be 
> interested to exchange more emails or set an IRC/WebEx meeting during 
> this week before the summit?
>
> Regards,
>
> Irena
>
> *From:*Robert Li (baoli) [mailto:baoli at cisco.com]
> *Sent:* Friday, October 25, 2013 11:16 PM
> *To:* prashant.upadhyaya at aricent.com; Irena Berezovsky; 
> yunhong.jiang at intel.com; chris.friesen at windriver.com; yongli.he at 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,
>
> 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 instances that employes the SRIOV interfaces. Certainly, 
> this was accomplished with hacking and some manual intervention. Based 
> on this experience and my study with the two existing nova 
> pci-passthrough blueprints that have been implemented and committed 
> into Havana 
> (https://blueprints.launchpad.net/nova/+spec/pci-passthrough-base and
> https://blueprints.launchpad.net/nova/+spec/pci-passthrough-libvirt), 
>  I registered a couple of blueprints (one on Nova side, the other on 
> the Neutron side):
>
> https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov
>
> https://blueprints.launchpad.net/neutron/+spec/pci-passthrough-sriov
>
> in order to address SRIOV support in openstack.
>
> Please take a look at them and see if they make sense, and let me know 
> any comments and questions. We can also discuss this in the summit, I 
> suppose.
>
> I noticed that there is another thread on this topic, so copy those 
> folks  from that thread as well.
>
> thanks,
>
> Robert
>
> On 10/16/13 4:32 PM, "Irena Berezovsky" <irenab at mellanox.com 
> <mailto:irenab at mellanox.com>> wrote:
>
>     Hi,
>
>     As one of the next steps for PCI pass-through I would like to
>     discuss is the support for PCI pass-through vNIC.
>
>     While nova takes care of PCI pass-through device resources
>      management and VIF settings, neutron should manage their
>     networking configuration.
>
>     I would like to register asummit proposal to discuss the support
>     for PCI pass-through networking.
>
>     I am not sure what would be the right topic to discuss the PCI
>     pass-through networking, since it involve both nova and neutron.
>
>     There is already a session registered by Yongli on nova topic to
>     discuss the PCI pass-through next steps.
>
>     I think PCI pass-through networking is quite a big topic and it
>     worth to have a separate discussion.
>
>     Is there any other people who are interested to discuss it and
>     share their thoughts and experience?
>
>     Regards,
>
>     Irena
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131029/9ddbe9fe/attachment-0001.html>