You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

Table of Contents

Overview

The intention of this page is to outline what CNTT "success" looks like by Sep @ LFN ONES 2020, along with high level tracking items that need to be completed.

Success is defined as:

  1. TBD - documentation created ? test suites defined ? test suites executed ?
  2. TBD
  3. TBD

To-Do (Spec)

This is a comprehensive list of work that can be done. A subset of the list below will go into  Baraque (and will be saved in the release notes for Baraque).

A: To be included in Baraque Release.

B: Nice to include in Baraque Release.

C: Low Priority for Baraque Release.

Tech


#Deliverable

Target Date

( // )

Comments
1

Edge WS: Add Support for Edge Usecase (Outlines ) 


in the usecase part.
2

More generic To cater all technologies ( VM , Containers )




Reference Model


#Deliverable

Target Date

( // )

Comments
0NFG: Finalise Networking Modelling by May 30.Finish with stable version
1

NFG: Add HW Accel capabilities (include SmartNIC) 


Based on the modelling done by NFG, SmartNIC support and HW acceleration to be supported by RM.
2

Better Characterisation of Networking and Storage.




3Data-centre Tier Services and how to integrate them tin RM.

4Technically make sure RM supports both Containers as well VMs.
we need to analysis where we need to be more agnostic. 

Reference Architecture 1

#Deliverable

Target Date

( // )

Comments
1

Update RA-1 for new CNTT OSTK Release

Tentative Sept 15, 2020

If and when a new OSTK release selected a new fully self-contained version of RA-1 document will be created.
2

Add SmartNIC


This is dependent on #4 "Finalised RM NFG" and RM Topic #1. May I suggest that we make this a subtopic of #4.
3Add HW Accel
Cyborg is being re-architected and will have a new API (v2) that is not backward compatible. We had included Cyborg and API v1 in the current (Baldy) release but decided to remove.  If the next RA-1 release (Baraque) will be based on a new OSTK release then depending upon the release selected it may or may not be possible to add this topic.
4

NFG: Finalise Networking Architecture to match RM.


> May 30th.


Reference Implementation 1


#Deliverable

Target Date

( // )

Comments
1

Finish & Cleanup Lab Requirement

  • Need a Topology Diagram.
  • Need Networking/Switching Requirements.

Chp04
2

Descriptor File requirement finalised.


chp05  chp06
3Add more installer general requirement (e.g. the need for it to be opensource, the result of it needs to be opensource).
chp06
4

Finish Cookbook to align with RA-1


ch08
5Finish Lab Cookbook
ch07
6

Need some initial content (are there no gaps? )


chp09

Development (CIRV)


B: Resolve Continuous Software Deployment Errors


B: Document & Perform Repeatable CICD Deployment



B: Descriptor File - finalize & perform PoC

Refer to: 

  • [RI 1 Core]: Work with OPNFV Infra WG for the evolvment of PDF to fit into need for CNTT RI #526
  • [RI 1 Labs] Tooling to Generate a PDF matching Airship Internal Data Structure #525



Reference Conformance 1


#Deliverable

Target Date

( // )

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:

  • Badging/Reporting Requirements.
    • Conformance vs Benchmarking.
  • Framework Requirements.
  • Categories of testing.

Ch02

3

Cleanup and Create 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.

Ch03

4Confirm and Validate Cookbook

Ch04 

input will be coming from Field Trials.

Development (CIRV)
1TBD

2







Reference Architecture 2


#Deliverable

Target Date

( // )

Comments
1

More details about component architecture (ch04) - dickering level


ch04
2

More details about Interfaces and APIs - dickering level


ch04
3

More details about security - dickering level


ch05
4Propose solutions to existing gaps (traced back through RA2/RM requirements, linked to specific CNCF or other projects)
ch06

Reference Implementation 2


#Deliverable

Target Date

( // )

Comments
1initial content for introduction
ch01
2initial content for RI requirement.
ch02
3initial content for labs requirements.
ch03
4initial content for lab runbook
ch04

Development













Reference Conformance 2


#Deliverable

Target Date

( // )

Comments
1initial content for introduction
ch01
2

initial content of requirement:

  • Badging/Reporting Requirements.
    • Conformance vs Benchmarking.
  • Framework Requirements.
  • Categories of testing.

ch02
3

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.

ch03




Development













To-Do (Officers)

ONAP Technical Coordinator

#Deliverable

Target Date

( // )

Comments
1


2


Development









CNCF Technical Coordinator

#Deliverable

Target Date

( // )

Comments
1


2


Development









CVC Technical Coordinator

#Deliverable

Target Date

( // )

Comments
1


2


Development









ONF Technical Coordinator

#Deliverable

Target Date

( // )

Comments
1


2


Development









ETSI-NFV Technical Coordinator

#Deliverable

Target Date

( // )

Comments
1


2


Development









  • No labels