Skip to end of metadata
Go to start of metadata

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

These requirements have been prioritized by the TSC  to realistically fit within the Dublin Release Timeline.

The Release Scope was finalized during the M1 Release Planning milestone at the TSC on January 31st.


The Requirements extracted from SP lists of priorities for Dublin are covered either by the Use Case, the functional requirements, the non functional requirement or within a project scope of work.

  • Use Cases 
  • Functional Requirements 
  • Non Functional Requirements

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” i.e. CLAMP, Policy, DCAE etc.
  • RANK #4 – NO GO – Mostly new requirements/features/projects

Use Cases 

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.
Use Case Owner(s) Projects or functional requirements impacted for Dublin Priority

M1

Scorecard

TSC M1 Approval M3 Scorecard M3 TSC Approval M4 Scorecard TSC M4 Approval Link(s) to HLD/LLD if any Dependency (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 project If Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)

Company

Engagement

Notes
vFW

Policy/(APPC)

HPA

1-regression

3-enhancements

GREEN

Y

YELLOW

Work done but test is blocked by VID/SO blockers - integration blockers

Y

GREEN

Issue mentioned in the M3 Scorecard has been cleared. Pair-wise testing with APPC was successful. Need to test closed loop when latest Policy containers will be available

Y vFirewall Use Case Upgrade
XS

All: Test Only except Policy

APPC(TO)

Policy: Committed


Policy: Committed

AT&T HPA Testing confirmed by INTEL
vDNS Integration Team HPA 1

GREEN

Y

YELLOW

Test blocked by VID/SO blockers - integration blockers

Y

GREEN

Y


All: Test Only N/A - part of regression tests N/A - part of regression tests
HPA Testing confirmed by INTEL
vCPE (Heat) Integration Team HPA 1

GREEN

Y

YELLOW

Test blocked by VID/SO blockers - integration blockers

Y

GREEN

Y


All: Test Only N/A - part of regression tests N/A - part of regression tests
HPA Testing confirmed by INTEL
CCVPN Use Case (Dublin)   High priority:1, SD-WAN Multi-site to Multi-site service creation; 2, Service change: add or delete a site;3, close loop intelligent surveillance

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

Consistent ID of a cloud region

2

GREEN


Y

YELLOW

CCVPN Dublin Deliverables for API Freeze Milestone Checklist

Multi-sites creation function will be partially implemented.

(Has risks on implementation of coding and testing in SDC) - integration blockers

Y

GREEN

Some bugs related to multi-site creation function in SO will be fixed by next week.

This function is also at high priority in the integration test and the integration team in CCVPN team will spare all the efforts to support this function.

Y CCVPN Use Case (Dublin)
AAI: M

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, VNFSDK, VNFRQTS (Docs) 2 Y Y

GREEN

Codes delivered and ready for integration tests.

5G - PNF Pre-Onboarding / Onboarding Development Status

VNF-SDK-342 is still in progress (Jira) Agreed w Victor

VNFSDK-342 - Getting issue details... STATUS

 


Y

5G - PNF Pre-Onboarding & Onboarding BBS L

SDC: C

VNFSDK: C

SDC: Committed based on Ericsson contribution

VNFSDK: Committed based on Nokia contribution

VNFRQTS: Committed based on Ericsson contribution


AT&T, Huawei, Ericsson, Nokia PNF POB/OB U/C is now in development, requirements and architecture stage with high corporate commitment.
5G: Bulk PM DCAE, DMaaP, VNFRqmt 2 Y Y

GREEN

Code is delivered

Y

5G - Bulk PM (Casablanca carry-over items) 5G: PM Dictionary

DCAE: C

DMaaP: C


DCAE: Committed based on Ericsson contribution

DMaaP: Committed


AT&T, Ericsson, Nokia Bulk PM is in development with high corporate commitment.
5G: Config w/ NetConf SDC, SO, SDNC, CCSDK, VNFRQTS 2 Y Y

GREEN

Functionality delivered in all impacted projects, except one open issue in SO:

SO-1779 - Getting issue details... STATUS

(Bug Fix we are aware of)

Y 5G - Configuration with NETCONF

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


AT&T, Ericsson NetConf is in development with high corporate commitment
5G: FM Meta PM Dictionary SDC, VNFRqmt, VES Specification (Done) 2 Y Y

GREEN

Code is delivered


Y

5G - FM Meta Data / 5G - PM Dictionary

5G: Bulk PM

5G: PNF OB


SDC: C SDC: Commit
AT&T, Ericsson, Nokia FMPM Dictionary is in development with high corporate commitment
5G: OOF & PCI SDC, APP-C, DCAE, OOF, Policy, VNFRqmt 2

GREEN

5G Use Case (R4 Dublin)

Testing resources confirmed by Wipro (Swaminathan S.)

Y

Y

GREEN

All code for Dublin is delivered.


Y 5G - OOF and PCI (Casablanca carry-over items)

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


AT&T, Wipro, Tech Mahindra

OOF/PCI Enhancements is in development with high corporate commitment

Dublin Release Requirements I added policy because my understanding from Dublin Release Requirements there are additions for 5G - OOF and PCI

M4: Two items SDNC-431,433 moved to El Alto)

<please provide the gerrit links for followup>

SDNC-431 - Getting issue details... STATUS

SDNC-433 - Getting issue details... STATUS

5G: PNF Plug and Play & PNF Re-registration SDC, Portal, VID, SO, A&AI, SDN-C, DCAE 2

GREEN

5G Use Case (R4 Dublin)

Confirmed by Dublin Release Requirements that testing resources have been identified

Y Y

GREEN

Code is delivered


Y

5G - PNF Plug and Play (Casablanca carry-over items) BBS

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

AAI: schema / model changes. (Jan 30 Jimmy Forsyth has ok'ed A&AI commitment)

PORTAL: Targets only the top menu integration required for 5G use case functions from VID and SDC/AAI

VID: A&AI schema alignment (agreed)

AT&T, Huawei, Ericsson, Nokia PNF PNP Enhancements is in development with high corporate commitment
5G: Network Slicing SDC, Modeling Sub-committee 2 Y Y

GREEN

Code is delivered, Modeling work in progress.

Y 5G - Slicing

SDC: C

Model: TO

SDC: Commit

Model: Commit


AT&T, Amdocs, Ericsson Network Slicing has only modeling work that is being done in R4.
5G: PNF Software Upgrade SDN-C 2 Y Y

GREEN

Code delivered and into integration stage.

5G - PNF SW Upgrade (Casablanca carry-over items)

Y 5G - PNF SW Upgrade (Casablanca carry-over items)

SDN-C: C SDN-C: Commit based on contributions from Huawei
Huawei
BBS DCAE, ExternalAPI, Modeling, SDNC, SO 0

GREEN

Y Y Y BBS Broadband Service Use Case (Dublin) PRH - 5G Use Case

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



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

Functional Requirements

M1 Scorecard:

  • Green: The functional requirement will be fully implemented and tested
  • Yellow:  The functional requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
  • Red: The functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
Functional Requirement Owner Project Impacted Priority M1 Scorecard TSC M1 Approval M3 Scorecard M3 TSC Approval M4 Scorecard TSC M4 Approval Link(s) to HLD/LLD if any Dependency (from/to) another project(s) T-Shirt Size (XS, S, M, L, XL) (star) Project's Impact: Test Only (TO), Code (C) 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) Company Engagement Notes
Consistent ID of a Cloud Region (Dublin) SDNC & APPC , VID, SO, UUI, VFC, OOF 2

GREEN

Y Y

YELLOW

OOF does not realize this requirement, but can be tested by

Test Plan 2: vFW Use Case covering"Consistent ID of Cloud Region" from Use Case Tracking in Dublin Release


Consistent ID of a Cloud Region (Dublin)

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


Continuation of HPA (Dublin) VNFSDK, SDC, SO, VF-C, OOF, AAI, Policy, Multi-Cloud 2

GREEN

Y

Y

GREEN

Coding is done. Testing now. Finding some issues in Policy related CLI commands. Debugging now.

Y Continuation of HPA (Dublin) SDC - Jira bugs open, OL001 compatibility requirements addressed.

AAI: TO

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


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

Intel

ARM(???)

Development t resources from ARM are required to test HPA support on ARM hardware
Scaling Use Case (Dublin) Main focus on DCAE/CLAMP & Policy 2

GREEN

Y Y

GREEN

Y Scaling Use Case (Dublin)

DCAE: TO

CLAMP: Committed (Based on TechM resource commitment)

Policy: Committed (Based on TechM Resource Commitment)




K8S based Cloud Region Support Multi-Cloud, AAI, SDC, SO 0

GREEN

Y

Y

GREEN

Code delivered in SDC, SO and MultiCloud. Pending Integration.

Y K8S based Cloud Region Support

AAI: TO

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

Intel, VMWare Testing confirmed by INTEL
Change Management Dublin Extensions - Flexible designer/orchestrator SO, VID 2

GREEN

SO (AT&T) and VID

(Nokia) Testing confirmed by CM Team (AT&T)

Y

GREEN

Y

GREEN

VID and SO functionality completed

Y Change Management Dublin Extensions

SO (C),

VID (C)

SO: Committed (AT&T)

VID: pending final decision from Nokia (stretch goal)


AT&T

Nokia


Change Management Dublin Extensions - Traffic Migration
APPC, OOF

2

GREEN

Testing confirmed by Orange and AT&T

Y Y

GREEN

OOF functionality completed and merged.

The portion of code in APPC has been merged.

<if feature not complete already - move to OUTPLAN>

Y Change Management Dublin Extensions

APPC (C),

OOF (C),

A&AI (TO)

APPC: Committed (Orange)

OOF: Committed (Orange)


Orange


Change Management Dublin Extensions - Schedule Optimization OOF 2

GREEN

Testing confirmed by AT&T

Y Y

GREEN

Feature completed; working on code coverage

Y Change Management Dublin Extensions

OOF (C),

Policy (TO)

OOF: Committed (AT&T)
AT&T
Model Driven Control Loop Design (Close Loop sub-committee) DCAE, CLAMP, Policy 3

GREEN

Testing confirmed by AT&T

Y

Y

GREEN

Y

Model driven Control Loop Design





DCAE: AT&T Committed

CLAMP: Committed

Policy: Committed

AT&T commits to finding the required resources

AT&T, Nokia
Modularity

SO, SDC, VFC, APPC, SDNC

3

GREEN

SO Only

Testing confirmed by SO Team

Y


GREEN

Y

GREEN

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

SO, SDC, AAI, 3

GREEN

ETSI Alignment

SOOL003 plug-in to SO

Ericsson confirmed the integration testing resource for the ETSI SOL003-plugin support


Y

GREEN

Y

GREEN

Code delivered in SO and A&AI; working on VNFM Simulator for integration testing

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


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




OSAM/PNF ??? 4

RED

Architecture did not approve

N



???






TOSCA Task Force ??? 4

RED

N



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


OOF: Policy Tosca model API and ONAP CLI integration Intel

Alloted Network Function ??? 4

RED

N



???






Phase 1 - VSP Compliance Check

 SDC

CLI/VNFSDK

 3

GREEN

Prabhu Balan – (prabhu.balan1@vodafone.com) from Vodafone.

Sean Joseph (sjoseph1@iconectiv.com)  from iconnectiv.

Y

GREEN

Y

GREEN

Y  VSP Compliance Check within SDC (Dublin)


SDC: Committed based on contribution from VF, Huawei and iconectiv

Vodafone, iconectiv, huawei




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

Non-Functional Requirements

M1 Scorecard:

  • Green: The non-functional requirement will be fully implemented and tested
  • Yellow: The non-functional requirement will be partially implemented. It is possible to identify capabilities for this non-functional requirement can be tested (phasing approach).
  • Red: The non-functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
Non Functional Requirement Owner Project Impacted Priority M1 Scorecard

TSC M1

Approval

M3 Scorecard M3 TSC Approval M4 Scorecard TSC M4 Approval Link(s) to HLD/LLD if any Dependency (from/to) another project(s) T-Shirt Size (XS, S, M, L, XL) (star) Project's Impact: Test Only (TO), Code (C) 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)
Improve our E2E Process Automation

SO
SDC
CCSDK
OOM
Testsuite
Documentation

1

GREEN

It will not include the following items in Dublin
  1. Support TOSCA network constructs
  2. Single click instantiation (Using VID)

Y


GREEN

Y

GREEN

End 2 End tests to start

Y AAI
AAF
DMaaP
Policy

PNF use case (5G)
XL

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)

OOM + ALL 1

GREEN

Container optimization : on –going (eg SDNC)

Testing Strategy

https://lists.onap.org/g/onap-tsc/message/4605


Y

GREEN

Reduction effort between Casablanca and Dublin

Some old images to be renewed

CIA team will endorse SDC

Optimized Docker excpected to be ready for RC0

Y

GREEN

Y

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

CIA Dublin Release Planning

Documentation by PTL no more useful: the wiki page will provide weekly information:

Effort also required to avoid old images, cf JIRA tickets

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh






SDC: N

CCSDK, CLAMP: Committed

Multi-VIM/loud: committed

Policy: committed

DCAE: Not committed

SDC: no resources


DCAE: Resource constraint

Component/memory optimization: Ongoing Assessment OOM + ALL 1

GREEN

Component/memory optimization: Ongoing Assessment

Testing Strategy

https://lists.onap.org/g/onap-tsc/message/4605


Y

GREEN

Global effort to optimize resources for small installation

Capabilities to configure JAVA_OPTS for Java based images


Y

GREEN


The ONAP Minimal Deployment target OK.

Some attention required for AAI


Y

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

Global optimization (e.g. shared DB) - stretch goal=shared PostgreSQL; shared MariaDB OOM + ALL 1

GREEN

Global optimization (e.g. shared DB) - stretch goal=shared PostgreSQL; shared MariaDB

Testing Strategy

https://lists.onap.org/g/onap-tsc/message/4605


Y

GREEN

Shared DB instance creation on-going

First integration with ONAP component on-going

Y

YELLOW

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.

Y

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

CIA Dublin Release Planning

First component using Shared DB: AAI using Cassandra

List of JIRA tickets

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh




SDC: N

CCSDK, CLAMP: Committed

Multi-VIM/loud: committed

Policy: committed

DCAE: Not committed

SDC: no resources


DCAE: Resource constraint

CI/CD

OOM + Integration

(Infrastructure)


1

GREEN

Manual PH1

Yes with limited scope: Manual PH1


GREEN

Healthcheck gate is operational

Y

GREEN

Infrastructure up , per commit triage working well- thank you Orange 

Y

TSC-25 - Getting issue details... STATUS

Integration

Logging

OOM

+ ALL (helm charts)

L

no except devops/scripts

in

oom/integration

OOM:

Linux Foundation (C)

Orange (C)

Bell (C)

Amdocs (C)

Logging:

Bell (C)

Amdocs (C)

Integration:



Document as You Code ALL 1

GREEN

Yes

GREEN

Y

GREEN

Y Tracked in JIRA - Label: Documentation




Security by Design Security Subcommittee ALL 1

GREEN

Security Checklists integrated to the Release Milestone templates

Yes


GREEN

Y

YELLOW

Yellow

  • Vulnerability Review Tables not finalized for few  projects
  • Some projects missing answers for CII Passing badge and have not added Jim Baker as an editor of their CII badge
  • Some projects still exposing interfaces via HTTP instead of HTTPS



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






Modeling M3 Checklist enhancement Modeling Subcommittee SO, SDC, VFC, APPC, VNFSDK 1

RED

De-scoped from Dublin - TSC decision on 2/21





Proposed M3 Checklist modeling updates discussion


VFC: Committed
Move Helm Chart (OOM) at project level OOM + ALL 1

GREEN

Y

GREEN

In progress: OOM-1240 - Getting issue details... STATUS

Y

YELLOW

Transfer for A&AI targeted for April 18th,2019. Once successful, will transfer:

  • policy
  • aaf
  • appc
  • dcae (awaiting review of documented process before proceeding - see below)

OOM - Development workflow after code transfer to tech teams

Y



During the PTL meeting on 12/17 -it was agreed that

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.

6 projects have been identified for trial: Logging, Policy, APPC, CLAMP, AAI and ONAP CLI

oParent Integration to fix vulnerabilities

Security Subcommittee

Yang Xu

Integration +ALL 1

GREEN

Y

GREEN

Y

GREEN

Y


Modeling: TO

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


Additional functional tests delivered per project on OOM


1

GREEN

Reviewed on 2/14 with the Integration Team

Final presentation to the PTLs on 2/19

Yes



GREEN


Some teams raising requests/risks to get help achieving this by M4.

Y

RED

Lack of people

See Risks



Infrastructure capacity



S3P- Geo-Redundancy

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

2 Yes

GREEN

OOF is running in multiple geos. Portal also using MUSIC. SDC & Policy will be in next release.

Y

GREEN

Y Platform Maturity Resiliency Requirements




SOL 004 (VNF Package Security) SDC, VNFSDK 2


GREEN

Yes

GREEN

Y

RED

Notified 2019-04-19 that the requirement is outplan as of 2019-04-22.


SDC:
SDC-1980 - Getting issue details... STATUS
Jira is for PNF package.

VNFSDK:
Partially implemented in Casablanca
.

VNFSDK-342 - Getting issue details... STATUS




SDC and VNFSDK: Committed based on Ericsson and Nokia contribution.

xNF communication security enhancements.

DCAE 3

GREEN

Testing confirmed by Nokia - Przybysz, Marcin


Yes

YELLOW

ONLY DCAE component. No other projects securing the xNF comms.

Need review at TSC

GREEN


Y

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. 


S3P - Service Mesh (ISTIO) Security & Architecture Subcommittees ALL except MSB or performed at K8S level (OOM); Poc of ISTIO plug-in to AAF not resourced 4

RED

No



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




S3P Manageability - Logging Capabilities

see yellow/red in

in progress

log, aaf cli, consul, contrib, dcae, dmaap, nbi, oof, sdnc, so, uui, vid, vnfsdk, vvp

good

aai, appc, clamp, esr, multicloud, policy, pomba, portal, sdc, vfc


4

RED

No



Library: In progress portal/sdk and possible so library adjustment

PORTAL-348 - Getting issue details... STATUS

Infrastructure: dmaap is adding containers, need to work with other teams in red

DMAAP-853 - Getting issue details... STATUS

as part of overall

LOG-487 - Getting issue details... STATUS

Log

OOM

Portal

SO

AAI


OOM (c)

LOG (c)

Portal (c)

SO (c)

AAI (c)

Multicloud(c)

LOG/POMBA

OOM



Locale/Internationalization language support Portal, UsecaseUI 3

GREEN

No particular Integration Testing required.

Portal/UUI Teams will provide the testing resources

Y

GREEN

Implementation complete - test phase

Waiting for inputs

GREEN

Assume code complete based on M3 feedback


Internationalization language support

PORTAL-267 - Getting issue details... STATUS

PORTAL-376 - Getting issue details... STATUS

PORTAL-377 - Getting issue details... STATUS

Portal, UsecaseUI L

Code:
PORTAL, UsecaseUI

UsecaseUI (C)
Angular 6 Upgrade of ONAP Portal and SDK Portal 3

GREEN

Development Stretch Goal for Dublin. No particular Integration Testing required. Portal container at RC0 will be the final version to be tested

Y

GREEN

Y

GREEN

Implementation and documentation of the Angular upgrade that is scoped in Dublin is complete. Further, new screen changes are being planned to E release (as the Angular upgrade is a huge XL sized effort)

Y

PORTAL-345 - Getting issue details... STATUS

PORTAL-330 - Getting issue details... STATUS

Portal XL

Code:

PORTAL

TO:

Policy, VID

PORTAL (C)


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

Dublin POC / Experimentation

POC Definition - (In Progress)

Type Requirement Owner Project Impacted Link(s) to HLD/LLD if any Dependency (from/to) another project(s) T-Shirt Size (XS, S, M, L, XL) (star) Project's Impact: Test Only (TO), Code (C) Company Engagement Notes M4 Status
Functional Requirement

Self Serve Control Loop (Closed Loop Subcommittee)

DCAE, Policy, SDC


Model driven Control Loop Design

This is a stretch goal for Dublin.  We are still trying to align resources so that this can be accomplished this release



DCAE: Stretch Goal

Policy: Stretch Goal

SDC: Stretch Goal

AT&T

RED

Due to Resource Constraint this will be pushed to the next feature release

Functional Requirement Fine-Grained Placement Service (F-GPS) - Edge Automation
Multi-Cloud, OOF

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

F-GPS (Dublin Summary)


OOF: Committed

MultiVIM/Cloud: Committed

End-to-end Use Case Integration: Stretch Goal (due to several workflow changes)

IBM, AT&T, VMware (Architecture/Modelling), Intel (Architecture),




Sub-Project DataLake DCAE, UUI

https://wiki.onap.org/display/DW/2019+Silicon+Valley+Meeting+Proposals?preview=/53248195/60889728/DataLake-Architecture-implementation.pptx 


XL
China Mobile, QCT

RED

Software is still under development.

Sub-Project Composable Disaggregrated Infrastructure (CDI) @Alex Vul Multi-Cloud



Intel

Non-Functional Requirement

CI/CD

Magic word "run-helm-deploy" in queue at LF, Orange and Log team

Move to POC


OOM + Integration

(Infrastructure)

OOM Gating


Amdocs

Orange

Linux Foundation

Bell

Huawei



Non-Functional Requirement Multi-Architecture Support Components used by vFW

-Healthcheck

-vFW




ARM


RED

Progress stalled - Global - jjb is a higher priority.

Functional Requirement ETSI Alignment

SO plugin to support SOL005 to connect to an external NFVO

SO, AAI, ESR, VFC, UUI

https://wiki.onap.org/pages/viewpage.action?pageId=58229331

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








Functional Requirements


Distributed Analytics as a Service (Dublin Summary) - Edge Automation

Demo

Distributed Analytics as a Service (Dublin Summary) - Edge Automation






YELLOW

Day-2 Config  and Visualization package is pending.

Non-functional requirements

S3P - Provide Upgrade Capabilities PH1


OOM supported by A&AI, SO, SDC and SDNCWaiting for inputs

Dublin Release Platform Maturity






YELLOW

Partial progress.

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


10 Comments

  1. in label "Logging-Dublin" PORTAL-348 - Getting issue details... STATUS 
 for portal/logging collaboration

  2. for ptl meet

    ONAPARC-264 - Getting issue details... STATUS

    LOG-930 - Getting issue details... STATUS

  3. Andreas Geissler Alexis de Talhouët Eric Debeau On the item "Improve our E2E Process Automation" under non functional requirements, believe we have similar goals. 

    I had consolidated various requirements under the titles -

    1. Support TOSCA network constructs
    2. Single click instantiation (Using VID)
    3. Automation during scale-out
    4. Enable day 0 configuration during instantiation

    Please refer to TSC-98 - Getting issue details... STATUS

    Based on my interactions so far, items 3 and 4 above are being addressed in Dublin release. Please review and if we are on the same lines then we can have this item marked as partially committed.

    Catherine Lefèvre - FYI

    1. Milind, I'm not sure to understand point 1; about point 2, it's a nice to have, but I would argue it's a requirement: this is more of a showcase functionality rather than an E2E Automation functionality. Platform is API-driven, any northbound system can integrate using these APIs; and prod-deployment of ONAP potentially have different northbound system than VID to trigger the orchestration. For point 3 and 4, we do allign.
      I wanted to avoid saying we partially commit to the E2E Automation non-functional requirement as it's one of the must have for SPs based on feedback gathering; but this is more about the message we vehiculate rather than technicality.


  4. Alexis de Talhouët Agree to your view point that only points 3 and 4 really can be categorized under E2E automation. With that then we can say this would be a fully compliant feature for Dublin release.

    1. Thanks Milind Jalwadi , Alexis Chiarello  - I am updating the status to Green with the restrictions

  5. Benjamin Cheung - Why is testing being explicitly called out under the M1 milestone status? HPA testing does not constitute testing of the entire use case...



    1. Alexander Vul  Meow? ... this is a comment meant for Xu Yang (from Integration team) or Catherine Lefèvre / Jim Baker ?

      1. Sorry... I thought that you made the change. Not sure who it's meant for. I assume that the project is GREEN because all the necessary resources have been committed? HPA testing alone is going to cut.