Suraj, As far as I know, the SO code is supporting HEAT *only* to create a VNF, hence does support only VIM supporting HEAT. Using MultiCloud to authenticate to the VIM is fine, but SO doesn’t offload the creation of the VNF to MultCloud. Hence for a VIM not supporting HEAT, and not OpenStack based, this doesn’t work.
I’m wondering if there is any design document about having SO completely relying on MultiCloud instead of relying on its own HEAT support. Alexis > On Feb 19, 2018, at 1:06 PM, Bisht, Suraj (Nokia - US/Irving) > <suraj.bi...@nokia.com> wrote: > > Hi Alexis, > > Attached mail earlier has all steps for SO integration as well > > For other cloud SO config should be > Case 2: SO instantiate a VF modules via MultiCloud > > In this case, VIM registration information refers to > MultiCloud endpoints which is a proxy to underlying VIMs, so the identity_url > looks like: > > "identity_url": " > http://10.0.14.1:80/api/multicloud-titanium_cloud/v0/pod25_RegionOne/identity/v2.0 > > <http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_RegionOne/identity/v2.0>", > > Above should invoke multi-VIM API supporting various VIM types, supported VIM > types are available in following link “Release Components Name“ > > https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-MultiVIM/Cloud > > <https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-MultiVIM/Cloud> > > Thanks, > Suraj > > From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com > <mailto:adetalhoue...@gmail.com>] > Sent: Monday, February 19, 2018 11:41 AM > To: Bisht, Suraj (Nokia - US/Irving) <suraj.bi...@nokia.com > <mailto:suraj.bi...@nokia.com>> > Cc: Avdhut Kholkar <avdhut.khol...@amdocs.com > <mailto:avdhut.khol...@amdocs.com>>; onap-discuss > <onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>>; Talari > Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_v...@nokia.com > <mailto:vara.talari_nehemiah_v...@nokia.com>> > Subject: Re: [onap-discuss] [SO][Multicloud] How to get SO deploy VNF using > Multicloud on any type of VIM? > > Avdhut, > > Thanks for the answer, good to know there is a possibility through VFC, but > I’d really want to integrate in SO as I need BPMN support. Or does VFC > provides hooks to trigger BPMN flow in SO? > > Suraj, > > What you linked is to provision a new cloud in ONAP. > > What I’m looking for is how SO can leverage this new type of cloud seamlessly > to deploy VNF in there. > As of now, SO let you instantiate only on OpenStack/Rackspace, based on the > code itself. > I’m looking for what is required to get SO use multivim instead. More > precisely, I’m looking for design document, workflow to understand what the > supposed interaction should be. > > Thanks, > Alexis > > > On Feb 19, 2018, at 11:56 AM, Bisht, Suraj (Nokia - US/Irving) > <suraj.bi...@nokia.com <mailto:suraj.bi...@nokia.com>> wrote: > > Hi, > > Kindly follow attached procedure to configure Multi-VIM. It has steps for AAI > as well as MSO > > Thanks, > Suraj > > From: onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org> > [mailto:onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of Avdhut Kholkar > Sent: Sunday, February 18, 2018 9:59 PM > To: Alexis de Talhouët <adetalhoue...@gmail.com > <mailto:adetalhoue...@gmail.com>>; onap-discuss <onap-discuss@lists.onap.org > <mailto:onap-discuss@lists.onap.org>> > Subject: Re: [onap-discuss] [SO][Multicloud] How to get SO deploy VNF using > Multicloud on any type of VIM? > > As far as I am aware, SO does not integrate with Multicloud. There is no > adaptor in SO that interfaces with Multicloud. > The VoLTE use case had SO integrated with VFC/NFVO which in turn interfaces > with Multicloud. I was also looking for something similar and was hoping that > the VoLTE use case had integrated SO and multivim but that was not the case. > The other Amsterdam use cases do not use multivim. > I maybe wrong and the multicloud experts can clarify. > > Regards, > Avdhut Kholkar > > From: onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org> > [mailto:onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of Alexis de Talhouët > Sent: Sunday, February 18, 2018 10:04 PM > To: onap-discuss <onap-discuss@lists.onap.org > <mailto:onap-discuss@lists.onap.org>> > Subject: [onap-discuss] [SO][Multicloud] How to get SO deploy VNF using > Multicloud on any type of VIM? > > Hi SO and Multicloud experts, > > Can SO seamlessly hand off request to multicloud in Amsterdam? or master? > > How such process is / would be working? I tried to look for > design/integration doc but couldn’t find any. I landed here: > https://jira.onap.org/browse/MULTICLOUD-21 > <https://jira.onap.org/browse/MULTICLOUD-21> but not much is explained in the > ticket. > > Looking at the code, I could find only one implementation of MsoVnfAdapter > here: > https://github.com/onap/so/tree/master/adapters/mso-vnf-adapter/src/main/java/org/openecomp/mso/adapters/vnf > > <https://github.com/onap/so/tree/master/adapters/mso-vnf-adapter/src/main/java/org/openecomp/mso/adapters/vnf> > > I need to deploy VNFs on a specific type of VIM, not OpenStack, nor > Rackspace, my impression was I need to create the multicloud driver for this > VIM, and then, auto-magically, SO would be able to get to this driver. How? > Can SO fetch VIM info from AAI in the case of use using multicloud ? > > Please help me understand what is there and how it should be done, so I can > understand the missing pieces and help toward that goal. > > Alexis > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, you may review > athttps://www.amdocs.com/about/email-disclaimer > <https://www.amdocs.com/about/email-disclaimer> > 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) > <Mail Attachment.eml>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
