Majhi provided an accurate description of the SDNC involvement in the vFW demo use case.
As he indicated for more complex interactions SDNC configures the network VNFs using southbound adapters or the REST API call node depending on the device/VNF. SFC is available in the ODL distribution just needs to be activated if you want to use ODL as your overlay controller with a compatible OVS/OVSDB/FD.IO etc vSwitch/vRouter in the VIM. I have an action item to put the steps for turning on SFC in SDNC’s ODL (basically a set of feature:install in the karaf console and SFC runs). As a local controller you would probalby also want to use the SFC neutron service plugin in your openstack based VIM to call the SFC functions and of course have to have a vS/vR on the VIM host. I think FD.io folks have a nice solution in that space and the Intel folks have various demonstration 104 is the latest I think of using the SFC with FD.io. OPNFV folks have also done some work to document/demonstrate how to use ODL SFC in an Openstack environment. We havent turned it into a DG based app since the Neutron Service Plugin can directly call the ODL RESTCONF API but there are some advantages to doing that (for instance you can turn it into a rpc from neutron to sdnc and handle ERROR returns more nicely ) as we did for the vanill a neutron interface on SDNC. Right now ONAP is outside fo the VIM so the sdnc local variation isnt directly applicable. Brian From: [email protected] [mailto:[email protected]] On Behalf Of MAJHI, TAPAN Sent: Tuesday, July 11, 2017 1:23 AM To: Cipher Cipher <[email protected]>; [email protected] Subject: Re: [onap-discuss] [SDNC][APP-C] Importance of SDNC in vFW Demo Cipher, I believe SDNC is not getting used to its full capacity in the demo. The workflow getting used in MSO is having one of the step as preloading the data. Because of which SDNC is getting used to get all the ips for the heat file.In the demo . In complex scenarios SDNC can play a vital role to create resources ,updating AAI and many more. In the demo not such action taking place. MSO is doing everything. Someone from SDNC can explain it better. I didn’t use the ./demo.sh appc directly but this is needed at the time of closed loop . When APPC controls the traffic with the help of vnf action “ModifyConfig”. If the mounting is not done ModifyConfig will not be successful. If you have different VNF then in that also we need honeycomb to make modifyConfig successful. Not sure about your third query. What is SFC ? Regards, Tapan M From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Cipher Cipher Sent: Tuesday, July 11, 2017 12:08 AM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] [SDNC][APP-C] Importance of SDNC in vFW Demo Hey, I am trying vFirewall demo using ONAP. Along the way I am trying to understand the each component I encountered. I couldn't understand the following two points. 1) Preloading of data: Before deploying Vf-module, we have to preload the data to SDNC. But in one of the comments, I came to know this step to update AAI indirectly through SDNC. If that's true, then what is the role of SDNC here. How can I make use of SDNC in complex usecases. 2) APP-C Mounting: Why we need to ./demo.sh appc to trigger the action in packet generator. If I am using a different VNF, how can I use ./demo.sh ? 3)In the release-1.0.0 can we have support of SFC in SDNC? Cheers Shankar This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=wXYf6eEHAgC6-JpddrUNLIrDj2VoUxmogIF_q47Z0IQ&s=X8YWpC3Ys72SkfPfDldh953DoRVDD4sQSjIy8H4YM2Y&e=> Amdocs Development Centre India Private Limited having CIN: U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A limited liability partnership with LLP Identification Number: AAI-6901 effective 28th Feb 2017)
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
