1

Edge WS: Add Support for Edge Usecase (Outlines ) 

in the usecase part.

2

More generic To cater all technologies ( VM , Containers )

0

NFG: 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.

3

Data-centre Tier Services and how to integrate them tin RM.

4

Technically make sure RM supports both Containers as well VMs.

we need to analysis where we need to be more agnostic. 

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

Add SmartNIC

Sept 14, 2020

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

Add HW Accel

Sept 14, 2020

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.

NFG: Finalise RA-1 Networking Architecture to match RM.

Sept 14, 2020

NFG Date: >May 28th

Address RA-1 Ch02 missing requirements

Sept 14, 2020

A number of RA-1 Ch02 requirements are not explicitly addressed in the rest of the document.

Edge: Incorporate into RA-1 the Edge RM requirements

Sept 14, 2020

1

Finish & Cleanup Lab Requirement

• Need a Topology Diagram.

• Need Networking/Switching Requirements.

ch04

2

Descriptor File requirement finalised.

ch05  ch06

3

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

ch06

4

Finish Cookbook to align with RA-1

ch08

5

Finish Lab Cookbook

ch07

6

Need some initial content (are there no gaps? )

ch09

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

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

4

Confirm and Validate Cookbook

Ch04 

input will be coming from Field Trials.

1

TBD

2

1

Chapter 2 - platform requirements stable, CNF requirements included, chapter at "Complete" level.

chapter02.md

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

3

Chapter 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

4

Chapter 4 - provide specification for all requirements (that can be met). Chapter at "DIckering over the finer points".

chapter04.md

5

Chapter 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

6

Chapter 6 - ensure any requirements not covered by one or more specifications in chapter04 have a gap documented in this chapter.

chapter06.md

1

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

3

Initial content for labs requirements - what does any lab need to be able to deploy the Reference Implementation. Chapter at "Still Developing Content".

chapter03.md

4

Initial 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

1

initial content for introduction

ch01

2

initial content of requirement:

• 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

1

2

1

2

1

2

1

2

1

2

1

2