Page History

Versions Compared

Key

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

...

6/19/17 - APPC Project Kick-Off

...

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
  - Materials for M1:
    - Release Planning Template:
    - 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 Brady (Committer) - Dev/test - 100%
- Skip Wonnell ~~(Committer~~) - Dev/test - what %?
- Marcus Williams (Committer) % ? awaiting feedback
- Ryan Young - Dev/tes - 100%
- Takamune Cho - Dev/test - 100%
- Atul Shegokar - Dev/test - 50%
- Shubhada Vaze - Dev/test - 70-100%
- Aaron Hay (test/csit/deployment pairwise lab) - 100%
- Hector Anapan-Lavalle (test/deployment documentation) - ?
- Paul Miller (architect) -
- Scott Seabolt (architect/doc support)
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

...

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

...

- .

...

- .

...

1/8 - Project Planning closure
M1 - 1/18 - M1 review

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

...