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

Compare with Current View Page History

« Previous Version 13 Next »

Table of Contents

Overview

The intention of this page is to outline what CNTT "success" looks like by June @ LFN DDF 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 (In General)

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

A: To be included in Hallasan Release.

B: Nice to include in Hallasan Release.

C: Low Priority for Hallasan Release.

Reference Model


#Deliverable

Target Date

( // )

Comments
0Finalise Networking Modeling.

1

Add Support for Edge Usecase (Outlines ) 



2

add HW Accel capabilities ( include SmartNIC) 



3

More generic To cater all technologies ( VM , Containers )





Reference Architecture 1


#Deliverable

Target Date

( // )

Comments
1

Update OSTK Version



2

Add SmartNIC



3Add HW Accel

4






Reference Implementation 1


#Deliverable

Target Date

( // )

Comments
1

A: Close Gaps in Cookbook

[RC1 Ch9 - Snezka F2F] RC Cookbook Enhancements #945 

[RI1 Ch07] User Manual initial content #408

User-Execution

  • Common Failure codes, description, and resolutions
  • Test Framework Clean-Up Utility, Process, and Support Expectations

Process / Version Mgmt

  • Process for version control
  • Process for bug fixes and patches
  • Containers Tagged
  • Playbooks grab the tagged version


2C: Conduct Friendly Cookbook Trial
There was a comments that this should be taken by the adoption WS. 

A: Outline Trial Partner Expectations & Establish Contact

3

A:  Descriptor File requirement finalized


chp05  chp06
4
  • C: Need a Topology Diagram.
  • B: Need Networking/Switching Requirements.

chp04

A: 5.2 Add more installer general requirement (e.g. the need for it to be opensource, the result of it needs to be opensource).
chp06

A: Need some initial content (are there no gaps? )


chp09

Development


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

B: 1.7 Results Collation & Presentation - write section on where/how results will be normalized, collated, and presented

C: 1.8 Governance - expand to include LCM, define partnerships and expectations from these partners as to what info or support is exchanged, or provided

C:  [RC1 Ch01] Provide Verification Process, including Life Cycle Management #159


Updates to: Ch01: Introduction


C: 3.8.2 Resiliency Measurements - need to be written


Updates to: (NFVI) Ch03: NFVI Test Cases Requirements


C: Review the applicability for, &/or Create content for Test Case Traceability of the following:

5.3.8 Tenants
5.3.9 LCM
5.3.10 Assurance
5.3.11 Security
5.3.13 Resilience
5.3.14 Bare-metal validations


Updates to: (NFVI) Ch05:  NFVI Test Cases and Traceability to CNTT Requirements


C: (General) Create Tools & Perform Hardware & Manifest Verifications
Part of long-term RC program

C: (General) Perform Empirical Validations (against prototype VNFs)
Part of long-term RC program

C: 6.2.2. Prototype VNFs - Identify reference VNFs per Family Types to be used for Empirical Data Collection and evaluation against 'real' VNFs

C: Expand (elaborate) the following which has no/limited content today:

  • 6.4.11 User & System Interfaces - lacks context, lists only UI and Programming Interfacce

  • 6.4.12 Deliverables - needs content to describe by Docker and Standalone Installation Scripts are needed and pertinent for VNF Frameworks


(VNF) Ch06: VNF Testing Framework Requirements

C: 7.5 Interaction Type - Describe the types of Interactions: Extended Topology, Complex (Akraino), Functional, HA, Fault, Interoperability
(VNF) Ch07: VNF Test Cases Requirements

B: Chapter needs community review and inputs - integrated NFVI framework (Section 8.3) is missing context, or reference to prior NFVI E2E Framework chapters.  Clean up needed.

e.g. Content examples to add 

  • Identify Framework Needs, Goals, and Dependencies
  • Define Opensource Integration (OPNFV, OVP, Functest, CVC, others)
  • Provide Automation Toolchain (list, topology, flow)

Missing content needs to be reviewed/vetted for inclusion, and if needed, write content:

8.2.2. Yardstick - purpose, adoption &/or use of project, define why important

8.2.3 Bottlenecks  - purpose, adoption &/or use of project, define importance


(Dev) Ch08: VNF Testing Cookbook

C: All Chapter Content needs to be written:

  • Introduction - Provide an overview of the purpose for the VNF TC Traceability to RM Requirements chapter
  • RM/RA1 Requirements - define requirements
  • Test Case Traceability - tracing test cases to requirements

(VNF) Ch09: VNF Test Cases and Traceability to CNTT Requirements

B: Content needs to be expanded:

10.2 OpenStack Release Comparisons - need to upload/add existing content regarding detail / comparison of OpenStack releases based on Pike baseline for CNTT RI-1 (e.g. Ocata, Pike, Queens, Stein, etc) 

10.5 Framework Gaps - VTP is referenced as framework gap, but need to also include:

  • Hardware (baremetal) Validations
  • Software (manifest) Validations
  • VVP heat artifact/template validations

(Dev) Ch10: Gap analysis & Development:

Performance Test Tooling, Test Cases, Strategy, and Methodology
Add to Test Framework/Methodology Chapters


Reference Architecture 2


#Deliverable

Target Date

( // )

Comments
1

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



2

More details about component architecture (ch04) - dickering level



3

More details about Interfaces and APIs - dickering level



4

More details about security (deep dive in LA) - dickering level



5More details about LCM (deep dive in LA) - dickering level 





Reference Implementation 2


#Deliverable

Target Date

( // )

Comments
1


2


3


4


Development













Picks for Hallasan




  • No labels