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 requiring architecture review
• Black - Architecture not yet performed

...

numberOfFixedRows	1
numberOfFixedColumns	4
decimalMark	. (point)

...

JIRA link (REQ)

One issue per requirement.

Instructions

...

...

...

CLAMP - C

DCAE - C

POLICY - C

...

CLAMP - C

DCAE - C

POLICY - C

committed by AT&T

...

...

AT&T

Ericsson

...

All Control Loop Policy Models should be TOSCA Compliant

Operational, Guard Policies

...

...

...

CLAMP - C

POLICY - C

...

CLAMP - C

POLICY - C

committed by AT&T & Ericsson

...

...

AT&T

Ericsson

...

...

...

DCAE - C

POLICY - C

...

DCAE - C

POLICY - C

committed by AT&T

...

...

AT&T

Wipro

...

...

...

CLAMP - C

POLICY- C

...

CLAMP - C

POLICY - C

committed by AT&T

Project Pairwise Testing

Gervais-Martial Ngueko

Pamela Dragosh

...

AT&T

Ericsson

...

...

...

...

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

...

Jira
server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-150

Eric Debeau

Scott Blandford

...

...

Documentation  - DO

Integration - TO

...

DOC - C

POLICY - C

DCAE - C

CLAMP - C

TSC: Which companies will cover this - per component?

...

Bell Canada,

AT&T,

Orange

...

...

...

RANK #2

------------

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

Can still use legacy API - but those components will be removed in the G Release. So they must upgrade in the G-release.

...

SO - C

SDNC - C

OOF - C

POLICY - C

POLICY - C (AT&T & Intel)

OOF - C (Intel)

Need commitments from SDNC and SO

...

...

...

Swaminathan Seetharaman

Shankaranarayanan Puzhavakath Narayanan

...

TSC: Replaced by new E2E Network Slicing Scope

No commitment to cover ExtAPI

...

...

SDC-C

AAI-C

External API

...

Company commitment per component

SDC - C (Amdocs)

AAI - C (Amdocs)

...

...

CMCC

Amdocs

AT&T

Wiprc

Huawei

...

N.K. Shankaranarayanan

Swaminathan Seetharaman

Sandeep Shah

RANK #3

...

...

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

Policy, DCAE, Integration - Wipro commits

OOF, Policy - AT&T commits

SDN-C, Runtime DB - IBM commits

...

...

AT&T

Wipro

IBM

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

...

5G / Run-time Data Persistency (RunTime Config DB) and VES Model relations, VES CM model (CM Notify).

...

...

...

RANK #3

...

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

Controller, RunTimeDB,  - IBM commits

SDC (TO) - AmDocs will commit

DCAE -  Nokia commits

A&AI Testing - IBM will do testing.

...

Nokia

AT&T

...

...

Ericsson

Nokia

...

...

...

RANK #2

...

SDC: C

SO: C

CDS: C

VID: C

Integration: C/DO

VNFRQTS: DO

...

SDC: (C)

SO: (C)

CDS: (C)

VID: (C)

Integration: (C)

Integration, SDC, SO, VID, CDS, and VNFRQTS are committed by Ericsson. SO is committed by Huawei

...

Eric Moore

...

Ericsson

Huawei

...

...

...

SDC: C

Integration: C

VNFRQTS: DO

...

SDC: C

Integration: C

SDC, Integration and VNFRQTS are committed by Ericsson

...

...

...

...

TSC: Please merge with REQ-84

...

Development in R6 will be part of REQ-84

...

Main goals:

• Support use of CDS for LCM actions
• Improved PNF LCM support

...

Jira
server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-53

...

...

SO: C

CCSDK: C

Integration:C

...

SO: C

CCSDK: C

Integration:C

Huawei commitment to SO,CCSDK,Integration

...

Enbo Wang

Huawei

...

...

RANK #2

...

SO: C

CDS: C

Integration:C

...

SO: C

CDS: C

Integration:C

Huawei commitment to SO, CDS, Integration

...

...

...

SDNC: C

DCAE: C

...

SDN-C: C

DCAE: C

SDN-C (A1 adaptor) committed by Ericsson & IBM

DCAE committed by Nokia

...

...

AT&T

Nokia

Ericsson

...

...

RANK #0

ANSWER: There is no S/W development in R6. Company Commitment is commitment to work on Modeling & Architecture work for R6. Most of this U/C will be modeling development.

...

Modeling: DO

VNFRQTS, after UCs agreed: DO

...

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

...

Nokia and Ericsson commit to:
Modeling: C
VNFRQTS: C

...

AT&T

Nokia

Ericsson

Orange

...

No development.

Activity driven by Nokia and Ericsson is Use Case development.

The UCs and modeling are done in synch.

...

...

...

SO: C

DCAE: C

Integration: C

...

SO: C

DCAE: C

Integration: C

SO, DCAE and Integration committed by Ericsson

...

...

DCAE: C

...

DCAE: C

Nokia Commits to DCAE: C Development

...

...

...

...

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

DCAE: DOC

DCAE: VES Event Reg Spec

...

SDC - C

DCAE - C

Nokia Commits to SDC, DCAE - C

...

AT&T

Ericsson

Nokia

...

...

SO: C

CDS: C

Modeling: DOC

Integration: C

...

SO: C

CDS: C

Modeling: P

Integration: C

Huawei commitment to SO, CDS, Integration

...

RANK #0

ANSWER: It is just modeling in R6. AT&T and Nokia commits to working with Modeling S/C work.

...

Nokia

AT&T

...

Jira
server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-134

...

RANK #2

...

DCAE: C

SO: C

VID: C

...

DCAE: C

SO: C

VID: C

NOKIA Committed to DCAE, SO and VID Development

...

...

...

...

RANK #3

...

SDNC: C

Integration: C

...

SDNC: C

Integration: C

SDNC and Integration committed by Ericsson

...

...

...

RANK #2

...

VNFSDK: C

Integration: TO

...

VNFSDK: C

Integration: C

Nokia Commits to VNFSDK and Integration - C

...

...

Nokia

Ericsson

...

...

...

...

AT&T

Ericsson

Huawei

Orange

...

Policy

SDC

...

...

...

APPC

CCSDK/CDS

SO

...

APPC - C

CCSDK - TO

SO - C

APPC - C

CCSDK - C

SO -C (Actor selection of CDS and APPC)

APPC - Nokia Shanghai

CCSDK - Tech Mahindra

SO - Tech Mahindra

...

AT&T

Nokia/Shanghai

Nokia/Poland

Tech Mahindra

Orange

...

...

...

APPC

Integration

...

APPC: C

Integration: C

...

Orange

AT&T

...

...

...

Orange

AT&T

...

...

Policy: C

VID: C

SDC: C

...

Portal partially committed by AT&T, IBM

...

Partially committed by Samsung (to support OJSI tickets)

...

...

AT&T

Samsung

IBM

...

...

Policy: C

VID: C

SDC: C

...

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.

...

...

AT&T

Samsung

IBM

...

...

...

SDC: C

SO: C

SOL003 Adapter: C

SOL005 Adapter: C

ETSI Catalog Mgr: C

SOL002 Adapter: C

SDC (P): partially committed by Ericsson or others with scale back scope

SO (C): committed by Ericsson and others with scale back scope

ETSI Catalog Mgr (C): committed by CMCC

OOF (P): partially committed by Intel

SOL003 Adapter (C): committed by Ericsson or Nokia with scale back scope 

SOL005 Adapter (C): committed by Verizon with scale back scope

SOL002 Adapter (C): committed by Samsung with scale back scope

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 requiring architecture review
• Black - Architecture not yet performed

Tableenhancer
numberOfFixedRows 1 numberOfFixedColumns 4 decimalMark . (point)
Requirement JIRA link (REQ) One issue per requirement. Instructions Owner TSC Ranking M1 Scorecard TSC M1 Approval Link(s) to HLD/LLD if any Dependency (from/to) another project(s) T-Shirt Size (XS, S, M, L, XL) Project's Impact: Test Only (TO), Code (C), Documentation Only (DO) Committed (C)/Partially Committed (P) or not (N) per Impacted projects If Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc) Integration Lead Company Engagement Notes Marco Platania Michael Hwang (MOD) AT&T Ericsson Marco Platania AT&T Ericsson Marco Platania AT&T Wipro DCAE: Commitment based on Wipro Project Pairwise Testing Gervais-Martial Ngueko Pamela Dragosh AT&T Ericsson Abdelmuhaimen Seaudi AT&T Bell Canada Ericsson  Huawei Orange Morgan Richomme Bell Canada, AT&T, Orange Pamela Dragosh AT&T, Intel *Note: Not sure integration lead is needed for modeling Borislav Glozman Swaminathan Seetharaman LIN MENG CMCC Amdocs AT&T Wiprc Huawei Reshmasree c  AT&T Wipro IBM RAN-Simulator will be submitted as part of Demo VNFs repository Sandeep Shah Nokia AT&T Will be a new component, presented at Architecture S/C. N/A Ericsson Nokia Eric Moore Ericsson Huawei André Schmid Ericsson N/A Ericsson Main goals: Support use of CDS for LCM actions Improved PNF LCM support Enbo Wang Huawei Enbo Wang Huawei Sandeep Shah (A1, O1) AT&T Nokia Ericsson DCAE: Impact for adopting new VES domain; Committed based on Nokia support. N/A AT&T Nokia Ericsson Orange No development. Activity driven by Nokia and Ericsson is Use Case development. The UCs and modeling are done in synch. user-3784d        Ericsson DCAE: Committed based on Ericsson support Krzysztof Kuzmicki Nokia DCAE: Committed based on Nokia support Damian Nowak AT&T Ericsson Nokia DCAE: No code impact on VES reg yaml updates yaoguang wang Huawei N/A (No integration or testing impact) Nokia AT&T Modeling work only Krzysztof Kuzmicki Nokia DCAE: SDK Dmaap lib refactor; committed based on Nokia support Mariusz Sobucki Ericsson Krzysztof Kuzmicki Nokia Ericsson Integration will only be for VNF-SDK work, there is not full E2E POB/OB integration in R6. N/A, producing a model file only, not a use case AT&T Ericsson Huawei Orange AT&T Marco Platania AT&T Nokia/Shanghai Nokia/Poland Tech Mahindra Orange @Lukasz Rajewski Orange AT&T @Lukasz Rajewski Orange AT&T Dominik Mizyn (for OJSI tickets) AT&T Samsung IBM 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 Andrew Fenner Ericsson Verizon CMCC Samsung Nokia Intel China Mobile, Tencent, Huawei Merged with E2E Network Slicing use case Swaminathan Seetharaman Chuanyu Chen Zhang Min Wipro,  AT&T, Amdocs, China Mobile, Huawei, Tencent, ZTE DCAE: Review pending; cannot be committed for Guilin as of 10/23 For EXT-API and Runtime DB, to check with the respective PTLs for possible resource commitments, accordingly will take a final call (not blocking for Guilin though) vFirewall:    Ritu Sood Eric Multanen EdgeXFoundry Kiran Kamineni Akraino ICN Distributed Analytics Dileep Ranganathan Rajamohan Mohan Raj Srivahni Chivukula Intel Aarna Tech Mahindra Lukasz Rajewski Konrad Bańka Samuli Silvius Eric Multanen Orange Samsung Intel Marcus Williams Intel Manjunath Ranganathaiah  Intel Prabhu Balan Vodafone James Guistwite Vodafone iconectiv

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

Tableenhancer
numberOfFixedRows 1 numberOfFixedColumns 4 decimalMark . (point)
Type Requirement Owner Link(s) to HLD/LLD if any Dependency (from/to) another project(s) T-Shirt Size (XS, S, M, L, XL) Project's Impact: Test Only (TO), Code (C) Company Engagement Notes M4 Status

SDC: who is doing what is under discussion between Ericsson and others. We have a scale-back workaround solution.

SO: who is doing what is under discussion between Ericsson and others

OOF: if OOF enhancement is not available for Frankfurt, a workaround would be applied (not critical for ETSI Alignment)

...

Ericsson

Verizon

CMCC

Samsung

Nokia

Intel

...

...

SDC

Modelling

...

...

TSC: This requirement is now merged with Network Slicing. No more individual tracking

...

China Mobile,

Tencent,

Huawei

...

E2E Network Slicing

There are two parts:

•  CSMF, NSMF in ONAP with external (core) NSSMF with a plug-in to SO is ArchCom approved.
  That is SO and External API impacts.
  
• External CSMF with NSMF in ONAP with SO plug-in for core NSSM is Arch com approved

The following is not approved:

• How the NSSMF is in ONAP
• Slice across two domains (i.e. core and ran)..

...

...

RANK #3

TSC:

• For the network slcing.  The following is a Go from architecture
  
  • SO plug-in to an External NSSMF (for core).
  • CSMF and NSMF representation in ONAP, and also allowing CSMF external.
  • What is not approved is NSSMF in ONAP; nor connecting two subslices together as that requires the NSSMF and that still needs quite some more discussion.

This should limit the impacts to SO and External API for Frankfurt 

Please re-adjust the RED Cells accordingly. thanks

<Swami> Updated Red cell entries on 4th Nov, 2019

...

SDC - C

SO - C

OOF - C

UUI - C

DCAE - C

POLICY - TO

(Stretch goals: EXT-API, AAI, Runtime DB, SDN-C - though implementation will proceed, code may not become official part of Frankfurt)

AAI - C

EXT-API - C

SDN-C - C

Runtime DB - C

...

(Commitments per component indicated in brackets)

SDC, Modeling - C (Amdocs)

SO - C (Wipro, China Mobile, Huawei)

OOF - C (Wipro, China Mobile, Huawei)

UUI - C (China Mobile, Huawei)

DCAE - C (China Mobile, Huawei)

POLICY- C (Wipro)

Stretch goals commitment:

AAI - C (Amdocs, Huawei)

EXT-API -N

SDN-C - C (Wipro)

Runtime DB - N (Stretch Goal)

...

Runtime DB, SDN-C, EXT-API and AAI are stretch goals. We will discuss with resp. PTLs on possible options, anyhow they are not blocking scope of this use case for Frankfurt.

...

...

Wipro, 

AT&T,

Amdocs,

China Mobile, Huawei, Tencent,

ZTE

For EXT-API and Runtime DB, to check with the respective PTLs for possible resource commitments, accordingly will take a final call (not blocking for Frankfurt though)

...

...

...

...

Code Multi-Cloud : Intel

Testing of SO, Multicloud, SDC: Intel

vFirewall:  

•  Ritu Sood
• Eric Multanen

EdgeXFoundry

• Kiran Kamineni

Akraino ICN Distributed Analytics

• Dileep Ranganathan
• Rajamohan Mohan Raj
• Srivahni Chivukula

...

Intel

Aarna

Tech Mahindra

...

...

...

Integration with CDS

Change Management Frankfurt Extensions

...

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

...

Marcus Williams

Eric Multanen

...

Extending HPA for K8S

...

...

MULTICLOUD: C

OOF:TO

Policy:TO

AAI/ESR:TO

SO: TO

SDC: TO

...

Intel

...

...

...

Intel commits to coding/testing in Multicloud

Manjunath Ranganathaiah

...

Jira
server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-203

...

...

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

...

...

...

SDC - C

VTP - C

...

SDC-iconectiv

VTP-iconectiv

...

...

Vodafone

iconectiv

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

RANK #3

...

...

...

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

POC / Experimentation

POC definition

Tableenhancer
numberOfFixedRows 1 numberOfFixedColumns 4 decimalMark . (point)
Met withEric Debeau/Orange team on 10/25 and they commited to support. Type Requirement Owner Link(s) to HLD/LLD if any Dependency (from/to) another project(s) T-Shirt Size (XS, S, M, L, XL) Project's Impact: Test Only (TO), Code (C) Company Engagement Notes M4 Status POC Acumos - DCAE Integration Scott Blandford Christopher Rath Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-166 M DCAE - C AT&T Orange (Integration/UC support)

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

...