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

2017-06-29 Thread Gaurav Gupta (c)
lt;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,

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

2017-06-28 Thread Danny Lin
eWayne 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: [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

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

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

2017-06-27 Thread NOSHPITZ, CLAUDE
un 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]

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

2017-06-27 Thread Arun Arora (c)
lists.onap.org] On Behalf Of Arun Arora (c) Sent: Tuesday, June 27, 2017 9:18 AM To: 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

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

2017-06-27 Thread DAUGHERTY, ROBERT E
To: 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: [onap-discuss] MSO code flow to OpenStack fo

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

2017-06-27 Thread ROSE, DANIEL V
(c) Sent: Tuesday, June 27, 2017 9:18 AM To: 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: [onap-discuss] MSO code

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

2017-06-27 Thread ROSE, DANIEL V
To: onap-discuss@lists.onap.org Cc: Kapil Gupta (c) <gka...@vmware.com>; Jyothis S (c) <jyoth...@vmware.com> 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. C