Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Panel | ||||
---|---|---|---|---|
| ||||
Overview |
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
- TBD
Poll for the release name
Panel | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
Schedule and Progress |
What is the schedule ?
Excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
Schedule https://github.com/cntt-n/CNTT/milestones
|
|
|
Progress
|
Panel | ||||
---|---|---|---|---|
| ||||
To-Do (Spec) |
This is a comprehensive high level list of work that can be doneis planned for this release. A subset of the this work list below will go into Baraque (and will be saved be completed in this release and be included in the release notes for Baraque).
A: To be included in Baraque this Release.
B: Nice to include to include in Baraque this Release.
C: Low Priority for Baraque this Release.
Tech
# | Deliverable |
---|
Comments |
---|
1 |
( yes/no )
Anuket (Meld - merger of OPNFV and CNTT) |
Reference Model
NFG: Add HW Accel capabilities (include SmartNIC)
Better Characterisation of Networking and Storage.
Reference Architecture 1
Complete
( yes/no )
# | Deliverable | Comments |
---|---|---|
1 |
Edge WS: Add Support for Edge Usecase (Outlines )
More generic To cater all technologies ( VM , Containers )
Reference Model
Complete
( yes/no )
Network/Hardware Management | Hardware Infrastructure Management: function and APIs Primary & secondary networking | |
2 | Operations | Security (workloads and infrastructure) - alignment with ONAP Life-cycle Management (infrastructure) Observability/telemetry |
3 | Acceleration | Hardware acceleration SmartNICs Programmable fabric Other acceleration technologies |
4 | Storage | Further details |
5 | Model for an Enterprise Cloud | Multi/hybrid cloud from Data Centre to Edge |
6 | Special use cases | Load balancing Mutual discovery (workloads/infrastructure) Service function chaining |
Reference Architecture 1 (updated September 15)
# | Deliverable | Comments |
---|---|---|
1 | Edge Computing | 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 |
4 | Add SmartNIC | RM dependency |
5 | Align with RM requirements | Align RM and RA1 requirements |
Reference Implementation 1
# | Deliverable |
---|
( yes/no )
Comments |
---|
1 |
Finish & Cleanup Lab Requirement
Need a Topology Diagram.2 |
Descriptor File requirement finalised.
- Raja to look at this and confirm.
Finish Cookbook to align with RA-1
Need some initial content (are there no gaps? )
3 |
Development (CIRV) |
B: Descriptor File - finalize & perform PoC
Refer to:
Reference Conformance 1
# | Deliverable Complete ( yes/no ) | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | Cleanup Chapter 01 | Updates to: Ch01: Introduction don't think LCM should be considered in RC. need discussion within WS | ||||||||
2 | Finalise Requirement:
| Ch02 | 3 | Cleanup and Create Traceability Matrix.
| Ch03 | 4 | Confirm and Validate Cookbook | Ch04 input will be coming from Field Trials. | ||
Development (CIRV) | ||||||||||
1 | TBD | |||||||||
2 | ||||||||||
Reference Architecture 2
# | Deliverable |
---|
( yes/no )
chapter02.mdComments |
---|
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
# | Deliverable |
---|
( yes/no )
Comments |
---|
1 |
Initial content for RI requirements (pull through RA2 specifications) and only add additional requirements if needed. Focus on the desired state. Chapter at "Lots of SME feedback".
Traceability to RA2 requirements. | ||
2 | Kuberef-based RI2 fully delivers RA2 specification. | |
3 | Airship-based RI2 included in chapter04.md. | |
Development | ||
Reference Conformance 2
# | Deliverable |
---|
Complete
( yes/no )
Comments |
---|
1 |
Define what level CNF testing is for CNTT | |
2 |
initial content of requirement:
- Badging/Reporting Requirements.
- Conformance vs Benchmarking.
- Framework Requirements.
- Categories of testing.
Iniitial Traceability Matrix.
- Reference to CNTT Req (RM, RA-1).
- Category (Conformance, Benchmarking).
- Type: Performance, Functional, etc.
- High Level Test Case Definition.
- Criteria (May, Should, Must, Info).
- Covered in the industry (Yes/No)
- Reference to Test Project/Name covering it.
Initial traceability for CNF requirements | ||
3 | Increase platform test coverage | |
Development | ||
Panel | ||||
---|---|---|---|---|
| ||||
Misc - Officers and Collaboration Topics |
# | Deliverable |
---|
Complete
( yes/no )
Comments |
---|
1 |
CVC Alignment (Trevor Lovett)
From an CVC/OVP perspective:
- Minimum viable set of requirements and tests to include in the first iteration of the badge (doesn't have to be every requirement tested initially)
- Commitment that the test suite will produce results in a format compatible with the OVP portal.
- Anything else, generally defer to CNTT for what is most valuable to define and test
2 |