Awesome!!
Thanks Danial J Best Regards, Arun From: ROSE, DANIEL V [mailto:[email protected]] Sent: Tuesday, June 27, 2017 7:03 PM To: Arun Arora (c) <[email protected]>; [email protected]; DAUGHERTY, ROBERT E <[email protected]> Cc: Gaurav Gupta (c) <[email protected]>; Kapil Gupta (c) <[email protected]>; Jyothis S (c) <[email protected]> Subject: RE: MSO code flow to OpenStack for Orchestration I believe that flow of calls is correct with the exception of I don’t think they call the contrail method all the time. The bpmn flow either creates a vanilla neutron network or a contrail neutron newwork, I think you have both in one flow. Adding in a MultiVIM layer is one of the R1 goals, and right now there is only direct calls to openstack. That said someone like Rob Daugherty can give you a better understanding of the code if you have more specific qustions Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: Arun Arora (c) [mailto:[email protected]] Sent: Tuesday, June 27, 2017 9:29 AM To: ROSE, DANIEL V <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Cc: Gaurav Gupta (c) <[email protected]<mailto:[email protected]>>; Kapil Gupta (c) <[email protected]<mailto:[email protected]>>; Jyothis S (c) <[email protected]<mailto:[email protected]>> Subject: RE: MSO code flow to OpenStack for Orchestration Hi Daniel, Thanks for the quick response :) We will check and get back if we have any further queries. Apart from this, is the code flow from Network/ VNF adapter to OpenStack is correct as mentioned below? Also, we concluded that there is no Intermediate layer between MSO and OpenStack API calls i.e. OpenStack APIs are called directly from Network/ VNF adapter. Can you confirm my this understanding as well? Best Regards, Arun Arora From: ROSE, DANIEL V [mailto:[email protected]] Sent: Tuesday, June 27, 2017 6:54 PM To: Arun Arora (c) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Cc: Kapil Gupta (c) <[email protected]<mailto:[email protected]>>; Jyothis S (c) <[email protected]<mailto:[email protected]>> Subject: RE: MSO code flow to OpenStack for Orchestration Those methods are called from the BPMN workflows that run on the camunda engine. Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Arun Arora (c) Sent: Tuesday, June 27, 2017 9:18 AM To: [email protected]<mailto:[email protected]> Cc: Kapil Gupta (c) <[email protected]<mailto:[email protected]>>; Jyothis S (c) <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] MSO code flow to OpenStack for Orchestration Hello there, I am writing to discuss about the code flow in MSO to orchestrate the Virtual Resources. Currently, we are trying to understand how the OpenStack APIs are called from MSO for orchestration, and, if there is any intermediate layer in MSO which makes a decision about using the underlying Cloud platform, if there are more than one. However, as per our understanding currently only OpenStack is supported for now. Our current understanding is based on the MSO HLD available in ONAP wiki and static code reading. Following is what we understand and request community’s comments on our understanding: Orchestration Request Flow in MSO - from Network/ VNF Adaptor onwards till OpenStack 1. MSO has Network adapter and VNF adapter which are used to create Virtual Network or VNF resources 2. Both Network adapter and VNF adapter call the OpenStack KeyStone and Heat APIs for authentication as well as service orchestration 3. Following are the major APIs (with filename) called to create Virtual Network or VNF resources MSO Network Adaptor createNetwork() ------------------------> createNetworkContrail() ------------------------> createNetwork() ------------------------> createStack()------------------------> OpenStack KeyStone & HEAT API calls NetworkAdapterRest.java MsoNetworkAdapterImpl.java MsoNetworkAdapterImpl.java MsoHeatUtils.java MSO VNF Adaptor createVfModule() ------------------------> createVfModule() ------------------------> CreateStack()------------------------> OpenStack KeyStone & HEAT API calls VnfAdapterRest.java MsoNetworkAdapterImpl.java MsoHeatUtils.java We would like to confirm our current understanding. Please provide your comments and suggestions on this. Also, currently we are not clear about the code from the MSO northbound Interfaces to Netwotk/ VNF Adaptor. So, any help on this as well is much appreciated. Thanks, Arun Arora
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
