Versions Compared

Old Version 84

changes.mady.by.user Takamune Cho

Saved on

compared with

New Version 85

changes.mady.by.user Randa Maher

Saved on

Key

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

...


6/19/17 - APPC Project Kick-Off

...

  • Need to follow-up to make sure we don't have any overlap between CDT APPC tool and the "VNF SDK Design Studio" mentioned in the SD-WAN slides.
    • 1/10/18 Update: This action item is closed. The CDT tool creates models that are specific to APPC and are needed for the self-service.  CDT is an APPC tool.

Notes:

  • Contributors for Beijing
    • Following three folks from TechM added for Beijing - Welcome!
      • Atul Shegokar 
      • Sanchita Pathak
      • Shubhada Vaze
    • Resources and Repositories wiki updated/cleanded up 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)

...

Note: Due to LF's Zoom room had a technical issue. We used Taka's private zoom room to alternatively open the meeting. Therefore, some contributors were not able to join. The agenda above will be continuously discussing after holiday.  next week 12/27/2017 weekly meeting will be cancelled. Happy Holidays!!

01/10/18 - APPC Project Weekly Minutes

Agenda:

  • Review Beijing timeline
  • Review Beijing resources
  • Review scope
  • Misc disc

Participants: Randa Maher, Aaron Hay, Patrick Brady, Skip Wonnell, Shubhada Vaze, Takamune Cho, Linda Horn, Veer Rajasekar, Tomasz Kaminski

Notes:

  • Review Beijing Milestones again (https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-ONAPBeijingReleasePlanning)
    • 1/8 - Project Planning closure
    • M1 - 1/18 - M1 review
    • M2 - Functionality Freeze -  2/12
      • no new visible functionality is to be added to the current ONAP release
      • Each Project team has defined and documented their Functional Test Cases
      • A stable document describing the API is documented and available in wiki.
    • M3 - API Freeze - 3/8
      • Mark the end of API and Data Model change. API and Data Model are now Frozen
      • 50% of Functional Test Case are automated.
    • M4 - Code Freeze - 3/29  - 4/5/18 
      • Mark the end of the Features coding
      • 100% of Functional Test Case are automated
    • RC0 - Integration - 4/19
    • RC1
    • RC2
    • Release Delivery - 5/24 - Signoff



  • Review Current Dev resources
  • Review Scope
    • Remove references and use of openecomp and replace  with onap  APPC-13 - In progress
      • Action: Need to follow-up with Michael Lando on his concern….
    • Platform Maturity (or S3P)
      • Performance - cannot commit anything at this point; too many questions and ambigiuty on what needs to be done. Awaiting input from Benchmarking committee
      • Stability - 1 - 72 hours soak test on component level.
      • Resiliency - this item needs clarification - is 1 for local or geo-red manual failover? Regardless, we will align with CCSDK/SNDC since we get our ODL & DB dockers from them. We will work with SDNC team.
      • Security = 1  - CII Passing badge + 50% Test Coverag
      • Scalability -1 -  APPC uses ODL distribution from CCSDK project. Scaling is a function of ODL capabilities - adding nodes to an existing cluster or adding a new cluster
      • Manageability - 1- APPC supports EELF already.
      • Usability - 1


    • Support AAF (Authentication and Authorization Framework) for API access
      • Dependency on AAF project to provide feature (AAF-91) to enable AAF security on the web server level (jetty level). AAF confirmed they will deliver AAF-91 in Beijing.



    • Upgrade ODL version to Nitrogen (driven by CCSDK dependency)
    • Replace MySQL with MariaDB (driven by CCSDK dependency)
    • Increase Code Coverage to 50%
    • Provide support for the following new LCM actions:
  • Following Actions in support of In-place software upgrade
    • QuiesceTraffic
    • ResumeTraffic
    • UpgradeSoftware
    • UpgradePreCheck
    • UpgradePostCheck
    • UpgradeBackup
    • UpgradeBackout
  • Additional LCM actions including:
    • ActionCancel
    • ActionStatus
    • AttachVolume
    • DetachVolume
    • CDT Tool - an APP-C Design Tool enabling VNF owners to create templates and other artifacts for APP-C Configure command (used to apply a post-instantiation configuration) as well as other life cycle commands. Missing piece of functionality for Test Action
    • Documentation updates for Beijing
    • On-going requirements discussion during Beijing to fleshout requirement for vDNS scaling use case for Casablanca…  Pam/Brian/Paul/etc..


Materials for M1:

- Release Planning Template:

• To be filled out by Jan 8. 10 days for review prior to TSC approval on Jan 18.

• Focus on scope and project dependencies

- Release Planning Checklist: To be filled out by Jan 17

  • M2 - Functionality Freeze -  2/12
    • no new visible functionality is to be added to the current ONAP release
    • Each Project team has defined and documented their Functional Test Cases
    • A stable document describing the API is documented and available in wiki.
  • M3 - API Freeze - 3/8
    • Mark the end of API and Data Model change. API and Data Model are now Frozen
    • 50% of Functional Test Case are automated.
  • M4 - Code Freeze - 3/29  - 4/5/18 
    • Mark the end of the Features coding
    • 100% of Functional Test Case are automated
  • RC0 - Integration - 4/19
  • RC1
  • RC2
  • Release Delivery - 5/24 - Signoff
  •  
  • Review Current Dev resources
    • Patrick (Committer) - Dev/test - 100%
    • Skip (Committer) - Dev/test - what %?
    • Marcus (Committer)  - awaiting feedback
    • Ryan   - Dev/tes - 100%
    • Taka - Dev/test - 100%
    • Atul - Dev/test - 50%
    • Shubhada - Dev/test - 70-100%
    • Aaron (test/csit/deployment pairwise lab) - 100%
    • Hector (test/deployment documentation) -  ?
    • Paul  (architect) -
    • Scott (architect/doc support)