Developer Wiki
Space shortcuts
Page tree

Versions Compared

Old Version 139

changes.mady.by.user Randa Maher

Saved on

compared with

New Version Current

changes.mady.by.user Takamune Cho

Saved on

Key

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

Meeting Dates

...

    • 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
  • Sprint 1 Status

...

  • Contributors for Beijing
  • F2F Santa Clara notes
  • Carrier Grade Requirements..
    • Levels mentioned at last meeting are documented here:Platform Maturity Requirements (aka Carrier Grade)
    • Initial assessment for APPC was based on the survey team responded to from Jason Hunt. APPC ranked as follows:
      • Performance: 0
      • Stability: 0 
      • Resiliency: 1
      • Security: 0
      • Scalability: 1
      • Manageability: 2 
    • Results of assessment shared at F2F based on responding projects (~15 of them)

...

  • Resiliency Testing (Sharon)
    • Sharon shared details on what SDNC is doing to meet the Resiliency testing recuirement for Level 2 (automated failover - single  site) - see slides
    • SDNC is leveraging  Kubernetes and OOM to address resiliency requirements
    • Advantage of using Kubernetes (vs. cluster capabiity of ODL) is that Kubernetes capability to recover a failed node
    • Healthcheck currently is at the pod level to determine if failover will be done or not. Sharon will confirm this.
    • Aaron Hay is the prime for the APPC Resiliency Epic (APPC-414)
    • APPC and SDNC teams will work closely together since there is a lot of synergy to be realized due to similar architectures & dependencies.
  • 72 hr test planning (Scott)
  • Code Coverage
    • Patrick provided a demo on using Junit and Mockito so that everyone can contribute to this requirements.
    • Slides and recording have been posted to wiki: How-To's and other helpful information
    • The Epic to track code coverage contributions is APPC-342
    • There are still ~20K lines of code without coverage; select the module you want to work on and created a story under APPC-342 so that folks know what you're working on and don't duplicate. You can follow Patrick's example (APPC-369)
    • You can use this link to determine the code that still needs coverage: SONAR Coverage
    • Taka will add a story to the backlog to replace powermock with Mockito. This is a backlog item at this point; I think we can get to the 50% with the current set of uncovered lines.
  • CDT repo
  • Manual Scaling
    • Awaiting confirmation of 2 additional resources from AT&T to commit supporting manual configscaleout.
    • If resources are confirmed, we will add this to our scope for Beijing. Note that this is "Manual", not Auto Scaling (ie closed loop)
  • AAF
    • Ryan Young is prime for driving this story: APPC-404
    • We need to secure AAF team's delivery plan for AAF-91 before we can finalize APPC plans for APPC support of AAF.
    • Ryan Young will work with Jonathan Gathman and Sai Gandham from AAF team to coordinate.
    • We need AAF team to deliver their story with sufficient time allowed for APPC to complete their work (develop & test)
  • Security - CII  Passing Badge
  • Review JIRA - housekeeping items
    • We did not get to this topic, we will cover next meeting....
  • Misc - FOSS & Commit Process
  • Ansible code (DG/Adapter)
    • SDNC project has a need for this capability; the current plan is for them to clone this code into CCDSK for Beijing to support their Change Management use case.
    • However since this is common functionality, the proposal is to move this to CCSDK project long term. APPC will not do anything with this in Beijing, but something that needs to be addressed in Cassablanca. 

...

  • Review upcoming milestones & release plan
  • Review action items from last week.
  • Status
    • Security
      • Critical security violations - APPC-656 (Taka)
        • Went through all the critical security items, expect logback, which is is waiting on upgrade of EELF
        • Need to wait until ODL upgrade is completed before we address the remaining items since they may be addressed with newer version of ODL.
        • The level 8 criticals will need to be addressed in Casablanca since there is no version of the software without the vulnerability. 
      • AAF Integration - APPC-404 (Ryan)
        • Working with AAF team on delivery of AAF-91; still not ready yet
        • If work for APPC once feature is delivered is more than just configuration, then APPC-404 is at risk for 3/29.
    • Code Coverage 
      • Current: 43.9%
      • Target: 50%
      • Many tasks and stories opened by team, need those to complete in Sprint 4. Submit as soon as possible so that we can see how we are progressing towards our target.
    • ODL upgrade - APPC-403 (Patrick)
      • Targeting changing features over to the new structure, basically each pom points to its own different parent now. 
      • Push a few features as drafts, trying to figure out how the imports/exports work in this version - lots of work with this release
    • Resiliency
      • APPC-476 and  APPC-666 (Aaron)
        • OOM team has completed moving our charts from the old 1-click method to Helm
        • Moved component we need to a common area
        • However, they run into an issue where the DB does not initialize properly under the new charts; meeting later today
        • In parallel, Aaron has repaired his Kubernetes clustered environments now and once he get info from OOM team, he should be able verify his changes in local APPC env
    • CDT
      • Need to build docker in ONAP; need a volunteer to step up and do the work for this one.
      • Will need a new folder in deployment project, need a docker file to point to tomcat/node.js, pull down artifacts from Nexus and put in docker, etc...
    • ScaleOut
      • APPC-545 (Ramya)
        • mostly completed; reviewing requirements again to ensure nothing overlooked; testing in local environment
      • APPC-683 (Vidhya)
        • APPC Client library change to add support for controller type will be submitted today; will be available for SO as we test in parallel
      • Code changes for ConfigScaleOut for the most part done on APPC, testing is the next big thing.
    • Stability (Scott/Ryan)
      • APPC-457 - test execution
      • Bug; APPC-658 
      • APPC-463 - documentation
      • The framework for the test has been built out, Scott submitted to deployment project, but in terms of actual testing, little progress.
      • Scott on vacation this week; Ryan has been helping AAF team, also dealing with computer issues this week.
      • Still having problems with async responses coming back.
    • Documentation
      • APPC-463 -  (Randa) - updates needed for APPC Client Library guide planned for this sprint.
    • Platform Hardening (Sonar)
      • APPC-13 - pending information from SDC
        • openecomp-tosca-datatype - waiting on ETA from Michael
          • Michael requested that we move away from using artifact directly and use their tosca parser since it's a managed/suportted exposed interface.
          • Action: Create story for Casablanca to move to managed tosca parser and remove direct dependency on openecomp-tosca-datatype
            • Status: CLOSED -
              Jira
              serverONAP JIRA
              serverId425b2b0a-557c-3c0c-b515-579789cceedb
              keyAPPC-736

        • sdc-distribution-client - available now…
      • APPC-660  - need to clear submit
      • Please note:  I did not create a Story in sprint 4 for Sonar issues; I need all effort put into increasing code coverage. This close to code freeze, we need to strategise where effort is going with the limited number fo committers and the other dev work they are doing in addition to reviewing code.
  • Other items
    • CLA - Decision by TSC & LF is to hold off on this for Beijing; it will be required in Casablanc
    • Sonar story for issues - see note above
    • Risks - any more to add?
      • Possibly Code Coverage hitting 50% by 3/29
      • New security issues popping up after ODL upgrade is done.
    • Admin access to APPC in WindRiver to acccess some Openstack comments - provided by Stephen Gooch.
    • MariaDB - this will be pushed out to Casablanca. Confirmed with PTL of CCSDK project that this will move to Cassablanca. 

...