Page History

Policy/(APPC)

HPA

1-regression

3-enhancements

All: Test Only except Policy

APPC(TO)

Policy: Committed

Policy: Committed

SDC, SO, SDN-C,OOF,ExternalAPI, UUI, ESR,Modeling,MultiVIM/Cloud, VFC, Modeling, DCAE, Policy, Holmes,

Consistent ID of a cloud region

AAI: TO

DCAE: TO

ExtAPI: TO

Multi-VIM: Test support

Holmes: C

SDC: Partially committed based on Chinamobile/ZTE/Vodafone/Fujitsu contribution

SO: Committed based on the contributions from CMCC, ZTE and VDF for the main flows

SDN-C/CCSDK : Committed based on contributions from Huawei and ZTE

VF-C: Committed

Modeling: Committed

Usecase-UI: Committed

Holmes: Committed based on Huawei and ZTE contribution

Multi-VIM/Cloud: Committed based on VMware contribution

Policy: Committed base on Huawei contribution

ExtAPI: Committed as long as a serviceOrder is created, either for service creation or modification with full service characteristics and values. ExtAPI can not read service characteristic and service state from AAI which does not expose those informations.

Dev/Test provided by Chinamobile, Vodafone, Huawei,

ZTE, WindRiver, VMWare, Intel, Lenovo, ChinaTelecom, Fujitsu

5G: PNF

Pre-onboarding

Onboarding

SDC: C

VNFSDK: C

SDC: Committed based on Ericsson contribution

VNFSDK: Committed based on Nokia contribution

VNFRQTS: Committed based on Ericsson contribution

DCAE: C

DMaaP: C

DCAE: Committed based on Ericsson contribution

DMaaP: Committed

5G: PNF PnP

e2e automation

SDC: C

SO: C

SDNC: C

CCSDK: C

SDNC: NETCONF/TLS support in controller committed from Ericsson

Additional development (SDC, SO, CCSDK) for PNF configuration UC is coordinated with CDS / e2e automation. See separate row for details.

PNF configuration testing: Ericsson

SO: (not a separate initiative uses E2E automation) assign/config building block

5G: Bulk PM

5G: PNF OB

Y

5G: PNF OB

Control Loop U/C

SDN-C: C

DCAE: C

OOF: C

Policy: C

SDNC: TechMahindra with help from AT&T

DCAE: Committed based on Wipro contribution

OOF: Commit

Policy: Committed based on Wipro contribution

SDC: C

Port: C

VID: C

SO: C

A&AI: C

SDN-C: C

DCAE: C

AAF: C

Portal: Commit (AT&T)

VID: Commit

SO: Committed based on the contributions from Nokia (confirmed)

A&AI: Commit

CCSDK/SDN-C : Committed to Tosca ingest changes

DCAE: Committed based on the contributions from Nokia

AAF: Commit

SDC: C

Model: TO

SDC: Commit

Model: Commit

AAI:
(using 5G use case PNF discovery and re-registration: TO

DCAE: C

ExtAPI: C

SDC: TO

SO (using 5G use case PNF discovery and re-registration): TO

Policy: TO

CLAMP: TO

SDNC: C

Modeling: design

DCAE: Committed based on contribution from Huawei, TechM and Nokia

ExternalAPI: Committed

SO: 5G PNF Committed based on the contributions from Nokia /Huawei

SDNC: Committed based on contributions from BBS team

Modeling: contributions from Swisscom/Huawei/Nokia

AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability

Nokia, Swisscom, Huawei,
TechM

APPC(TO, code already exists),

SDN-C: test support only

SO: Support testing effort, changes are likely in.

VFC:Committed

UUI:Committed

VID: Committed based on ATT resources

AT&T

China Mobile

Y

AAI: TO

SO: Code Hardening, Expansion of use-case support, testing

Intel

ARM(???)

CLAMP: Committed (Based on TechM resource commitment)

Policy: Committed (Based on TechM Resource Commitment)

Y

SDC & SO: Committed based on Intel/VMWare contribution

AAI: Partially committed

AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability

Y

SO (C),

VID (C)

SO: Committed (AT&T)

VID: pending final decision from Nokia (stretch goal)

AT&T

Nokia

2

APPC (C),

OOF (C),

A&AI (TO)

APPC: Committed (Orange)

OOF: Committed (Orange)

Orange

OOF (C),

Policy (TO)

Y

Model driven Control Loop Design

DCAE: AT&T Committed

CLAMP: Committed

Policy: Committed

AT&T commits to finding the required resources

SO, SDC, VFC, APPC, SDNC

Y

https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2

https://jira.onap.org/browse/CCSDK-575

SDC: Not committed

APPC: Not committed

SO: Committed based on the code from R3

SDNC: Not committed

VFC: Partially committed

SDC: no resources, not enough info

APPC: no resources

SDNC: no resources

VFC: optimize DB microservice

CDS project will provide Resource assignment functionality

ETSI Alignment

SO plugin to support SOL003 to connect to an external VNFM

Y

SDC: Partially committed (based on Ericsson contribution)

SO: Committed (SOL003) based on contribution from Nokia and Ericsson

AAI: Not Committed

SDC: no resources

.AAI: no resources (detailed impact to be discussed) Action Byuong

 SDC

CLI/VNFSDK

Y

Vodafone, iconectiv, huawei

SO
SDC
CCSDK
OOM
Testsuite
Documentation

Y

Code:
SO
SDC
CCSDK
OOM
Testsuite

APPC (CDS)

TO:
AAI
DMaaP
Policy

SDC:
TechM (C)
IBM (C)

CCSDK:
ATT (C)
Bell   (C)
IBM (C)
Ericsson (C)
TechM (C)

SO:
Ericsson (C)
Bell (C)
ATT (P)

OOM:
Orange (P)
Bell (C)

Testsuite:
Orange (C)
Huawei (C)
Dutch T (C)

Documentation:
Orange (C)
Bell (C)
Dutch T (C)

AAI: TO

S3P - Footprint Optimization (Integration with Alpine)

Alpine is the target, but possibility to use oother based OS (cf TSC 2019-02-28)

SDC: N

CCSDK, CLAMP: Committed

Multi-VIM/loud: committed

Policy: committed

DCAE: Not committed

SDC: no resources

DCAE: Resource constraint

The ONAP Minimal Deployment target OK.

Some attention required for AAI

https://wiki.onap.org/download/attachments/45293323/Dublin-Footprint-Optimizations.pdf?version=1&modificationDate=1544543600000&api=v2

CIA Dublin Release Planning

Checklist and wiki to be published.

SDC: N

CCSDK, CLAMP: Committed

Multi-VIM/loud: committed

Policy: committed

DCAE: Not committed

SDC: no resources

DCAE: Resource constraint

Code OK for Mariadb-galera cluster and Cassandra cluster

A&AI Integrated with Shared Cassandra. SDC has been tested but in discussion with PTL on merging into release.

SDNC and SO (in test - awaiting PTL approval) with mariadb-galera.

SDC: N

CCSDK, CLAMP: Committed

Multi-VIM/loud: committed

Policy: committed

DCAE: Not committed

SDC: no resources

DCAE: Resource constraint

OOM + Integration

(Infrastructure)

Yes with limited scope: Manual PH1

Integration

Logging

OOM

+ ALL (helm charts)

no except devops/scripts

in

oom/integration

OOM:

Linux Foundation (C)

Orange (C)

Bell (C)

Amdocs (C)

Logging:

Bell (C)

Amdocs (C)

Integration:

Yes

https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Security%20-%20Requirements-pa2.pptx?version=1&modificationDate=1544453068000&api=v2

No enforcement to make it happen for all project in Dublin release, but expectation to to completed within El Alto release. This could potentially be a S3P items.

AAI, DCAE, DMaaP, Holmes, Logging, Modeling, MSB, Multi-Cloud, ONAP CLI, UUI, Policy, Portal, SO, VFC, VNFSDK, AAF,CLAMP, MUSIC: Already Integrated

ExtApi, VID: Committed

SDC: Not Committed

CCSDK/SDNC, OOM, APPC, OOM: No

CCSDK/SDNC, APPC: dependency on ODL

OOF (HAS, OSDF): python, not Java

SDC: No resource

OOM: No java code

Yes

OOM (introduction of CNI)/MUSIC capabilities leveraged by initial ONAP Components i.e. OOF, Portal, SDC

Yes

xNF communication security enhancements.

Yes

Slide presented on PTL Call (1/14/2019)

DCAEGEN2-1101 - DCAE enhancements to support certificate authentication for HTTPS.  All HTTPS connections from xNFs go to DCAE so no other projects need to be updated.

DCAEGEN2-978 - DCAE replaces clear text password with hash.

DCAE - Committed based on Nokia's contribution

Controller part (SDNC) committed from Ericsson, see 5G UC. 

Code:
PORTAL, UsecaseUI

Code:

PORTAL

TO:

Policy, VID