Page History

All Control Loop Policy Models should be TOSCA Compliant

Operational, Guard Policies

GO

Track as #39 on Frankfurt Release Integration Testing Status

CLAMP - C

POLICY - C

CLAMP - C

POLICY - C

committed by AT&T & Ericsson

AT&T

Ericsson

GO

Track as #40 on Frankfurt Release Integration Testing Status

DCAE - C

POLICY - C

DCAE - C

POLICY - C

committed by AT&T

AT&T

Wipro

GO

Track as #41 on Frankfurt Release Integration Testing Status

CLAMP - C

POLICY- C

CLAMP - C

POLICY - C

committed by AT&T

AT&T

Ericsson

GO

Track as #42 on Frankfurt Release Integration Testing Status

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

GO

Track as #42 on Frankfurt Release Integration Testing Status

SDNC - C

OOF - C

POLICY - C

POLICY - C (AT&T & Intel)

OOF - C (Intel)

SDNC - C (AT&T)

GO

Track as #9 on Frankfurt Release Integration Testing Status

POLICY - C

OOF - C

DCAE - C

SDN-C - C

Integration (Demo VNFs) - C

(See Notes)

POLICY - C

OOF - C

DCAE - C

SDN-C - C

Integration (Demo VNFs) - C

DCAE, Integration: -      Wipro commits

OOF, Policy: - AT&T commits

SDN-C:    IBM commits

AT&T

Wipro

IBM

RAN-Simulator submitted as part of simulators repo.

Originally Runtime DB was also indicated as a potentially impacted component, however, it is not a part of Frankfurt release. So the necessary functionality for this use case (for Frankfurt) is continued to be realized using ConfigDB.

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

GO

Tracked as item 46: Frankfurt Release Integration Testing Status

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

GO

Track as #23 on Frankfurt Release Integration Testing Status

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

Recommend GO

Track as #24 on Frankfurt Release Integration Testing Status

SDC: C

Integration: C

VNFRQTS: DO

SDC: C

Integration: C

SDC, Integration and VNFRQTS are committed by Ericsson

GO

Track as #16 on Frankfurt Release Integration Testing Status

SO: C

CCSDK: C

Integration:C

SO: C

CCSDK: C

Integration:C

Huawei commitment to SO,CCSDK,Integration

Enbo Wang

Huawei

GO

Track as #37 on Frankfurt Release Integration Testing Status

PNF software upgrade in R6 Frankfurt

Notes: Test procedures and test results will be record soon in: PNF software upgrade with Netconf/Yang interface with EM

SO: C

CDS: C

Integration:C

SO: C

CDS: C

Integration:C

Huawei commitment to SO, CDS, Integration

GO

Track as #22 on Frankfurt Release Integration Testing Status

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

DCAE: Impact for adopting new VES domain; Committed based on Nokia support.

A1 Adapter implementation has been tested against A1 Mediator (1.0.0)

GO

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.

GO

Track as #6 on Frankfurt Release Integration Testing Status

REQ-25

REQ-33

REQ-134

DCAE: C

Integration: C

SO: TO

AAI: TO

CLAMP: TO

Policy: TO

SDNC: TO

CCSDK: TO

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

GO

Track as #38 on Frankfurt Release Integration Testing Status

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

GO

Track as #5 on Frankfurt Release Integration Testing Status

DCAE: C

SO: C

VID: C

DCAE: C

SO: C

VID: C

NOKIA Committed to DCAE, SO and VID Development

DCAE: SDK Dmaap lib refactor; committed based on Nokia support

16.04:

Currently released image for SO-BPMN (1.6.0 form27'th of March) is not working.

Image from today 16.04 is sufficient and works. v2/onap/so/bpmn-infra/manifests/1.6.0-20200416T0645 
→ There will be need to release new SO images

GO

Track as #43 on Frankfurt Release Integration Testing Status

SDNC: C

Integration: C

SDNC: C

Integration: C

SDNC and Integration committed by Ericsson

GO

Track as #8 on Frankfurt Release Integration Testing Status

VNFSDK: C

Integration: TO

VNFSDK: C

Integration: C

Nokia Commits to VNFSDK and Integration - C

Nokia

Ericsson

16.04:

New image has been released /onap/vnfsdk/refrepo:1.5.1 

• package integrity rules are present (SOL004 option 1) - need to have prepared  automated test cases
• PNF SW update validation rules are present need to have prepared  automated test cases
• Full integration  automation of pre-onboarding and onboarding tests is ongoing

AT&T

Ericsson

Huawei

Orange

SDC

GO

Track as #11 on Frankfurt Release Integration Testing Status

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

GO

Track as #15 on Frankfurt Release Integration Testing Status

APPC

Integration

APPC: C

Integration: C

Orange

AT&T

GO

Track as #15 on Frankfurt Release Integration Testing Status

Orange

AT&T

GO

Portal is ready with docker tag 3.2.0-STAGING-latest, however on-top of working to release the dockers as "3.2.0" final tag.

Angular Upgrade to latest version

Performance and Optimization

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

Implementation completed. Documentation still to be updated.

Very close to release first version of docker images in staging to start the pairwise testing.

GO

Track as #26 on Frankfurt Release Integration Testing Status

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)

GO

Track as #10 on Frankfurt Release Integration Testing Status

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

YES

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

GO

Track as #19 on Frankfurt Release Integration Testing Status

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

GO

See REQ-219 for project status

Discuss on PTL call

YELLOW

Although majority of project plans to upgrade java in Guilin release, some of them already migrated in Frankfurt.

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

YES

YES