Versions Compared

Key

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

...


6/19/17 - APPC Project Kick-Off

...

  • CSIT (APPC-104)
    • Working on local environment so that we can validate the test cases using Robot framwork.
    • This continues to be a work in progress; we are supposed to have 50% of planned TC done by M3, but not sure we will hit that
  • Documentaton (APPC-89)
    • Paul Miller will update the API Guide for R1/M3 (APPC-102)
    • Documentation project planning a meeting next week, we will find out more about what they recommend, but we need to keep moving ahead with our updates for M3.
  • Restart Testing in internal ORD instance
    • Have not been able to successfully test restart, still have not been able to get AAI data populated; however, error we are getting suggests that current deployment may not have pick up our code.
    • Action: Patrick to check lab to ensure we have version with code deployed
  • Sonar
  • Tracking deferred Gerrit comments
    • Story APPC-157 opened to track these items for completion.
  • Integration Testing
    • Catherine is working with Helen Chen from Integration team to create a JIRA dashboard to track Integration issues
    • Convention to flag issues openend by Integration Team
      • Label will be used to identify issue are originated by Integration Team
      • Affects Version = Amsterdam Release

08/18/17 - APPC/CDP-PAL/MultiVIM - Touch Base 3

Participants:

RANDA MAHER rx196w@us.att.com, Chenfei Gao cgao@research.att.com, Ryan Young ry303t@att.com, Scott Seabolt js9808@att.com, Bin Yang bin.yang@windriver.com, TYLER SMITH ts4124@us.att.com, Ethan Lynn ethanlynnl@vmware.com, Joseph Chou jc2555@att.com, Pamela Dragosh pdragosh@research.att.com, BECKY L HOTZE bk2371@att.com, Bin Hu bh526r@att.com, ram bagadi rb341d@att.com, Skip Wonnell skip@att.com, Phil Nguyen pn8984@att.com, AARON HAY ah415j@att.com, varun gudisena vg411h@att.com, xinhui li lxinhui@vmware.com, Hector Anapan ha076r@att.com

Meeting Recording:

MultiIVIM Meeting 8-18-17- Touchbase3.mp4

Action Items:

  • Randa to setup a call with Policy and CLAMP to clarify what APPC will be as part of the closed loop in support of vCPE use case
  • Ryan will investigate what additional work would be required if Policy passed the VNFID only and not the full identify URL
  • Bing Yang will investigate if MultiVIM can support https
  • Tyler will investigate if CDP-PAL can support http
  • MultiVIM team still needs to finalize storage of identity-url into AAI - discussion going on with ESR and VID team. 

Conclusion from discussion:

  • 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.

Additional Notes:

  • APPC/CDP-PAL use HTTPS; need MultiVIM to investigate if they can support HTTPS. Typler 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.

Action Items from last week:

  • 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 Thrus., 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.