Skip to end of banner
Go to start of banner

CNTT Elbrus Release Cycle

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 47 Next »

Table of Contents

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

Schedule and Progress

What is the schedule ?

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

 

M3

 

M3

 

M3

 

M3

 

M2

To-Do (Spec)

This is a high level list of work that is planned for this release. A subset of this work list below will be completed in this release and be included in the release notes).

A: To be included in this Release.

B: Nice to include in this Release.

C: Low Priority for this Release.

Tech


#DeliverableComments
1

Anuket (Meld - merger of OPNFV and CNTT)


Reference Model


#DeliverableComments
1Network/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
4

Add SmartNIC

RM dependency
5Align with RM requirementsAlign RM and RA1 requirements

Reference Implementation 1


#DeliverableComments
1

2

3

Development (CIRV)








Reference Conformance 1


#DeliverableComments
1



2


Development (CIRV)
1

2





Reference Architecture 2


#DeliverableComments
1Functional 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)

Reference Implementation 2


#DeliverableComments
1Traceability to RA2 requirements.
2

Kuberef-based RI2 fully delivers RA2 specification.


3Airship-based RI2 included in chapter04.md.

Development










Reference Conformance 2


#DeliverableComments
1Define what level CNF testing is for CNTT
2Initial traceability for CNF requirements
3Increase platform test coverage

Development










Misc - Officers and Collaboration Topics

#DeliverableComments
1



2

  • No labels