Page History

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

AT&T

Ericsson

CLAMP - C

POLICY - C

CDS - C

Integration - C

CLAMP - C

POLICY - C

CDS - C

Integration - C

Vidyashree Rama

Gaurav Agrawal

AT&T

Bell Canada

Ericsson 

Huawei

Orange

Documentation  - DO

Integration - TO

DOC - C (Orange)

POLICY - C (AT&T)

DCAE - C (AT&T)

CLAMP - C (AT&T)

Bell Canada,

AT&T,

Orange

SDNC - C

OOF - C

POLICY - C

POLICY - C (AT&T & Intel)

OOF - C (Intel)

SDNC - C (AT&T)

POLICY - C

OOF - C

DCAE - C

SDN-C - C

Integration (Demo VNFs) - C

Runtime DB - C (see Remarks)

POLICY - C

OOF - C

DCAE - C

SDN-C - C

Runtime DB - C (see Remark(

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

Runtime DB may not be an official ONAP component in Frankfurt, however, the functionality required for our use case will be realized.

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

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

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

SO: C

CCSDK: C

Integration:C

SO: C

CCSDK: C

Integration:C

Huawei commitment to SO,CCSDK,Integration

Enbo Wang

Huawei

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

Modeling: DO

VNFRQTS, after UCs agreed: DO

SDC(*)

( *) 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.

REQ-25

REQ-33

REQ-134

DCAE: C

Integration: C

SO: TO

AAI: TO

CLAMP: TO

Policy: TO

SDNC: TO

CCSDK: TO

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

Nokia

AT&T

DCAE: C

SO: C

VID: C

DCAE: C

SO: C

VID: C

NOKIA Committed to DCAE, SO and VID Development

SDNC: C

SO: TO

Integration: C

SDNC: C

SO: C

Integration: C

SDNC, SO and Integration committed by Ericsson

VNFSDK: C

Integration: TO

VNFSDK: C

Integration: C

Nokia Commits to VNFSDK and Integration - C

Nokia

Ericsson

AT&T

Ericsson

Huawei

Orange

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

SDC: C

Partially committed by Samsung (to support OJSI tickets)

AT&T

Samsung

IBM

Policy: C

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

AT&T

Samsung

IBM

SO: C

SOL003 Adapter: C

SOL005 Adapter: C

ETSI Catalog Mgr: C

SOL002 Adapter: C

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

ETSI Catalog Mgr (C): committed by CMCC

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

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

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

Ericsson

Verizon

CMCC

Samsung

Intel

Lin Meng's comment  (21st Nov):

a) 15th &18th Nov: LinMeng's Mail sent to TSC explaining the "exception".

b) 19th Nov: Steve's clarification of Arc decision in the first column.

c) 20th Nov: Swami's Mail sent to TSC requesting OOF and UUI inclusion in scope (resource commitments and PTL agreements available)

d) 21st Nov: LinMeng updated the columns for impacted modules, commitments based on the request sent to TSC ,  for TSC reference when in discussion

Please help change the status to Green

YES considering

#1 SO, ExtAPI  UUI scope only

#2 NSSMF is outside ONAP

#3 OOF is exceptionally added and will be reviewed at M2

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

Lin Meng (21st Nov)

Confirmation:

1)Yes, we can deliver this feature for Frankfurt even without ExtAPI.

2) The impact in EXT-API for Frankfurt is only minimal impact, the resource has been identified and will be commited.

Please help change the status to YES

(See Notes)

SO : C

EXT-API : C 

POLICY : TO

SDC : TO

A&AI : TO

U-UI : C

OOF : C

LinMeng updated on 21st Nov based on the request sent to TSC for including U-UI and OOF into scope, for TSC reference when in discussion

EXT-API : C (Huawei, Wipro)

SO : C (Wipro, China Mobile, Huawei)

POLICY : C (Wipro)

SDC: C (China Mobile, Amdocs)

A&AI : C (Huawei, Amdocs)

U-UI : C (China Mobile)

OOF : C (AT&T, Wipro)

LinMeng updated on 21st Nov:

Reply to TSC Concern:

1)Yes, we can deliver this feature for Frankfurt even without ExtAPI.

2) The impact in EXT-API for Frankfurt is only minimal impact, the resource has been identified and will be committed.

Wipro, 

Amdocs,

China Mobile, Huawei, Tencent,

AT&T,

Verizon

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

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

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

Some of the tickets may not be closed easily but most of the most severe tickets is being worked on.

to be followed-up via TAC. Pawel to write to Jason