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

Compare with Current View Page History

« Previous Version 264 Next »

The page is intended to summarize all the requirements for Frankfurt Release.

These requirements will be prioritized by the TSC  to realistically fit within the Frankfurt Release Timeline.

The Release Scope should be finalized during the M1 Release Planning milestone at the xxx.

TSC Prioritization (Ranking)

  • RANK #0  – Special GO - fully covered by involved companies
  • RANK #1  – GO “Must Have”
  • RANK #2 - GO “Continuity of previous releases”
  • RANK #3 – GO if PTLs are OK since the impacted applications are less “stretched”
  • RANK #4 – NO GO – Mostly new requirements/features/projects

Requirements Milestones Summary

See also Documenting Release Requirements in JIRA

Epic Link Fix For Versions (all)
Frankfurt Release Guilin Release Honolulu Release Istanbul Release Jakarta Release Kohn Release London Release Montreal Release New Delhi Release Istanbul Maintenance Release 1 Unscheduled T:
5G / OOF SON Enhancement 3 0 0 0 0 0 0 0 0 0 0 3
5G / ORAN & 3GPP Standards Harmonization 3 0 0 0 0 0 0 0 0 0 0 3
5G OOF SON use case requirements for Guilin release 0 1 0 0 0 0 0 0 0 0 0 1
5G Service Modeling in R8 0 0 15 0 0 0 0 0 0 0 2 17
5G SON use case enhancements for Istanbul release 0 0 0 13 0 0 0 0 0 0 0 13
5G SON use case enhancements for Jakarta release 0 0 0 0 14 0 0 0 0 0 0 14
5G SON use case enhancements for Kohn release 0 0 0 0 0 14 0 0 0 0 0 14
5G SON use case enhancements for London release 0 0 0 0 0 0 14 0 0 0 2 16
5G SON Usecase R8 0 0 16 0 0 0 0 0 0 0 2 18
A1 Adapter Extension & A1 Policy Management 0 1 0 0 0 0 0 0 0 0 0 1
A1 Policy Functions Extension - Istanbul 0 0 0 12 0 0 0 0 0 0 0 12
A1 Policy Functions Extension - Jakarta 0 0 0 0 12 0 0 0 0 0 0 12
A1 Policy Functions Extension - Kohn 0 0 1 1 1 13 0 0 0 1 0 13
A1 Policy Functions Extension - London 0 0 0 0 0 0 13 0 0 0 0 13
Add VSP Compliance and Verification Check feature Phase 2 3 0 0 0 0 0 0 0 0 0 0 3
Akraino Distributed Analytics use case 3 0 0 0 0 0 0 0 0 0 0 3
All Control Loop Policy Models should be TOSCA Compliant 3 0 0 0 0 0 0 0 0 0 0 3
APPC Ansible automation with VNF-C LCM support 3 0 0 0 0 0 0 0 0 0 0 3
Architecture - modelling alignment 7 0 0 0 0 0 0 0 0 0 0 7
ASD onboarding package IM / DM 0 0 0 0 12 0 0 0 0 0 0 12
Bulk PM / PM Data Control Extension 0 1 0 0 0 0 0 0 0 0 0 1
Bulk PM / PM Data Control Improvements 0 0 11 0 0 0 0 0 0 0 0 11
Bulk PM / PM Data Control Improvements 0 0 0 12 0 0 0 0 0 0 0 12
Bulk PM / PM Data Control Improvements 0 0 0 0 13 0 0 0 0 0 0 13
CCVPN-E-LINE Service over OTN NNI 3 0 0 0 0 0 0 0 0 0 0 3
Total Unique Issues: 196 22 248 184 189 107 187 1 1 1 84 1216
Showing 25 of 166 statistics.
View in Jira

Use Cases 

Release 6 (Frankfurt) proposed use cases and functional requirements

M1 Scorecard:

  • Green: Use Case will be fully implemented and tested
  • Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).
  • Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.

Architecture:

  • Pink - NO  GO
  • Purple - GO
  • Green - Considered OK not requiring architecture review
Use Case

JIRA link (REQ)

One issue per requirement.

Instructions

Owner(s)Projects or functional requirements impacted for this releasePriority

M1

Scorecard

TSC M1 ApprovalLink(s) to HLD/LLD if anyDependency (from/to) another project(s)

T-Shirt Size (star)

Project's Impact: Test Only (TO), Code (C)Committed (C)/ Partially Committed (P) or not (N) per impacted projectIf Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Integration Lead

Company

Engagement

Notes
Third Party Operational Domain Manager

REQ-17 - Getting issue details... STATUS

Divyang.Patel@team.telstra.com

Atif.Husain@team.telstra.com

nishi.mathur@team.telstra.com

SDC

TSC: Missing information

(see red and blue cells)

Atif - updated the missing information in red and blue cells



Third-party Operational Domain Manager
S

SDC (C)

SO (TO)

AAI (TO)

Changes being done in local setup


[TSC]: What does it mean? No SDC contribution to the ONAP Community.

[Atif]:Changes were temporarily done locally, when the ElAlto branch wasn't cut and we couldn't commit to master

Will commit after review discussion with SDC PTL


[TSC]:What's the status? PTL OK?

[Atif] PTL is OK. Code commit started.

TelstraComplete company commitment for delivery of Frankfurt Scope for this use case
Service Resolver Features

REQ-13 - Getting issue details... STATUS

rene.robert@orange.comSDC, SO, PolicyTSC: NO GO From Archi. Next Step?

Service Resolver

SDC (C), SO (C), AAI (TO)No SO decisionMISSING INFOMISSING INFOOrange
CMPv2 CA Plugin for AAF

REQ-140 - Getting issue details... STATUS

AAF

Integration

TSC: ALL Info provided. GO to be part of the TSC prioritization



XL -

AAF (C)

Integration (C)

AAF: (C)

Integration:(C)

See notes

AT&T

Ericsson

Nokia


Note: Nokia and Ericsson volunteered to work this. As PTL, I approved the path forward (create Client, build plugin, etc) but was unable to create actual REQ. Please consider this working item until them.

(update : REQ-140 - Getting issue details... STATUS  created, at the moment we do not expect multiple release impacts but it has to be further checked)

ALSO... This MAY be a multi-release effort, which will not affect normal Operations in anyway, if CMPv2 isn't completed within Frankfurt.



CCVPN:

E-LINE Service over OTN NNI

REQ-141 - Getting issue details... STATUS

LIN MENGA&AI, SDN-C, OOF, U-UI, SOTSC: All Info provided. Has it been reviewed by the impacted PTLs?



XL 

(Multiple releases)

TO: SO;

C: U-UI, A&AI, OOF, SDN-C

U-UI committed by ChinaMobile;

A&AI committed by Huawei;

OOF committed by Huawei;

SDN-C committed by Huawei


China Mobile, Huawei

End to End Layer 1 Service Management. Modeling the Optical Service

REQ-37 - Getting issue details... STATUS

SDC, SO, AAI

SDN-C,  Modeling, UUI

TSC:See red cells

Need commitments from company/PTL


Raghavan - Updated info on commitments 



Multi-domain Optical Network ServicesCCVPN use-case alignmentXL (Multiple releases)

TO: SDC, ExtAPI

C: UUI, SO, A&AI, SDN-C

SO - C

A&AI - C

SDN-C - C

UUI - C

SDC - TO

ExtAPI - TO

TSC: Which company will develop this?

Code will be committed by Fujitsu


Have gained PTL agreement & JIRA epics have been created under SO, SDNC, A&AIXin Miao

AT&T

Orange

Fujitsu

Working with CCVPN team to align towards common modelling for OTN
Distributed Analytics use case on K8S regions

REQ-195 - Getting issue details... STATUS

Multi-Cloud

See Red cells

Still Arch





Depends on development progress of Multi-Cloud K8S work.

(K8S based Cloud region support (Continue from R4))

XL 

(Multiple releases)

TO

C

TSC: Which company will develop this? Has it been reviewed with PTL?


MISSING INFORMATION

Intel, Aarna, TM


(star) T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

  • XS - <4 Man/Weeks;
  • S - ~6 Man/Weeks;
  • M - ~8 Man/Weeks;
  • L - ~12 Man/Weeks;
  • XL - > 12 Man/Weeks.

Requirements

M1 Scorecard:

  • Green: The requirement will be fully implemented and tested
  • Yellow:  The requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
  • Red: The requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy


Architecture:

  • Pink - NO  GO
  • Purple - GO
  • Green- Considered OK not requireing architecture review


Requirement

JIRA link (REQ)

One issue per requirement.

Instructions

OwnerProject ImpactedPriorityM1 ScorecardTSC M1 ApprovalLink(s) to HLD/LLD if anyDependency (from/to) another project(s)T-Shirt Size (XS, S, M, L, XL) (star)Project's Impact: Test Only (TO), Code (C), Documentation Only (DO)Committed (C)/Partially Committed (P) or not (N) per Impacted projectsIf Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Integration LeadCompany EngagementNotes
Self Serve Control Loops

REQ-9 - Getting issue details... STATUS

CLAMP

DCAE

POLICY

TSC: ALL Info provided. GO to be part of the TSC prioritization

Self Serve Control Loops v2CLAMPXL

CLAMP - C

DCAE - C

POLICY - C

CLAMP - C

DCAE - C

POLICY - C

committed by AT&T


AT&T

All Control Loop Policy Models should be TOSCA Compliant

Operational, Guard Policies

REQ-21 - Getting issue details... STATUS

CLAMP

POLICY

TSC: ALL Info provided. GO to be part of the TSC prioritization

TOSCA Compliant Policy TypesSDCM

CLAMP - C

POLICY - C

CLAMP - C

POLICY - C

committed by AT&T & Ericsson


AT&T, Ericsson
Policy Update Notifications

REQ-25 - Getting issue details... STATUS

DCAE

POLICY

TSC: ALL Info provided. GO to be part of the TSC prioritization

Policy Update Notifications
S

DCAE - C

POLICY - C

DCAE - C

POLICY - C

committed by AT&T


AT&T, WiproDCAE: Commitment based on Wipro
CLAMP Deployment of Policies to PDP Groups

REQ-29 - Getting issue details... STATUS

CLAMP

POLICY

TSC: ALL Info provided. GO to be part of the TSC prioritization

CLAMP Deployment of Policies to PDP Groups
M

CLAMP - C

POLICY- C

CLAMP - C

POLICY - C

committed by AT&T


AT&T
Integration of CDS as Actor in Control Loops

REQ-33 - Getting issue details... STATUS

CLAMP

POLICY

CDS

TSC: ALL Info provided. GO to be part of the TSC prioritizationa

CDS actor support in Policy

REQ-21 - Getting issue details... STATUS

L

CLAMP - C

POLICY - C

CDS - C

Integration - C

CLAMP - C

POLICY - C

CDS - C

Integration - C

Partial commitment from Bell Canada to support Policy+CDS integration.


Partial commitment from Huawei to support 
CDS+CLAMP integration.


undefined undefined

Bruno Sakoto

Adil Mir

Vidyashree Rama

Gaurav Agrawal

AT&T, Bell Canada, Ericsson, 

Huawei

Orange


Control Loop Tutorial Documentation

REQ-150 - Getting issue details... STATUS


DOC

Integration

TSC: See red cell

REQ-150 - Getting issue details... STATUS

CLAMP, DCAE, POLICYM

Documentation  - DO

Integration - TO

DOC - C

POLICY - C

DCAE - C

CLAMP - C

TSC: Which companies will cover this - per component?


Morgan Richomme

Bell Canada,

AT&T,

Orange


Component Upgrades to new Policy Lifecycle API

REQ-162 - Getting issue details... STATUS

SO

SDNC

OOF

POLICY

TSC: See red cell.

What's the side effect if no company will develop SDNC, SO?





M

SO - C

SDNC - C

OOF - C

POLICY - C

POLICY - C

OOF - C

Need commitments from SDNC and SO

TSC: Which companies will cover this - per component?


AT&T, Intel
Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling

REQ-60 - Getting issue details... STATUS

Swaminathan Seetharaman

Shankaranarayanan Puzhavakath Narayanan

SDC

SO

OOF

AAI

Modeling

TSC: See red cell.

NETWORK SLICING in R6 Frankfurt

 SDC

Possibly dependent on  REQ-162 - Getting issue details... STATUS

 L

SDC-C

AAI-C

External API

Company commitment per component
MISSING INFORMATION

CMCC

Amdocs

AT&T

Wiprc

Huawei


5G / OOF SON Enhancement

REQ-154 - Getting issue details... STATUS

DCAE

Policy

Controller

OOF

Runtime DB

TSC: See red cell.

OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt

Runtime DB

Possibly dependent on  REQ-162 - Getting issue details... STATUS

L

POLICY - C

OOF - C

DCAE - C

SDN-C - C

Runtime DB - C

Integration (Demo VNFs) - C

POLICY - C

OOF - C

DCAE - C

SDN-C - C

Runtime DB - C

Integration (Demo VNFs) - C

Company commitment per component


Swaminathan Seetharaman

Wipro

AT&T

RAN-Simulator will be submitted as part of Demo VNFs repository

DCAE: Son-handler update; committed based on Wipro support

5G / Run-time data persistency (RunTime DB / CM): VES Model relations, VES CM model (CM Notify).

REQ-133 - Getting issue details... STATUS

A&AI

Controller

SDC

RunTime DB (new component)

DCAE

TSC: See red cell.

5G CONFIGURATION (RunTime DB)
L

A&AI - TO

SDC - TO

Controller - C

RunTime DB (new component) - C

DCAE - C

A&AI - C

SDC - C

Controller - C

RunTime DB (new component) - C

DCAE - C

Company commitment per component


Sandeep Shah

Nokia

AT&T

Will be a new component, presented at Architecture S/C.
Modeling: GeoLocation Model (and standards harmonization)Modeling work only

Modeling

TSC: No development? Company Commitment or is it a Modeling subcommittee activity?

PNF PLUG and PLAY in R6 FrankfurtAAIMN/AN/A
N/A

Ericsson

Nokia


PNF / PNF Software Upgrade using direct Netconf/Yang interface with PNF

REQ-84 - Getting issue details... STATUS

SDC

VID

SO

CDS

VNFRQTS

Integration

Modeling

TSC: See red cell.

=> Requested information about company commitment has been added



PNF software upgrade in R6 Frankfurt
XL

SDC: C

SO: C

CDS: C

VID: C

Integration: C/DO

VNFRQTS: DO

SDC: (C)

SO: (C)

CDS: (C)

VID: (C)

Integration: (C)

committed by Ericsson & Huawei (SO)


Eric Moore

Ericsson

Huawei


PNF / Enable Schema Update once PNF software is updated

REQ-88 - Getting issue details... STATUS

Modeling

SDC

Integration

VNFRQTS

TSC: See red cell.

=> Requested information about company commitment has been added



PNF software upgrade in R6 Frankfurt
M

SDC: C

Integration: C

VNFRQTS: DO

SDC: C

Integration: C

committed by Ericsson


Ericsson
LCM API Evolution

REQ-92 - Getting issue details... STATUS

Development in R6 will be part of REQ-84


TSC: No development?

Shall we merge with REQ-84?

=> No development in this REQ, ok to merge with REQ-84 if preferred



https://wiki.onap.org/download/attachments/50202249/2019-07-02%20ONAP_R6_Controller_Evolution_LCM_APIs.pptx?api=v2
N/A

Development in R6 will be part of REQ-84

N/A
N/AEricsson

Main goals:

  • Support use of CDS for LCM actions
  • Improved PNF LCM support
PNF / Enhancement on PNF Software Upgrade with EM with Ansible

REQ-53 - Getting issue details... STATUS


SO

SDNC

Integration

TSC: See red cell.

PNF software upgrade in R6 FrankfurtLCM API EvolutionM

SO: C

SDNC: C

Integration:C

SO: C

SDNC: C

Integration:C

Company commitment per component


Enbo Wang


Huawei


PNF / PNF Software Upgrade with EM with Netconf

REQ-96 - Getting issue details... STATUS

yaoguang wang

SO

CDS

Integration

TSC: See red cell.

PNF software upgrade in R6 FrankfurtPNF Software Upgrade using direct Netconf/Yang interface with PNFM

SO: C

CDS: C

Integration:C

SO: C

CDS: C

Integration:C

Company commitment per component


Enbo WangHuawei
Modeling: 5G / ORAN & 3GPP Standards Harmonization

REQ-38 - Getting issue details... STATUS

Modeling Only for Frankfurt

Modeling

SDN-C

DCEA


TSC: See red cell.

MOBILITY STANDARDS HARMONIZATION WITH ONAP
M

SDNC: C

DCAE: C

SDN-C: C

DCAE: C

SDN-C (A1 adaptor) committed by Ericsson

Company commitment per component


Dongho Kim

Marge Hillis

Vimal Begwani

AT&T

Nokia

Ericsson

DCAE: Impact for adopting new VES domain; Committed based on Nokia support.
5G / License Management

REQ-118 - Getting issue details... STATUS

VNFREQ, after UCs agreed

SDC(*)

Modeling

( *) No code or test impact expected in R6 as an outcome of the proposed UC

TSC: No development? Company Commitment or is it a Modeling subcommittee activity?

LICENSING MANAGEMENTSDCMNo code or test impact expected in R6

N/A

AT&T

Nokia

Ericsson

Orange


5G / Bulk PM / PM Control

REQ-129 - Getting issue details... STATUS

SO

DCAE

Integration

TSC: See red cell.

=> Requested information about company commitment has been added



5G Bulk PM in Frankfurt/R6CLAMP/Policy/CDS (REQ-33)XL

SO: C

DCAE: C

Integration: C

SO: C

DCAE: C

Integration: C

SO, DCAE and Integration committed by Ericsson


user-3784d        EricssonDCAE: Committed based on Ericsson support
5G / Bulk PM / Secure Communication between xNFs and ONAP

REQ-136 - Getting issue details... STATUS

Pawel Baniewski

DCAE

Integration

TSC: See red cell.

5G Bulk PM in Frankfurt/R6AAF (REQ-140)S

DCAE: C

DCAE: C

Company commitment is Nokia?


NokiaDCAE: Committed based on Nokia support
5G / PM dictionary

REQ-80 - Getting issue details... STATUS

SDC: GAB Config file

DCAE: VES Event Reg Spec

TSC: See red cell.

FM META DATA & PM DICTIONARY in R6 Frankfurt
S

SDC: Update GAB Config File (no S/W update)

DCAE: DO

SDC - C


DCAE - C

Company commitment per component


Damian Nowak

AT&T

Ericsson

Nokia

DCAE: No code impact on VES reg yaml updates
5G / 5G NRM Network Resource Model (Configuration Mgmt)

REQ-49 - Getting issue details... STATUS

yaoguang wang

SO

CDS

Modeling

Integration

TSC: See red cell.

5G Network Resource Model (NRM) Configuration in R6 Frankfurt
M

SO: C

CDS: C

Modeling: DO

Integration: C

SO: C

CDS: C

Modeling: P

Integration: C

Company commitment per component


yaoguang wangHuawei
5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G ServiceModeling Work Only (No REQ)ModelingTSC: No development? Company Commitment or is it a Modeling subcommittee activity?

5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt
N/AModeling: CModeling: C
N/A (No integration or testing impact)

Nokia

AT&T

Modeling work only
PNF / Plug and Play

REQ-134 - Getting issue details... STATUS


Benjamin Cheung

DCAE

SO

VID

TSC: See red cell.

PNF PLUG and PLAY in R6 FrankfurtAAF (REQ-140)M

DCAE: C

SO: C

VID: C

DCAE: C

SO: C

VID: C

Company commitment per component


NokiaDCAE: SDK Dmaap lib refactor; committed based on Nokia support
PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP

REQ-76 - Getting issue details... STATUS

SDNC

Integration

TSC: See red cell.

=> Requested information about company commitment has been added



Configuration with NETCONF in Frankfurt/R6AAF (REQ-140)M

SDNC: C

Integration: C

SDNC: C

Integration: C

SDNC and Integration committed by Ericsson


Mariusz SobuckiEricsson
PNF / PNF pre-onboarding onboarding

REQ-135 - Getting issue details... STATUS

VNF-SDK

Integration

TSC: See red cell.

PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt
S

VNFSDK: C

Integration: TO

VNFSDK: C

Integration: TO

Company commitment per component


Nokia

Ericsson


Modeling: Runtime instance model based on A&AI reverse engineering

Modeling Work Only REQ-170 - Getting issue details... STATUS

Modeling only. No new implementation requirements

TSC: See red cells

Reverse-engineering AAI data model to Papyrus information modelAAISAAI: C (one bug fix remaining in UML generation tooling)Company commitment per component
MISSING IFNORMATION

AT&T

Ericsson

Huawei

Orange


Modeling: documentation of policy and allotted resource modelModeling Work OnlyKevin Scaggs

Modeling only. No new implementation requirements

TSC: No development? Company Commitment or is it a Modeling subcommittee activity?


Policy

SDC

M



AT&T
Scaling Extensions

REQ-42 - Getting issue details... STATUS

APPC

CCSDK

TSC: See red cell.

Scaling Use Case (Frankfurt)

APPC

CCSDK/CDS

SO

 S-M

APPC - C

CCSDK - TO

SO - M

APPC - C

CCSDK - C

SO -M (Actor selection of CDS and APPC)

Company commitment per component



Marco Platania

AT&T

Nokia/Shanghai

Nokia/Poland

Tech Mahindra

Orange


APPC Ansible automation with VNF-C LCM support / CHM

REQ-191 - Getting issue details... STATUS

APPC

Integration

TSC: ALL Info provided. GO to be part of the TSC prioritization

Change Management Frankfurt Extensions

APPC

Integration

S

APPC: C

Integration: C

APPC and Integration Commited by Orange
@Lukasz Rajewski

Orange

AT&T


vFW Traffic Distribution with Software Upgrade / CHM

REQ-187 - Getting issue details... STATUS

IntegrationTSC: ALL Info provided. GO to be part of the TSC prioritization

Change Management Frankfurt ExtensionsIntegrationXSIntegration: CIntegration Commited by Orange
@Lukasz Rajewski

Orange

AT&T


Portal Security Enhancements

REQ-64 - Getting issue details... STATUS

Manoop TalasilaPORTALTSC: If partially committed - then please provide what will be the committed deliverables.?


MUSICL

Policy: C

VID: C

SDC: C

Portal partially committed by AT&T, IBM

Partially committed by Samsung (to support OJSI tickets)

Dominik Mizyn (for OJSI tickets)

AT&T

Samsung

IBM


Portal Technology Stack Upgrade and New reporting features

REQ-68 - Getting issue details... STATUS

Manoop TalasilaPORTALTSC: if no resource to support portal/sdk is it still viable?



XL

Policy: C

VID: C

SDC: C

Portal committed by AT&T, IBM

Partially committed by Samsung (to support Springboot upgrade on "portal" repo)

Partially committed by IBM for test automation

GAPS: No resources to support portal/sdk repo for Springboot upgrade.

Sireesh Chintamani (Overall Integration Lead)

Sunder Tattavarada  (for Angular upgrade)

Dominik Mizyn (for Springboot upgrade on "portal" repo)

Leimeng Shi (for reporting feature)

AT&T

Samsung

IBM


ETSI Alignment Support

REQ-101 - Getting issue details... STATUS

SDC

Modeling

SO

VFC

OOF

Integration

TSC: If partially committed - then please provide what will be the committed deliverables.?

ETSI Alignment Support
XL

SDC: C

SO: C

VFC/ETSI Catalog: C

Integration: C

OOF: C

SDC (P)

SO (C)

VFC/ETSI Catalog (C)

Integration (C)

OOF (P)

Company commitment per component

GAPs: OOF enhancement is requested for resource-level Homing. If not, there is a workaround. 

SDC is looking for resources

Andrew Fenner

Ericsson

Verizon

CMCC

Samsung


Architecture - Modelling Alignment

REQ-110 - Getting issue details... STATUS

Stephen Terrill

SDC

Modelling

TSC: No development? Company Commitment or is it a Modeling subcommittee activity?



L





Vertical Industry Oriented On-demand 5G Slice Service (this is merged with Network Slicing use case, and has become E2E Network Slicing)

REQ-146 - Getting issue details... STATUS

LIN MENGModeling, U-UI, SO, DCAETSC: NO GO From Archi. Next Step?








China Mobile,

Tencent,

Huawei

Merged with Network Slicing use case
E2E Network Slicing

REQ-158 - Getting issue details... STATUS

REQ-146 - Getting issue details... STATUS

SO, AAI, OOF, SDN-C, EXT-API, U-UI, Policy, DCAE, ModelingTSC: NO GO From Archi. Next Step?

NETWORK SLICING in R6 FrankfurtSDCXL

SO - C

OOF - C

SDN-C - C

AAI - C

EXT-API - C

UUI - C

DCAE - C

POLICY - TO

SO - C

OOF - C

SDN-C - C

AAI - N

EXT-API - C

UUI - C

DCAE - C

POLICY - C


Wipro, AT&T,

Amdocs,

China Mobile, Huawei, Tencent


Remove Python2 dependencies

REQ-174 - Getting issue details... STATUS

David McBrideALL projects using Python1- NEED Company to commit - MUST HAVE



M





Multicloud K8s Support (Continuation from R4) 

REQ-178 - Getting issue details... STATUS

MultiCloud K8s

SO

SDC

See red cells

K8S based Cloud region support (Continue from R4)

Multi-Cloud : CCompany commitment per component
MISSING Information

Intel

Aarna

Tech Mahindra


K8s CDS Support

REQ-182 - Getting issue details... STATUS

Multicloud K8s

CDS

Integration

TSC: ALL Info provided. GO to be part of the TSC prioritization

Integration with CDS

Change Management Frankfurt Extensions


S-M

MULTICLOUD: C

CDS: C

Integration: C

SO: TO

SDC: TO

CDS commited by Orange and Samsung

MULTICLOUD commited by Samsung, Orange and Intel

Integration commited by Samsung, Orange and Intel 


Orange

Samsung

Intel


K8s HPA Support

REQ-183 - Getting issue details... STATUS

Multicloud K8s, AAI/ESR, Policy, OOF, SO, SDC 

TSC: ALL Info provided. GO to be part of the TSC prioritization

Extending HPA for K8S

Multicloud K8s

REQ-162 - Getting issue details... STATUS


MULTICLOUD: C

OOF:TO

Policy:TO

AAI/ESR:TO

SO: TO

SDC: TO

Intel commits to coding in Multicloud and testing in OOF, Policy, AAI, SO, SDC
Marcus Williams

Intel


 K8s Security and traffic  controller

  REQ-171 - Getting issue details... STATUS

 Multicloud K8sSee red cells


 Multicloud K8sS - MMULTICLOUD: C

Multicloud K8s

Company commitment per component


MISSING INFORMATION Intel
VSP Compliance and Validation Check within SDC  - Phase 2

REQ-203 - Getting issue details... STATUS


SDC

See red cells

Requirements introduced after Sept 27th



VSP Compliance and Validation Check within SDC

SDC: C

Company commitment per component

([Prabhu: Reviewed the design with SDC PTL and Vodafone  already committed the code in SDC and code review is in progress)


Prabhu BalanVodafone
OVP Testing and Certification Support Within SDC

REQ-208 - Getting issue details... STATUS

SDC

VTP

See red cells

Requirements introduced after Sept 27th



OVP Testing and Certification Support Within SDC (Frankfurt)

SDC - C

VTP - C

SDC - Vodafone

VTP-iconectiv




SECCOM Code coverage – increase to 60%

REQ-207 - Getting issue details... STATUS

All projects

Feasibility to be reviewed

Some teams got a waiver from previous release












SECCOM Containers configured per secure recommendation

REQ-215 - Getting issue details... STATUS

All projects using containersCandidate for TSC MUST HAVE










SECCOM Java 11 and 13 migration from v8

REQ-219 - Getting issue details... STATUS

All projects using javaFeasibility to be reviewed










SECCOM CII badging – meet targeted Silver and Gold requirements

REQ-223 - Getting issue details... STATUS

All projectsFeasibility to be reviewed










SECCOM Complete the OJSI backlog

REQ-227 - Getting issue details... STATUS

All relevant projects having an entry in OJSIFeasibility to be reviewed










SECCOM HTTPS communication vs. HTTP

REQ-231 - Getting issue details... STATUS

All relevant projects still using http communication instead of httpsCandidate for TSC MUST HAVE










SECCOM Password removal from OOM HELM charts

REQ-235 - Getting issue details... STATUS

All relevant projectsCandidate for TSC MUST HAVE










SECCOM Communication Matrix

REQ-239 - Getting issue details... STATUS

All projectsFeasibility to be reviewed










SECCOM Containers and Kubernetes secure configuration recommendation

REQ-243 - Getting issue details... STATUS

All projects using containersFeasibility to be reviewed










SECCOM Coverity integration by end of Frankfurt

REQ-247 - Getting issue details... STATUS

All projectsFeasibility to be reviewed with LF IT










SECCOM Ingress controller

REQ-251 - Getting issue details... STATUS

All projectsFeasibility to be reviewed










SECCOM ISTIO POC – limited ONAP deployment scope

REQ-255 - Getting issue details... STATUS

AAF + TBCShall we move this req  to POC?










SECCOM Secure communication for 5G – AAF contribution – CMPv2 protocol trial usage 

REQ-259 - Getting issue details... STATUS

Hampus TjäderAAFWhat's the difference with the Use Case. Shall we only consider this req










SECCOM Perform Software Composition Analysis - Vulnerability tables

REQ-263 - Getting issue details... STATUS

All projectsCandidate for TSC MUST HAVE












(star) T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

  • XS - <4 Man/Weeks;
  • S - ~6 Man/Weeks;
  • M - ~8 Man/Weeks;
  • L - ~12 Man/Weeks;
  • XL - > 12 Man/Weeks.

POC / Experimentation

POC Definition - (In Progress)

TypeRequirementOwnerProject ImpactedLink(s) to HLD/LLD if anyDependency (from/to) another project(s)T-Shirt Size (XS, S, M, L, XL) (star)Project's Impact: Test Only (TO), Code (C)Company EngagementNotesM4 Status

Acumos - DCAE IntegrationDCAE

REQ-166 - Getting issue details... STATUS


MDCAE - CAT&T

(star)T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

  • XS - <4 Man/Weeks;
  • S - ~6 Man/Weeks;
  • M - ~8 Man/Weeks;
  • L - ~12 Man/Weeks;
  • XL - > 12 Man/Weeks.


  • No labels