Versions Compared

Version Old Version 20 New Version Current
Changes made by

Rabi Abdel

Rabi Abdel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
titleTable of Contents


Table of Content Zone

Table of Contents
maxLevel3
exclude1\.1
stylenone




Panel
borderColorDarkSalmon
bgColorDarkSalmon

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


Panel
borderColorDarkSalmon
bgColorDarkSalmon

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.
23

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

OSTK Version

RA-1 for new CNTT OSTK Release

Sept 14, 2020

If and when a new OSTK release selected (Target: June 28th) a new fully self-contained version of RA-1 document will be created.
2

Add SmartNIC

Sept 14, 2020This is dependent on #4 "Finalised RM NFG" and RM Topic #1. May I suggest that we make this a subtopic of #4.
3

Add HW Accel

Sept 14, 2020Cyborg 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 RA-1 Networking Architecture to match RM.

> May 30th.

Sept 14, 2020NFG Date: >May 28th
5Address RA-1 Ch02 missing requirementsSept 14, 2020A number of RA-1 Ch02 requirements are not explicitly addressed in the rest of the document.
6Edge: Incorporate into RA-1 the Edge RM requirements Sept 14, 2020


Reference Implementation 1


2C: Conduct Friendly Cookbook TrialThere was a comments that this should be taken by the adoption WS. A: Outline Trial Partner Expectations & Establish Contact3

A:  Descriptor File requirement finalized

chp05  chp064C: 
#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

Finish & Cleanup Lab Requirement

  • Need a Topology Diagram.
B: 
  • Need Networking/Switching Requirements.
chp04A: 5.2

ch04
2

Descriptor File requirement finalised.

  •  Raja to look at this and confirm.

ch05  ch06
3Add more installer general requirement (e.g. the need for it to be opensource, the result of it needs to be opensource).
chp06A: Need

ch06
4

Finish Cookbook to align with RA-1


ch08
5Finish Lab Cookbook
ch07
6

Need some initial content (are there no gaps? )

chp09

ch09

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
  • evolvement 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
A: 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

Cleanup Chapter 01


Updates to: Ch01: Introduction

don't think LCM should be considered in RC. need discussion within WSC: 3.8.

2 Resiliency Measurements - need to be written

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

don't understand what exactly this means. need discussion within WS

B : 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 VerificationsPart of long-term RC programC: (General) Perform Empirical Validations (against prototype VNFs)Part of long-term RC program

B: 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

don't think RC should emphasiz user interface and deliverables. need discussion within WS

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

(VNF) Ch07: VNF Test Cases Requirements

what exactly does this mean?

A: 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:

don't think it is necessary to compare openstack releases here in RC

Performance Test Tooling, Test Cases, Strategy, and MethodologyAdd to Test Framework/Methodology Chapters
Reference Architecture

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
1Chapter 2 - platform requirements stable, CNF requirements included, chapter at "Complete" level.
chapter02.md
2Chapter 3 - review wording so that "must" / "should" statements are covered in either chapter02 or chapter04 and this is a description of components and interfaces. Chapter at "Complete" level.
chapter03.md
3Chapter 4 - ensure all specifications have a reference ID, provide specifications for all RI2 requirements for this release. Chapter at "Lots of SME feedback".
chapter04.md
4Chapter 4 - provide specification for all requirements (that can be met). Chapter at "DIckering over the finer points".
chapter04.md
5Chapter 5 - review wording so that "must"/"should" style statements are covered in either chapter02 or chapter04 and this is general guidance for securing Kubernetes and associated add-ons.  Make it clear this does not flow into RC2 tests. Chapter at "Lots of SME feedback".
chapter05.md
6Chapter 6 - ensure any requirements not covered by one or more specifications in chapter04 have a gap documented in this chapter.
chapter06.md


Reference Implementation 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
Initial content for introduction. Chapter at "Lots of SME feedback".
chapter01.md
2

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".


chapter02.md
3Initial content for labs requirements - what does any lab need to be able to deploy the Reference Implementation. Chapter at "Still Developing Content".
chapter03.md
4Initial content for lab cookbook - what are the steps anyone needs to run through to deploy the Reference Implementation.  Chapter at "Still Developing Content".
chapter04.md

Development














Reference Conformance 2


#Deliverable

Target Date

( // )

Comments
1initial content for introduction
ch01
2
#Deliverable

Target Date

( // )

Comments
1234

initial content of requirement:

34

Development

Reference Conformance 2

  • 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

















Panel
borderColorDarkSalmon
bgColorDarkSalmon

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










Field Trial Technical Coordinator

#Deliverable

Target Date

( // )

Comments
1


2


Development