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 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.
Tech
# | Deliverable | Comments |
---|---|---|
1 | Anuket (Meld - merger of OPNFV and CNTT) |
Reference Model
# | Deliverable | Comments |
---|---|---|
1 | 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 |
4 | Add SmartNIC | RM dependency |
5 | Align with RM requirements | Align RM and RA1 requirements |
Reference Implementation 1
# | Deliverable | Comments |
---|---|---|
1 | ||
2 | ||
3 | ||
Development (CIRV) | ||
Reference Conformance 1
# | Deliverable | Comments |
---|---|---|
1 | ||
2 | ||
Development (CIRV) | ||
1 | ||
2 | ||
Reference Architecture 2
# | Deliverable | Comments |
---|---|---|
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 | Comments |
---|---|---|
1 | 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 | Comments |
---|---|---|
1 | Define what level CNF testing is for CNTT | |
2 | Initial traceability for CNF requirements | |
3 | Increase platform test coverage | |
Development | ||
Panel | ||||
---|---|---|---|---|
| ||||
Misc - Officers and Collaboration Topics |
# | Deliverable | Comments |
---|---|---|
1 | ||
2 |