Versions Compared

Old Version 1

changes.mady.by.user Scott Steinbrueck

Saved on

compared with

New Version Current

changes.mady.by.user Rihab Banday

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

Describe the goals of this release ?

  1. Choose a name
  2. Scope noted below
  3. Label update (and documented in Github - link)

Name suggestions ?

  1. Elbrus (highest peak in Europe)
  2. Choose a highest mountain that starts with C (Cho Oyu, 8201 m/26,906 ft, – could use release name of ChoOyu)
  3. Highest mountain on Mars - Olympus
  4. TBD

Poll for the release name

Panel


Vote
renderTitleLevel0
alwaysShowResultstrue
lockedtrue
titleName of Release - Sep 25, 2020
1 - Elbrus (highest peak in Europe)
2 - Choose a highest mountain that starts with C (Cho Oyu, 8201 m/26,906 ft, – could use release name of ChoOyu)
3 - Highest mountain on Mars - Olympus




Panel
borderColorDarkSalmon
bgColorDarkSalmon

Schedule and Progress

What is the schedule ?

Excerpt

Schedule  https://github.com/cntt-n/CNTT/milestones

MilestoneDescription
Date
M1Release PlanningCreate the high level scope (in sections below)

Friday  

vF2FConference

Monday  

M2Issue LoggingCreate initial list of Github issues, starting with issues that match the scope planned in M1

Friday  

M3Freeze ContributionsUpdate content via PRs, matching to issues created in M2/M3

Friday  

M4Freeze ProofreadingFind typo's, correct with PRs

Friday  

M5Release CandidateSelect release content

Tuesday  

M6Release SignoffPackage the release, setup tag at ReadTheDocs

Friday

Progress

WeekMilestoneStatus

 

M3

Image Added

 

M3

Image Added

 

M3

Image Added

 

M3

Image Added

 

M3

Image Added

 

M2

Image Added




Panel
borderColorDarkSalmon
bgColorDarkSalmon

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
Complete
Comments
1

Anuket (Meld - merger of OPNFV and CNTT)


Reference Model


#Deliverable
( yes/no )
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

Complete

( yes/no )

Comments0NFG: Finalise Networking Modelling Finish with stable version1

NFG: Add HW Accel capabilities (include SmartNIC) 

Based on the modelling done by NFG, SmartNIC support and HW acceleration to be supported by RM.
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

3Acceleration

Hardware acceleration

SmartNICs

Programmable fabric

Other acceleration technologies

4StorageFurther details
5

Model for an Enterprise Cloud

Multi/hybrid cloud  from Data Centre to Edge

6Special use cases

Load balancing

Mutual discovery (workloads/infrastructure)

Service function chaining


Reference Architecture 1 (updated September 15)

#DeliverableComments
1

Edge Computing

Incorporate Edge technologies and deployment considerations

Discussion/Ideas: CNTT Edge - RA01 ( OpenStack ) Architecture - Scenario

2Update Security ChapterAlign with RM Requirements
3Update LCM ChapterEnsure completeness and alignment with RM LCM changes
4

Add SmartNIC

RM dependency
5Align with RM requirementsAlign RM and RA1
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

Complete

( yes/no )

Comments1

Update RA-1 for new CNTT OSTK Release

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

This 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

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 RA-1 Networking Architecture to match RM.

NFG Date: >May 28th5Address RA-1 Ch02 missing requirementsA 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

Reference Implementation 1


#Deliverable

Complete

( yes/no )

Comments
1

Finish & Cleanup Lab Requirement

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


2
Descriptor File requirement finalised.ch05  ch06
  •  Raja to look at this and confirm.


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

Finish Cookbook to align with RA-1

ch085Finish Lab Cookbookch076

Need some initial content (are there no gaps? )

ch09


Development (CIRV)

B: Resolve Continuous Software Deployment ErrorsB: Document & Perform Repeatable CICD Deployment

B: Descriptor File - finalize & perform PoC

Refer to: 

  • [RI 1 Core]: Work with OPNFV Infra WG for the 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


#DeliverableComplete

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

  • 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
Complete

( yes/no )

Comments
1
Chapter 2 - platform requirements stable, CNF requirements included, chapter at "Complete" level.chapter02.md2Chapter 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.md3Chapter 4 - ensure all specifications have a reference ID, provide specifications for all RI2 requirements for this release. Chapter at "Lots of SME feedback".chapter04.md4Chapter 4 - provide specification for all requirements (that can be met). Chapter at "DIckering over the finer points".chapter04.md
Functional CNF Requirements captured in Ch2
2Non-functional CNF requirements captured in Ch2
3Traceability completeness improvement
4Improve completeness of requirements relevant to RC2
5Improve completeness of Ch4 (specification)
6Add content to Ch3 sub-sections of 3.2.1
7Improve completeness of Ch5 (security)
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.md6Chapter 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
Complete

( yes/no )

Comments
1
Initial content for introduction. Chapter at "Lots of SME feedback".chapter01.md2

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.md3Initial content for labs requirements - what does any lab need to be able to deploy the Reference Implementation. Chapter at "Still Developing Content".chapter03.md4Initial 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
Traceability to RA2 requirements.
2

Kuberef-based RI2 fully delivers RA2 specification.


3Airship-based RI2 included in chapter04.md.

Development











Reference Conformance 2


#Deliverable
Complete

( yes/no )

Comments
1
initial content for introductionch012

initial content of requirement:

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

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.
Define what level CNF testing is for CNTT
2Initial traceability for CNF requirements
3Increase platform test coverage
ch03

Development














Panel
borderColorDarkSalmon
bgColorDarkSalmon
To

Misc -

Do (

Officers

)

ONAP Technical Coordinator

and Collaboration Topics


#Deliverable

Complete

( yes/no )
Comments
1



2
34