Hi Avdhut,
Your understanding of multicloud broker is correct.
And yes, the multicloud will be enhanced to be more flexible so
that :
1, multicloud plugins could register the supported cloud type to multicloud
broker so that the broker will route request accordingly (not hardcoded as it
is in A release)
2, with regard to dependency on MSB, it is possible to come up with the design
to allow multicloud plugins decide by themselves which endpoint to use, hence
to decide to use MSB for request routing or put their host/port into the
endpoint url directly.
3,the name convention could be discussed but it was designed to reconcile the
name convention between multicloud and VFC.
Hope this answered your questions.
Best Regards,
Bin Yang, Solution Readiness Team, Wind River
Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189
Skype: yangbincs993
From: [email protected]
[mailto:[email protected]] On Behalf Of Avdhut Kholkar
Sent: Monday, December 18, 2017 10:01 PM
To: [email protected]
Subject: [onap-discuss] [multicloud] queries on multicloud
Hi,
I have executed the multicloud ‘fake vim’ demo to understand how the multicloud
broker identifies the required plugin. I have a few queries on what I observed.
Can someone from the multicloud team clarify if my understanding is correct and
reply to the queries I have:
1. The multicloud broker queries AAI to find the registered cloud details
– mainly the ‘cloud type’. Query is based on a naming convention used in the
url path of the broker, ‘<cloud name>_<cloud_region>’ (eg. vmware_fake)
2. Based on the ‘cloud type’, it finds the relevant plugin. This seems to
be hardcoded currently.
3. It calls the plugin by changing the URL path – this is also currently
hardcoded. In addition, the path changed is fixed – ../multicloud/ is changed
to ../<name of plugin>/
4. In addition, the path always changes the hostname and port to that of
MSB.
Is there a plan to make it more flexible in the coming release?
1. AAI returns an identity URL when queried for cloud regions. Is it not
used currently – can it not be used?
2. Why is there a strong dependency on MSB. Can it be removed and have an
optional ability to use it, if required. Alternative could be a configuration
of each plugin for the host path and port.
3. Is there a plan to change the hardcoded mapping of cloud type to
plugin to that of a configuration.
4. Is there a plan to not depend on the naming convention used in the
broker url path. (vmware_fake) and instead define a REST API that explicitly
specifies the cloud region and cloud name.
Regards,
Avdhut Kholkar
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement, you may review at
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)
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
