Page History

...

• Communication - IRC channel (#onap-appc)
  
  • https://www.irccloud.com/#!/ircs://chat.freenode.net:6697/%23onap-appc
  • Thank you Marcus for setting this up.
    
  • We will need to be able to communicate in real-time as testing kicks off in earnest, so this is important.
    
  • AT&T folks will need to request approval to unblock irccloud.com domain- I will share details, SLA is not quick…
• Labs
  
  • Marco Platania has a rackspace lab that is used to deploy new dockers on daily basis, so we will be running through some level of integration testing to make sure we are not breaking anything. We will not have access to do dev testing in this lab, but we may possible request some specific tests. Marco will reach out to APPC if he sees problems.
  • Additionally, Hector is working on his internal lab - making good progress.He was able to bring up a fully working (as far as passing healthchecks go) ONAP instance, We didn't get a chance to discuss this one, we can get more next week.
  •  Lab with vCPE? Still under discussion, no conclusion yet.
• Sonar
  • We have been given a target for unit test/code coverage for R1 - 30% - 50%
  • There is an issue with Sonar not reporting correct data (we were at 18%, but now shows 0%)
  • Ticket opened with LF Helpdesk (ONAP Helpdesk #43745), no response yet.
• R1 blockers
  
  • List was started as part of Virtual developers event - can be found here:
    
    • https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers
  • I added dependency on ODL Docker from SDNC tean.
    
  • Do you have any other you want to add?
• OpenECOMP vs. ONAP renaming (APPC-13)
  
• This came up as a topic in PTL weekly call
• Making change from openecomp to onap has wide and extensive implications, cannot be accommodated in R1 without impacting other scope.
• Discussion being taken up by TSC - proposal is to identify plan in R1, execute in R2
• Waiting on guidance for this story.
  

08/

...

09/17 - APPC Project Weekly Minutes

Agenda:

• APPC/CDP-PAL/MultiVIM      - integration discussion
• Sprint 1 Status
• Documentation

...

• APPC/CDP-PAL/MultiVIM      integration discussion
• Primes:
• APPC - Ryan Young and Scott Seabolt
• CDP-PAL - Satish Addagada  and Tyler Smith
• MultiVIM - Xinhui Li  and Bin Yang
• Plan
• Assumptions
• Impacts
• Deadlines
• • CDP-PAL
    • In order to make expected 8/20 deadline, we will implement the following solution.
    • We will take in the following properties (actual values are subject to change, based upon discussion):

• Based upon those properties, we will route our API calls through the MultiVIM service url.

• • • APPC
      • Will require development to handle new URL format
    • MutlVIM
      • Already working on their keystone proxy
      • Additional information on MultiVIM plan can be found in attached slides:
        • ONAP_MultiCloud_API_July_31.pptx
    • R1 Priority
      • Support actions needed by APPC to support vCPE use case are a must. Identified as Priority 1 in attached file. Priority 2 items are needed to be able to validate other functionality offered by APPC, but not needed to support R1 use cases, but would like to have in R1 (mitigatiion plan is for APPC to be able to support both MultiVIM and CDP-PAL URL formats)
        • AppC_CDP_PAL_Multivim_Openstack_API_Mapping-v2.xlsx
    • Sync-up calls
      • Three sync-up calls will be setup in case we need to address technical questions that may arise:
        • Friday 8/11, Tuesday 8/15, and Thursday 8/17

• Assumptions
  • CDP-PAL
    • When invoking the authentication API call to MultiVIM’s identity url (passing in the openstack username, password, and identity service URL), we will get a token identical to the one we would normally receive from Openstack.

    • In order to access the Openstack provider API’s through the MultiVIM proxy, we need only replace the OpenStack service base url with the MultiVIM service base url. Furthermore, we expect the API response to be identical to what we would normally get if we had interacted directly with the Openstack Provider API.
      e.g. instead of https://OpenStackServiceURL/v2.0/login, we will use  https://MultiVimProxyServiceURL/v2.0/login.

  • MutliVIM
    • MultiVIM team is aligned with above assumption and is aligned with their plans
• Impacts
  • Development impacts for APPC, CDP-PAL, and MultiVIM teams
• Deadlines
  • All components will be code complete by 8/20 with goal of being able to start pairwise testing week of 8/21 pending availability of an environment
• • Testing- where?
    • Most likely environment for use is the WindRiver Dev2Dev lab being setup by Integration team.
    • Action: Randa to follow-up with Helen and Marco on readiness of this environment for testing start week of 8/21.
    Testing- where?
• Sprint 1 Status
• Documentation

...