Hello Jaime, Thank you for looking into this.
Initially I have tried installing networking and sfc features (odl-netvirt-openstack, odl-dlux-core, odl-mdsal-apidocs, odl-sfc-ui, odl-sfc-openflow-renderer, odl-sfc-scf-openflow, odl-sfc-ovs) in ODL and installed openstack networking-odl package. Openstack L2 agent is disabled and ODL L2 is enabled. Followed as specified in http://docs.opendaylight.org/en/stable-carbon/submodules/netvirt/docs/openstack-guide/openstack-with-netvirt.html I also configured logical-sff and used the same to attach the classifier, but found same errors. Currently I don't have the setup up and running, so I couldn't provide the detailed configuration I have tried. I will reproduce the same and come back with the detailed configuration and logs. As suggested I will go with Nitrogen karaf distribution downloaded from the below specified link https://www.opendaylight.org/technical-community/getting-started-for-developers/downloads-and-documentation Best Regards, Anusha K On Wed, Oct 25, 2017 at 1:48 PM, jcaamano <[email protected]> wrote: > Hello Anusha > > If I understood you correctly, I don't think that using OpenDaylight just > for SFC in a network managed by OpenStack its something that has been > attempted before. > > A start point would be to let OpenDaylight manage all the networking. > And then add SFC. ODL documentation includes a guide to integrate with > OpenStack [1]. For SFC, the Logical Service Function Forwarder > configuration model should be used [2] and this for the classifier [3]. > > There might be some additional manual steps required to make SFC working > in Carbon. In Nitrogen, you will get better support for this scenario so > I would go with that if possible. > > [1] http://docs.opendaylight.org/en/stable-carbon/opendaylight-w > ith-openstack/index.html > [2] http://docs.opendaylight.org/en/stable-carbon/user-guide/ser > vice-function-chaining.html#logical-service-function-forwarder > [3] http://docs.opendaylight.org/en/stable-carbon/user-guide/ser > vice-function-chaining.html#how-to-attach-the-classifier-to-a-logical-sff > > BR > Jaime. > > > On 2017-10-23 20:21, Anusha K wrote: > >> Hi, >> >> I have been trying to achieve service function chaining with NSH >> encapsulation using ODL carbon (distribution-karaf-0.6.1-Carbon). >> Openstack >> (ocata) allinone node is pre-deployed with the integration of Yi Yang ovs >> nsh patch. >> In ODL only SFC features are enabled (odl-sfc-ui, >> odl-sfc-openflow-renderer, odl-sfc-scf-openflow, odl-sfc-ovs). >> >> I have created simple topology >> >> Client --- SF1 --- Server >> >> Openstack ALLINONE Node - 192.168.122.9 >> ODL - 192.168.122.58 >> client - 10.0.0.4(IP), 23(ofport) >> server- 10.0.0.10(IP), 24(ofport) >> SF1 - 10.0.0.7(IP), 25(ofport) >> >> When SFC configuration is inserted through REST, I didn't find >> classification rules in the ovs node (openstack allinone). The whole >> configuration inserted through REST is attached. >> Found below error in karaf.log while inserting the Service Function >> Classifier configuration through REST and the same was attached. >> >> 2017-10-16 07:32:17,037 | ERROR | dispatcher-76130 | >> SfcGeniusRpcClient | 396 - org.opendaylight.sfc.genius - >> 0.5.1.Carbon | getDpnIdFromInterfaceNameFromG >> eniusRPC(GetDpidFromInterfaceInput >> [_intfName=qvo1d67f595-33, augmentation=[]]) failed: RpcResult >> [successful=false, result=null, errors=[RpcError [message=Retrieval of >> datapath id for the key {qvo1d67f595-33} *failed due to missing Interface >> in Config DataStore, severity=ERROR, errorType=APPLICATION, >> tag=operation-failed, applicationTag=null, info=null, cause=null]*]] >> 2017-10-16 07:32:17,038 | ERROR | dispatcher-76130 | >> OpenflowClassifierProcessor | 397 - org.opendaylight.sfc.scf-openf >> low >> - 0.5.1.Carbon | createdServiceFunctionClassifier: *Could not extract the >> node name from the OVS interface* >> 2017-10-16 07:32:17,039 | ERROR | dispatcher-76130 | >> SfcGeniusRpcClient | 396 - org.opendaylight.sfc.genius - >> 0.5.1.Carbon | getDpnIdFromInterfaceNameFromG >> eniusRPC(GetDpidFromInterfaceInput >> [_intfName=qvo1d67f595-33, augmentation=[]]) failed: RpcResult >> [successful=false, result=null, errors=[RpcError [message=Retrieval of >> datapath id for the key {qvo1d67f595-33} *failed due to missing Interface >> in Config DataStore*, severity=ERROR, errorType=APPLICATION, >> tag=operation-failed, applicationTag=null, info=null, cause=null]]] >> 2017-10-16 07:32:17,039 | ERROR | dispatcher-76130 | >> OpenflowClassifierProcessor | 397 - org.opendaylight.sfc.scf-openf >> low >> - 0.5.1.Carbon | createdServiceFunctionClassifier: *Could not extract the >> node name from the OVS interface* >> >> I have also tried topology which is similar to sfc104 demo. I succeeded in >> achieving SFC with NSH encapsulation using the same ODL distribution >> (distribution-karaf-0.6.1-Carbon). >> But I could not achieve the same with allinone openstack setup, where all >> the VM's(client, server, SF1) are on single compute node. >> >> Could someone please provide some insights on the same. >> >> Thank you >> >> Best Regards, >> Anusha K >> >> _______________________________________________ >> sfc-dev mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/sfc-dev >> > >
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
