Thanks Danny for your reply. but I think this way will elongate the traffic path ... Per each SF, there will be 6 hops (SFF- SF Proxy VM) - (SF-Proxy VM- OVS) - (OVS - SF VM) - (SF VM - OVS) - (OVS - SF Proxy VM ) - (SF Proxy VM- SFF) or ?
Best regrads, Ahmed On Thu, Sep 1, 2016 at 3:36 PM, Zhou, Danny <[email protected]> wrote: > Ahmad, comments inline. > > > > *From:* Ahmed Medhat [mailto:[email protected]] > *Sent:* Wednesday, August 31, 2016 6:46 PM > *To:* Zhou, Danny <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [sfc-dev] NSH Proxy for NSH unaware SFs > > > > Thanks a lot Danny for your answers: > > So now : > 1-which version of ODL SFC supports the NSH proxy ? Boron supports it ? > > DZ: Yes, the latest code merged to the mainline hence coming Boron release > will support it. > > 2- Regarding Openstack ,,, do you mean that the each VM host a NSH unaware > SF should have the VPP based NSH proxy ? > > DZ: No, I mean you can instantiate a VM hosting VPP based NSH proxy which > could support many NSH unaware VMs. Specifically, the OVS need to steer NSH > traffics to the NSH Proxy VM which then manipulate the NSH header and steer > traffics to NSH unaware VMs. > > 3- where can I find the VPP based NSH proxy ? > > DZ: Pls check the NSH SFC project wiki https://wiki.fd.io/view/NSH_SFC > which contains the link to the repository. > > 4- The ODL controller will contact the VPP based NSH Proxy for what and > when ? ( I think that the ODL controller should use the floating ips of > the VMs hosting the SFs in order to be reachable from the ODL controller) > > DZ: Configure the tables (e.g. NSH match table and map table) in the NSH > Proxy to 1) match on the SP and SI pair to determine which VM recognized > transports (e.g. VxLAN, VLAN) and destination IP/MAC to use for ingress > traffic and 2) match on the transport/IP/MAC to get the previously stripped > NSH + Transport then recover the NSH packet followed-by decrement SI. > > Best regards, > > Ahmed > > > > > > On Wed, Aug 31, 2016 at 12:27 PM, Zhou, Danny <[email protected]> > wrote: > > Answers inline. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Ahmed Medhat > *Sent:* Wednesday, August 31, 2016 6:08 PM > *To:* [email protected] > *Subject:* [sfc-dev] NSH Proxy for NSH unaware SFs > > > > Hi all, > > I would like to know the status of the NSH proxy ? and need to know some > more details about it please (How it works, How to configure it with ODL > SFC solution in Openstack, Where Can I found it ...etc) ? > > DZ: The patch https://git.opendaylight.org/gerrit/#/c/42699/ from Yi Yang > has been merged, which leverages NETCONF SB plugin to interface with VPP. > Integration test ongoing as sth is blocked on the Honeycomb agent. At high > level, the SF’ Yang model is extended to add a portion below about > corresponding NSH proxy information if nsh_aware flag is false, so SFF > instead of steer NSH traffics to NSH unaware SF it directs traffics to NSH > proxy first which then manipulate NSH header on behalf of the SF. > > " service-function-proxy:proxy-data-plane-locator": > { > > "port": 4790, //NSH Proxy’s > tunnel port > > "ip": "192.168.50.76", //NSH Proxy’s tunnel > IP > > "transport": "service-locator: vxlan-gpe" > //NSH Proxy’s inbound transport type > > } > > In Carbon release, we will be enabling a SFC 104 demo with integrated VPP > which could act as NSH Proxy and NSH aware VNFs, so the SFC 104 will > include all kinds of modules (e.g. OVS based SFF/classifier, VPP based NSH > proxy, VPP based NSH aware VNFs and NSH unaware VNFs) in a NSH based SFC > solution. > > Other questions I need to know: > > 1- I know it is based on the FD.io/VPP, will the VPP be used instead > of the OVS or will it be connected to OVS ? > > DZ: It will be connected to OVS as NSH Proxy is an individual entity > bridging OVS based SFF and NSH unaware SFs. > > > > 2- Is this solution can work with OpenStack ? How ? > > DZ: It should work if you instantiate a VM hosting VPP based NSH proxy. > > Thanks in advance, > > Best regards, > > Ahmed > > >
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
