Versions Compared

Old Version 9

changes.mady.by.user Pankaj Goyal

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  

M2
vF2F
Issue LoggingFriday 02
Conference

Monday  

M2
vF2FConferenceMonday 12
Issue 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


#DeliverableComments
Complete
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 )

Comments
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)

#Deliverable
0NFG: 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.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 )
Comments
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 requirements

Reference Implementation 1


#Deliverable

Complete

( yes/no )
Comments
1
Finish & Cleanup Lab Requirementch04
  • Need a Topology Diagram.
  • Need Networking/Switching Requirements.


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 Cookbookch076Need 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


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).
    #Deliverable

    Complete

    ( yes/no )    		Comments
    1Cleanup 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
  • 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 )chapter02.md
    Comments
    1
    Chapter 2 - platform requirements stable, CNF requirements included, chapter at "Complete" level.
    Functional CNF Requirements captured in Ch2
    2
    Chapter 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
    Non-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.md
    Traceability to RA2 requirements.
    2

    Kuberef-based RI2 fully delivers RA2 specification.


    3Airship-based RI2 included in chapter04.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

    Complete

    ( yes/no )
    Comments
    1
    initial content for introductionch01
    Define what level CNF testing is for CNTT
    2

    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.
    ch03
    Initial traceability for CNF requirements
    3Increase platform test coverage

    Development














    Panel
    borderColorDarkSalmon
    bgColorDarkSalmon

    Misc - Officers and Collaboration Topics


    #Deliverable

    Complete

    ( yes/no )
    Comments
    1

    CVC Alignment (Trevor Lovett)

    From an CVC/OVP perspective:

  • Minimum viable set of requirements and tests to include in the first iteration of the badge (doesn't have to be every requirement tested initially)
  • Commitment that the test suite will produce results in a format compatible with the OVP portal.
    • Anything else, generally defer to CNTT for what is most valuable to define and test



    2
    34