Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The full url will be stored in AAI as part of the identity-url, as shown below:

cloud-region




cloud-owner and cloud-region-id as compound key


cloud-owner

onap:cloud-owner

str

cloud owner name, e.g. att-aic



openo:vendor




cloud-region-id

onap:cloud-region-id

str

RegionOne


cloud-type

onap:cloud-type

str

type of the cloud, decides which multicloud plugin to use, openstack-ocata



openo:type




identity-url

onap:identity-url

str

http://msb.onap.org:80/api/multicloud/v0/{cloudowner}_{region}/identity/v3

  • For username & password, APPC stores the credential locally in a properties file and these are passed to OpenStack to authenticate. For R1, this will remain the same. APPC will make no changes to this existing functionality.
  • Ethan indicated that credential would be stored in AAI as part of cloud region, put there by ESR as part of VM info; however, for R1, APPC will not extract username/password from AAI. Implication for testing is that these credentials in properties file must match what is stored in AAI for that cloud instance. 
  • Note that APPC only has 1 set of credential for all cloud instance today.

...

  • APPC/CDP-PAL use HTTPS; need MultiVIM to investigate if they can support HTTPS. Typler Tyler will do likewise to see if HTTP can be supported by CDP-PAL.
  • MutliVIM team is still in discussions on identify-url and how it will get into AAI
  • Question from Policy - does Policy need to send the full url or can APPC look it up based on VNF ID and retrieve it from AAI instead of having it passed in request? Ryan to look into what it would take to retrieve the url.

...

  • Need to confirm URL for testing - Randa & Xinhui to follow-up with Helen
    • Status: Pending   Waiting on details to be provided by Helen
  • Tyler will work on Priority 2 items for openstack mapping by ThrusThurs., 8/17.
    • Status:  Pending, new ETA 8/21/
  • Ryan and Tyler to discuss how to handle endpoints and come back with expectations/assumptions to get all aligned
    • Status: CLOSED - CDP) was under the impression that they would have to manage a different authentication mechanism with VIM; however,  from today's meeting with MultiVIM team,  the confirmed  that the identity url in A&AI would be the same as if were the OpenStack identity. This means that MultiVIM proxy responds identically as OpenStack, so no changes to CDP-PAL.
  • Bin Yang to document all his questions/concerns and send in advance of this meeting so that we can discuss. There is an open action item on what exactly is getting populated in A&AI. APPC get URL from A&AI.
    • Status: CLOSED. Were part of items discussed in 8/18 meeting.

...