Describe the goals of this release ?
- Choose a name
- Scope noted below
- Label update (and documented in Github - link)
Name suggestions ?
- Elbrus (highest peak in Europe)
- Choose a highest mountain that starts with C (Cho Oyu, 8201 m/26,906 ft, – could use release name of ChoOyu)
- Highest mountain on Mars - Olympus
Poll for the release name
What is the schedule ? Friday Monday Friday Friday Friday Tuesday Friday Progress
Milestone Description Date M1 Release Planning Create the high level scope (in sections below) vF2F Conference M2 Issue Logging Create initial list of Github issues, starting with issues that match the scope planned in M1 M3 Freeze Contributions Update content via PRs, matching to issues created in M2/M3 M4 Freeze Proofreading Find typo's, correct with PRs M5 Release Candidate Select release content M6 Release Signoff Package the release, setup tag at ReadTheDocs Week Milestone Status M3 M3 M3 M3 M3 M2
This is a high level list of work that is planned for this release. A subset of this work list below will be completed in this release and be included in the release notes).
A: To be included in this Release.
B: Nice to include in this Release.
C: Low Priority for this Release.
Anuket (Meld - merger of OPNFV and CNTT)
Hardware Infrastructure Management: function and APIs
Primary & secondary networking
Security (workloads and infrastructure) - alignment with ONAP
Life-cycle Management (infrastructure)
Other acceleration technologies
Model for an Enterprise Cloud
Multi/hybrid cloud from Data Centre to Edge
|6||Special use cases|
Mutual discovery (workloads/infrastructure)
Service function chaining
Reference Architecture 1 (updated September 15)
Incorporate Edge technologies and deployment considerations
Discussion/Ideas: CNTT Edge - RA01 ( OpenStack ) Architecture - Scenario
|2||Update Security Chapter||Align with RM Requirements|
|3||Update LCM Chapter||Ensure completeness and alignment with RM LCM changes|
|5||Align with RM requirements||Align RM and RA1 requirements|
Reference Implementation 1
Reference Conformance 1
Reference Architecture 2
|1||Functional CNF Requirements captured in Ch2|
|2||Non-functional CNF requirements captured in Ch2|
|3||Traceability completeness improvement|
|4||Improve completeness of requirements relevant to RC2|
|5||Improve completeness of Ch4 (specification)|
|6||Add content to Ch3 sub-sections of 3.2.1|
|7||Improve completeness of Ch5 (security)|
Reference Implementation 2
|1||Traceability to RA2 requirements.|
Kuberef-based RI2 fully delivers RA2 specification.
|3||Airship-based RI2 included in chapter04.md.|
Reference Conformance 2
|1||Define what level CNF testing is for CNTT|
|2||Initial traceability for CNF requirements|
|3||Increase platform test coverage|