The demo is specifically just a demo. So the stuff in the demo like the robot scripts will not work for other vnfs. The mechanisms used in the scripts will work with any vnfs however.
To give you an example, preload command calls sdnc rest api that loads info like IPs to sdnc so that when you go to vid and instantiate a vnf sdnc knows what data to use. You can call that api yourself to fill in your specific parameters for ANY vnf ( you can add a call to the DG to make a call out to any external system via rest instead of doing the preload also). In the rebase code VID has the option to provide those preloads as part of the GUI to make it a bit easier but even though the flow changes the fact that it applies to all VNFs does not change. Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected] [mailto:[email protected]] On Behalf Of Viswa KSP Sent: Thursday, June 01, 2017 4:50 AM To: [email protected] Subject: [onap-discuss] Why there is a manual step before deploying a distributed / certified network service? Dear All, We are trying to follow the steps as per tutorial to bring demo vFirewall Network service. While the steps before deploy operation ( i.e creation of license model, design-test-certify cycle for VSP, VF & NS and finally distributing NS for production ) seems to be generic & acceptable for other VNFs, the step for running demo.sh in robot VM to enable "Deploy" in VID seems to very specific to vFirewall NS. I would like to understand if this manual step is expected in any other NS? What if we wanna customize the work-flow i.e say I want to just design my NS and just deploy it right away ( without other steps as per demo work-flow ) , how should I go-about in achieving this? On a very high-level, I would like to know how much we can customize ONAP ? BR, Viswa
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
