Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-29 Thread Gaurav Gupta (c) 
Hi Rob , Daniel


To futher investigate and difference between createNetwork and 
createNetworkContrail .


We have come to an understanding that based on orchestration Mode whether to 
use createNetwork/createNetworkContrail is used .


Incase of the Orchestration Mode  Heat  CreateNetworkContrail is used

in case of Orchestration Mode neutron createNetwork is used .


is this understanding correct  ?.


with best regards

gaurav


From: onap-discuss-boun...@lists.onap.org <onap-discuss-boun...@lists.onap.org> 
on behalf of Arun Arora (c) <aroraa...@vmware.com>
Sent: 27 June 2017 19:37:58
To: DAUGHERTY, ROBERT E; ROSE, DANIEL V; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] MSO code flow to OpenStack for Orchestration


Hi Rob,



Yes, I also understand that the OpenStack APIs are called from Network/VNF 
adapter.

However, we are still working on the code flow understanding from Network/VNF 
adapter to above. As you mentioned BPMN calls Network/VNF adapter to do the 
operations, we now will work on BPMN and above to complete our understanding.



Best Regards,

Arun



From: DAUGHERTY, ROBERT E [mailto:rd4...@att.com]
Sent: Tuesday, June 27, 2017 7:30 PM
To: Arun Arora (c) <aroraa...@vmware.com>; ROSE, DANIEL V <dr6...@att.com>; 
onap-discuss@lists.onap.org
Cc: Gaurav Gupta (c) <guptagau...@vmware.com>; Kapil Gupta (c) 
<gka...@vmware.com>; Jyothis S (c) <jyoth...@vmware.com>
Subject: RE: MSO code flow to OpenStack for Orchestration



Arun,



Just confirming what said: OpenStack APIs are called directly from the MSO 
Network/VNF adapter.  The BPMN flow makes calls to the adapter to perform those 
operations.



Rob



From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:43 AM
To: ROSE, DANIEL V <dr6...@att.com<mailto:dr6...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DAUGHERTY, 
ROBERT E <rd4...@att.com<mailto:rd4...@att.com>>
Cc: Gaurav Gupta (c) <guptagau...@vmware.com<mailto:guptagau...@vmware.com>>; 
Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S (c) 
<jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
Subject: RE: MSO code flow to OpenStack for Orchestration



Awesome!!



Thanks Danial :)





Best Regards,

Arun





From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Tuesday, June 27, 2017 7:03 PM
To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DAUGHERTY, 
ROBERT E <rd4...@att.com<mailto:rd4...@att.com>>
Cc: Gaurav Gupta (c) <guptagau...@vmware.com<mailto:guptagau...@vmware.com>>; 
Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S (c) 
<jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
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:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:29 AM
To: ROSE, DANIEL V <dr6...@att.com<mailto:dr6...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Gaurav Gupta (c) <guptagau...@vmware.com<mailto:guptagau...@vmware.com>>; 
Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S (c) 
<jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
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:dr6...@att.com]
Sent: Tuesday, June 27, 2017 6:54 PM
To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S 
(c) <jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
Subject: RE: MSO code flow to OpenStack for Orchestrati

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-28 Thread Danny Lin 
I think we are aligned, as that is the goal of R1 of Multi-VIM/Cloud project, 
ie, supporting the existing functionality of SO, APP-C, VNF-C, and a few other 
components, while maintaining the compatibility to OpenStack.

Danny


From: <onap-discuss-boun...@lists.onap.org> on behalf of DeWayne Filppi 
<dewa...@gigaspaces.com>
Date: Tuesday, June 27, 2017 at 9:33 PM
To: "NOSHPITZ, CLAUDE" <cn5...@att.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

No, you're not misreading it.  A layer of mediation is a requirement of 
multi-VIM.  There is however, no "requirement" (using the term strictly), for 
SO to use it, particularly if it jeopardizes SO, and therefore the entire 
system.  Having said that, obviously if multi-VIM is available as planned in 
R1, and it provides all the needed functionality required by the use cases, 
then it should be used.  This only makes sense because the MSO already has 
Openstack capability.  It wouldn't make sense if a brand new interface had to 
be developed as an alternative.  IOW, SO needs multi-VIM, but has a fallback.

--DeWayne

On Tue, Jun 27, 2017 at 5:08 PM, NOSHPITZ, CLAUDE 
<cn5...@att.com<mailto:cn5...@att.com>> wrote:
Apologies if I am misreading this -- it seems like interposing at least some 
layer of mediation in front of "raw" OpenStack calls is a pretty clear 
requirement for R1.

If that's already covered in MultiVIM,  then would the question be more about 
minimizing technical debt due to non-future-proof  workflows or other tooling?

--Claude

> On Jun 27, 2017, at 3:55 PM, DeWayne Filppi 
> <dewa...@gigaspaces.com<mailto:dewa...@gigaspaces.com>> wrote:
>
> I'd say the ideal would be for the MSO/SO to not directly call VIM APIs, but 
> would not want to jeopardize the SO project based on an external dependency 
> that frankly isn't necessary to reach the use case goal for R1.  Just my 2 
> cents.
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=6eVY7dvBpvoXBXPsAVK6PXwHbCRePAEMgPW2uE02KE0=mWC-oG4n2nIZJktAFstJfXIaG0sVFVTWo1T0Q28DNGI=aoDDwjKjF9eufW3gTP5RSs3FjvtDQorm0wm2gMx8n2o=



--
DeWayne Filppi, Director, Solutions Architect

[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-27020792c3e94269b883d9a828be029f56c08986b2ab208a46143b169592c35a.png]<https://urldefense.proofpoint.com/v2/url?u=http-3A__cloudify.co=DwMFaQ=uilaK90D4TOVoH58JNXRgQ=3nVF4lkCrih5WqBdByLDuw=0FweFcaxxctFPyYD-zmZBybrKM8yEpoMvtHoWt_aSgs=YbzhISOmHfDxmdjqJMpb050_F5E_Gj_Wbhf1BIubBZc=>



M: +17145121706

http://cloudify.co<https://urldefense.proofpoint.com/v2/url?u=http-3A__cloudify.co_=DwMFaQ=uilaK90D4TOVoH58JNXRgQ=3nVF4lkCrih5WqBdByLDuw=0FweFcaxxctFPyYD-zmZBybrKM8yEpoMvtHoWt_aSgs=hY9sL3-H3DWzJhQCNNcBiP7dDwwEQuOtUxIt5Q59R3Q=>

@dfilppi

[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/2fb5e7413e7dbeee3e88676333b65c05237ec13d3512e4a63ebc1b5f85bfb917.png]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_CloudifySource=DwMFaQ=uilaK90D4TOVoH58JNXRgQ=3nVF4lkCrih5WqBdByLDuw=0FweFcaxxctFPyYD-zmZBybrKM8yEpoMvtHoWt_aSgs=Zjg6qQsoPY4XhQnSDPsp-n0kWXhcmczYXoC760iOv3c=>
  
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/16b91ab7a91bb3a298f2a322640bebb3754357f93e9f20ff50d2c94bb82b1814.png]
 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company-2Dbeta_17918192_=DwMFaQ=uilaK90D4TOVoH58JNXRgQ=3nVF4lkCrih5WqBdByLDuw=0FweFcaxxctFPyYD-zmZBybrKM8yEpoMvtHoWt_aSgs=HCrGqs2KQnK2wQXIDU6Q4vPq_OPMVwtIzF5OMVZNEE0=>
   
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/6f7421bc5b9a93a0649735bbc8589b200c678bf08af9d7e0cebf1b3cffcdac94.png]
 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudify-2Dcosmo=DwMFaQ=uilaK90D4TOVoH58JNXRgQ=3nVF4lkCrih5WqBdByLDuw=0FweFcaxxctFPyYD-zmZBybrKM8yEpoMvtHoWt_aSgs=iR0dMBGZL2JN500rnUp_Z9Lba0fS1L-NBlmYgiNxcOo=>
   
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/4be4d1377f4c1afe70a25e78926b6aad4e0a4fb1d45a7727e31d5a807eb3aae7.png]
 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_cloudifysource=DwMFaQ=uilaK90D4TOVoH58JNXRgQ=3nVF4lkCrih5WqBdByLDuw=0FweFcaxxctFPyYD-zmZBybrKM8yEpoMvtHoWt_aSgs=DjR_c-HlVAMSIWETUoefr35dJ1kX4zjK_q-J0IuH0s0=>




___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-27 Thread NOSHPITZ, CLAUDE 
Apologies if I am misreading this -- it seems like interposing at least some 
layer of mediation in front of "raw" OpenStack calls is a pretty clear 
requirement for R1.  

If that's already covered in MultiVIM,  then would the question be more about 
minimizing technical debt due to non-future-proof  workflows or other tooling?

--Claude

> On Jun 27, 2017, at 3:55 PM, DeWayne Filppi  wrote:
> 
> I'd say the ideal would be for the MSO/SO to not directly call VIM APIs, but 
> would not want to jeopardize the SO project based on an external dependency 
> that frankly isn't necessary to reach the use case goal for R1.  Just my 2 
> cents.
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=6eVY7dvBpvoXBXPsAVK6PXwHbCRePAEMgPW2uE02KE0=mWC-oG4n2nIZJktAFstJfXIaG0sVFVTWo1T0Q28DNGI=aoDDwjKjF9eufW3gTP5RSs3FjvtDQorm0wm2gMx8n2o=
>  
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-27 Thread DeWayne Filppi 
I'd say the ideal would be for the MSO/SO to not directly call VIM APIs,
but would not want to jeopardize the SO project based on an external
dependency that frankly isn't necessary to reach the use case goal for R1.
Just my 2 cents.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-27 Thread NOSHPITZ, CLAUDE 
Is there general agreement that direct invocation by (M)SO of any OpenStack 
APIs, including “extensions” like Contrail, will not exist in R1 due to these 
functions being encapsulated within Multi-VIM?

Thanks.

--Claude

From: <onap-discuss-boun...@lists.onap.org> on behalf of "Arun Arora (c)" 
<aroraa...@vmware.com>
Date: Tuesday, June 27, 2017 at 7:07 AM
To: "DAUGHERTY, ROBERT E" <rd4...@att.com>, "ROSE, DANIEL V" <dr6...@att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] MSO code flow to OpenStack for Orchestration


Hi Rob,



Yes, I also understand that the OpenStack APIs are called from Network/VNF 
adapter.

However, we are still working on the code flow understanding from Network/VNF 
adapter to above. As you mentioned BPMN calls Network/VNF adapter to do the 
operations, we now will work on BPMN and above to complete our understanding.



Best Regards,

Arun



From: DAUGHERTY, ROBERT E [mailto:rd4...@att.com]
Sent: Tuesday, June 27, 2017 7:30 PM
To: Arun Arora (c) <aroraa...@vmware.com>; ROSE, DANIEL V <dr6...@att.com>; 
onap-discuss@lists.onap.org
Cc: Gaurav Gupta (c) <guptagau...@vmware.com>; Kapil Gupta (c) 
<gka...@vmware.com>; Jyothis S (c) <jyoth...@vmware.com>
Subject: RE: MSO code flow to OpenStack for Orchestration



Arun,



Just confirming what said: OpenStack APIs are called directly from the MSO 
Network/VNF adapter.  The BPMN flow makes calls to the adapter to perform those 
operations.



Rob



From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:43 AM
To: ROSE, DANIEL V <dr6...@att.com<mailto:dr6...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DAUGHERTY, 
ROBERT E <rd4...@att.com<mailto:rd4...@att.com>>
Cc: Gaurav Gupta (c) <guptagau...@vmware.com<mailto:guptagau...@vmware.com>>; 
Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S (c) 
<jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
Subject: RE: MSO code flow to OpenStack for Orchestration



Awesome!!



Thanks Danial ☺





Best Regards,

Arun





From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Tuesday, June 27, 2017 7:03 PM
To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DAUGHERTY, 
ROBERT E <rd4...@att.com<mailto:rd4...@att.com>>
Cc: Gaurav Gupta (c) <guptagau...@vmware.com<mailto:guptagau...@vmware.com>>; 
Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S (c) 
<jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
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:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:29 AM
To: ROSE, DANIEL V <dr6...@att.com<mailto:dr6...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Gaurav Gupta (c) <guptagau...@vmware.com<mailto:guptagau...@vmware.com>>; 
Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S (c) 
<jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
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:dr6...@att.com]
Sent: Tuesday, June 27, 2017 6:54 PM
To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>; Jyothis S 
(c) <jyoth...@vmware.com<mailto:jyoth...@vmware.com>>
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

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-27 Thread Arun Arora (c) 
Hi Rob,



Yes, I also understand that the OpenStack APIs are called from Network/VNF 
adapter.

However, we are still working on the code flow understanding from Network/VNF 
adapter to above. As you mentioned BPMN calls Network/VNF adapter to do the 
operations, we now will work on BPMN and above to complete our understanding.



Best Regards,

Arun



From: DAUGHERTY, ROBERT E [mailto:rd4...@att.com]
Sent: Tuesday, June 27, 2017 7:30 PM
To: Arun Arora (c) ; ROSE, DANIEL V ; 
onap-discuss@lists.onap.org
Cc: Gaurav Gupta (c) ; Kapil Gupta (c) 
; Jyothis S (c) 
Subject: RE: MSO code flow to OpenStack for Orchestration



Arun,



Just confirming what said: OpenStack APIs are called directly from the MSO 
Network/VNF adapter.  The BPMN flow makes calls to the adapter to perform those 
operations.



Rob



From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:43 AM
To: ROSE, DANIEL V >; 
onap-discuss@lists.onap.org; DAUGHERTY, 
ROBERT E >
Cc: Gaurav Gupta (c) >; 
Kapil Gupta (c) >; Jyothis S (c) 
>
Subject: RE: MSO code flow to OpenStack for Orchestration



Awesome!!



Thanks Danial :)





Best Regards,

Arun





From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Tuesday, June 27, 2017 7:03 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org; DAUGHERTY, 
ROBERT E >
Cc: Gaurav Gupta (c) >; 
Kapil Gupta (c) >; Jyothis S (c) 
>
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:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:29 AM
To: ROSE, DANIEL V >; 
onap-discuss@lists.onap.org
Cc: Gaurav Gupta (c) >; 
Kapil Gupta (c) >; Jyothis S (c) 
>
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:dr6...@att.com]
Sent: Tuesday, June 27, 2017 6:54 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >; Jyothis S 
(c) >
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: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, June 27, 2017 9:18 AM
To: onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >; Jyothis S 
(c) >
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

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-27 Thread DAUGHERTY, ROBERT E 
Arun,

Just confirming what said: OpenStack APIs are called directly from the MSO 
Network/VNF adapter.  The BPMN flow makes calls to the adapter to perform those 
operations.

Rob

From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:43 AM
To: ROSE, DANIEL V ; onap-discuss@lists.onap.org; DAUGHERTY, 
ROBERT E 
Cc: Gaurav Gupta (c) ; Kapil Gupta (c) 
; Jyothis S (c) 
Subject: RE: MSO code flow to OpenStack for Orchestration


Awesome!!



Thanks Danial :)





Best Regards,

Arun





From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Tuesday, June 27, 2017 7:03 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org; DAUGHERTY, 
ROBERT E >
Cc: Gaurav Gupta (c) >; 
Kapil Gupta (c) >; Jyothis S (c) 
>
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:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:29 AM
To: ROSE, DANIEL V >; 
onap-discuss@lists.onap.org
Cc: Gaurav Gupta (c) >; 
Kapil Gupta (c) >; Jyothis S (c) 
>
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:dr6...@att.com]
Sent: Tuesday, June 27, 2017 6:54 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >; Jyothis S 
(c) >
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: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, June 27, 2017 9:18 AM
To: onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >; Jyothis S 
(c) >
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

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-27 Thread ROSE, DANIEL V 
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:aroraa...@vmware.com]
Sent: Tuesday, June 27, 2017 9:29 AM
To: ROSE, DANIEL V ; onap-discuss@lists.onap.org
Cc: Gaurav Gupta (c) ; Kapil Gupta (c) 
; Jyothis S (c) 
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:dr6...@att.com]
Sent: Tuesday, June 27, 2017 6:54 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >; Jyothis S 
(c) >
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: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, June 27, 2017 9:18 AM
To: onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >; Jyothis S 
(c) >
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.javaMsoNetworkAdapterImpl.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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] MSO code flow to OpenStack for Orchestration

2017-06-27 Thread ROSE, DANIEL V 
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: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, June 27, 2017 9:18 AM
To: onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) ; Jyothis S (c) 
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.javaMsoNetworkAdapterImpl.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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss