You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 375 Next »

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

M1

Scorecard

TSC M1 ApprovalM3 ScorecardM3 TSC ApprovalM4 ScorecardTSC M4 ApprovalUse CaseOwner(s)Projects or functional requirements impacted for DublinLink(s) to HLD/LLD if anyDependency (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 projectIf Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)

Company

Engagement

Notes

1-regression

3-enhancements

GREEN

Y

YELLOW

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

Y

YELLOW

Blocked by the two Integration blocking issue


vFW

Policy/(APPC)

HPA

vFirewall Use Case Upgrade
XS

All: Test Only except Policy

APPC(TO)

Policy: Committed


Policy: Committed

AT&THPA Testing confirmed by INTEL
1

GREEN

Y

YELLOW

Test blocked by VID/SO blockers - integration blockers

Y

YELLOW

Blocked by the two Integration blocking issue


vDNSIntegration TeamHPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests
HPA Testing confirmed by INTEL
1

GREEN

Y

YELLOW

Test blocked by VID/SO blockers - integration blockers

Y

YELLOW

Blocked by the two Integration blocking issue


vCPE (Heat)Integration TeamHPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests
HPA Testing confirmed by INTEL
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

YELLOW

1. Almost all the coding work in each module has been delivered. (excepts Little work in SO and UUI still in progress, will be hand over ASAP. )

2. Some remaining ending work will be done by this week. 
( partial coding work in SO and SDC are under review now).

3. No big risk for integration test. Multi-site creation function, service change function(add/delete a site), close loop bandwidth adjustment function will be tested in the integration test phase.


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

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


2YY

GREEN

Codes delivered and ready for integration tests.

5G - PNF Pre-Onboarding / Onboarding Development Status

VNF-SDK (stretch goal) code is still being worked. But "base" code is green.



5G: PNF

Pre-onboarding

Onboarding

SDC, VNFSDK, VNFRQTS (Docs)5G - PNF Pre-Onboarding & OnboardingBBSL

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, NokiaPNF POB/OB U/C is now in development, requirements and architecture stage with high corporate commitment.
2YY

GREEN

Code is delivered


5G: Bulk PMDCAE, DMaaP, VNFRqmt5G - Bulk PM (Casablanca carry-over items)5G: PM Dictionary

DCAE: C

DMaaP: C


DCAE: Committed based on Ericsson contribution

DMaaP: Committed


AT&T, Ericsson, NokiaBulk PM is in development with high corporate commitment.
2YY

YELLOW

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

SO-1779 - Getting issue details... STATUS


5G: Config w/ NetConfOskar MalmSDC, SO, SDNC, CCSDK, VNFRQTS5G - 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, EricssonNetConf is in development with high corporate commitment
2YY

GREEN

Code is delivered



5G: FM Meta PM DictionarySDC, VNFRqmt, VES Specification (Done)5G - FM Meta Data / 5G - PM Dictionary

5G: Bulk PM

5G: PNF OB


SDC: CSDC: Commit
AT&T, Ericsson, NokiaFMPM Dictionary is in development with high corporate commitment
2

GREEN

5G Use Case (Dublin)

Testing resources confirmed by Wipro (Swaminathan S.)

Y

Y

YELLOW

Use case is feature complete and code committed.

Code delivered for DCAE and Policy.

For SDN-C, code delivered for 2 items. SDNC-431,433 moved to El Alto. SDNC-431 code complete but not merged.

For OOF code committed, and needs to be merged.


5G: OOF & PCISDC, APP-C, DCAE, OOF, Policy, VNFRqmt5G - 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

2

GREEN

5G Use Case (Dublin)

Confirmed by Dublin Release Requirements that testing resources have been identified

YY

GREEN

Code is delivered



5G: PNF Plug and Play & PNF Re-registrationBenjamin CheungSDC, Portal, VID, SO, A&AI, SDN-C, DCAE5G - 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 James 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, NokiaPNF PNP Enhancements is in development with high corporate commitment
2YY

5G: Network SlicingBorislav GlozmanSDC, Modeling Sub-committee5G - Slicing

SDC: C

Model: TO

SDC: Commit

Model: Commit


AT&T, Amdocs, EricssonNetwork Slicing has only modeling work that is being done in R4.
2YY

GREEN

Codes delivered and ready for integration tests.

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


5G: PNF Software UpgradeUlas KozatSDN-C5G - PNF SW Upgrade (Casablanca carry-over items)

SDN-C: CSDN-C: Commit based on contributions from Huawei
Huawei
0

GREEN

YY

GREEN

Most of the code has been merged or is pending for review.

SO enhancements and APEX policy rule for BBS has been submitted, minor fixes will be done in the next 1-3 days and proceed with testing.

BBS Use Case Tracking (Dublin Release)

BBS System Status


BBSDavid Perez CaparrosDCAE, ExternalAPI, Modeling, SDNC, SOBBS 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
PriorityM1 ScorecardTSC M1 ApprovalM3 ScorecardM3 TSC ApprovalM4 ScorecardTSC M4 ApprovalFunctional RequirementOwnerProject ImpactedLink(s) to HLD/LLD if anyDependency (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 projectsIf Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Company EngagementNotes
2

GREEN

YY

Consistent ID of a Cloud Region (Dublin)Bin YangSDNC & APPC , VID, SO, UUI, VFC, OOFConsistent 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


2

GREEN

Y

Y

YELLOW

Pending code review and integration


Continuation of HPA (Dublin)Alexander VulVNFSDK, SDC, SO, VF-C, OOF, AAI, Policy, Multi-CloudContinuation 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
2

GREEN

YY

GREEN


Scaling Use Case (Dublin)Scott BlandfordMain focus on DCAE/CLAMP & PolicyScaling Use Case (Dublin)

DCAE: TO

CLAMP: Committed (Based on TechM resource commitment)

Policy: Committed (Based on TechM Resource Commitment)




0

GREEN

Y

Y

GREEN

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


K8S based Cloud Region SupportMulti-Cloud, AAI, SDC, SOK8S 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, VMWareTesting confirmed by INTEL
3

GREEN

POC for Dublin under Multi-Cloud umbrella


Y


Y

YELLOW

Day-2 Configuration and Visualization package is pending.


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

Demo


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

Demo (C)Only demo repositoryDay-2 Configuration and Visualization package is pending. Planning to complete this by RC0.VMware, Intel

Testing confirmed by INTEL

2

GREEN

SO (AT&T) and VID

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

Y

GREEN

Y

YELLOW

VID functionality completed; SO blocked by SDC issue in deploying workflow into SO


Change Management Dublin Extensions - Flexible designer/orchestratorSO, VIDChange Management Dublin Extensions

SO (C),

VID (C)

SO: Committed (AT&T)

VID: pending final decision from Nokia (stretch goal)


AT&T

Nokia


2

GREEN

Testing confirmed by Orange and AT&T

YY

YELLOW

Functionality completed; Working on code coverage; code is yet to be merged


Change Management Dublin Extensions - Traffic Migration
APPC, OOFChange Management Dublin Extensions

APPC (C),

OOF (C),

A&AI (TO)

APPC: Committed (Orange)

OOF: Committed (Orange)


Orange


2

GREEN

Testing confirmed by AT&T

YY

YELLOW

Feature completed; working on code coverage


Change Management Dublin Extensions - Schedule OptimizationOOFChange Management Dublin Extensions

OOF (C),

Policy (TO)

OOF: Committed (AT&T)
AT&T
3

GREEN

Testing confirmed by AT&T

Y

YGREEN
Model Driven Control Loop Design (Close Loop sub-committee)DCAE, CLAMP, Policy

Model driven Control Loop Design





DCAE: AT&T Committed

CLAMP: Committed

Policy: Committed

AT&T commits to finding the required resources

AT&T, Nokia
3

GREEN

SO Only

Testing confirmed by SO Team

Y


GREEN

Y

GREEN


Modularity

SO, SDC, VFC, APPC, SDNC

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



3

GREEN

ETSI Alignment

SOOL003 plug-in to SO

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


Y

GREEN

Y

ETSI Alignment

SO plugin to support SOL003 to connect to an external VNFM

SO, SDC, AAI,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




4

RED

Architecture did not approve

N



OSAM/PNF??????






4

RED

N



TOSCA Task Force???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 integrationIntel

4

RED

N



Alloted Network Function??????






 3

GREEN

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

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

Y

GREEN

Y

GREEN


Phase 1 - VSP Compliance Check

 SDC

CLI/VNFSDK

 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
PriorityM1 Scorecard

TSC M1

Approval

M3 ScorecardM3 TSC ApprovalM4 ScorecardTSC M4 ApprovalNon Functional RequirementOwnerProject ImpactedLink(s) to HLD/LLD if anyDependency (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 projectsIf Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Company EngagementNotes
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


Improve our E2E Process Automation

SO
SDC
CCSDK
OOM
Testsuite
Documentation

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


AT&T
Bell Canada
Ericsson
Huawei
IBM
Orange
Tech Mahindra


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


S3P - Footprint Optimization (Integration with Alpine)

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

OOM + ALL

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

Orange

OAM

Amdocs

+ PTL


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

 



OOM + ALL

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

Orange

OAM

Amdocs

+ PTL

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

GREEN

Code OK for Mariadb-galera cluster and Cassandra cluster

Integration to be done with A&AI



OOM + ALL

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

Amdocs
1

GREEN

Manual PH1

Yes with limited scope: Manual PH1



GREEN

Healthcheck gate is operational

Y

CI/CD

OOM + Integration

(Infrastructure)


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:



Amdocs

Orange

Linux Foundation

Bell

Huawei


1

GREEN

Yes

GREEN

Y

Document as You CodeALLTracked in JIRA - Label: Documentation






1

GREEN

Security Checklists integrated to the Release Milestone templates

Yes


GREEN

Y

Security by DesignSecurity SubcommitteeALL

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








1

RED

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





Modeling M3 Checklist enhancementModeling SubcommitteeSO, SDC, VFC, APPC, VNFSDKProposed M3 Checklist modeling updates discussion


VFC: Committed


1

GREEN

AAI POC performed by Dublin Release Requirements on TSC Call 2/14

Y

<FOLLOW UP>Waiting for inputs

S3P - Provide Upgrade Capabilities PH1OOM supported by A&AI, SO, SDC and SDNCDublin Release Platform Maturity





In Dublin will establish plan & basis for platform release upgrade strategy to be implemented in following release.
1

GREEN

Y

GREEN

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

Y

Move Helm Chart (OOM) at project levelOOM + ALL



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



1

GREEN

Y

GREEN

Y

oParent Integration to fix vulnerabilities

Security Subcommittee

Yang Xu

Integration +ALL


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




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

Additional functional tests delivered per project on OOM


Infrastructure capacity





2Yes

GREEN

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

Y

S3P- Geo-Redundancy

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

Platform Maturity Resiliency Requirements






2


GREEN

Yes

GREEN

Y

SOL 004 (VNF Package Security)Samuli KuuselaSDC, VNFSDK

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.

In Dublin will implement the 5G Use Case scope as minimum. Possible left overs in El Alto.
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



xNF communication security enhancements.

DCAE

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. 


NokiaController part is covered under the 5G Use Case. It is not covered under this item.
4

RED

No



S3P - Service Mesh (ISTIO)Security & Architecture SubcommitteesALL except MSB or performed at K8S level (OOM); Poc of ISTIO plug-in to AAF not resourcedhttps://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2






4

RED

No



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


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



Amdocs

AT&T

Bell

Hauwei

Intel



3

GREEN

No particular Integration Testing required.

Portal/UUI Teams will provide the testing resources

Y

GREEN

Implementation complete - test phase

Waiting for inputs

Locale/Internationalization language supportPortal, UsecaseUIInternationalization language supportPortal, UsecaseUIL

Code:
PORTAL, UsecaseUI

UsecaseUI (C)


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

Angular 6 Upgrade of ONAP Portal and SDKPortal

PORTAL-330 - Getting issue details... STATUS

PortalXL

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)

TypeRequirementOwnerProject ImpactedLink(s) to HLD/LLD if anyDependency (from/to) another project(s)T-Shirt Size (XS, S, M, L, XL) (star)Project's Impact: Test Only (TO), Code (C)Company EngagementNotesM4 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

Functional RequirementFine-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-ProjectDataLakeDCAE



China Mobile, Huawei, ZTE, VMware

Sub-ProjectComposable Disaggregrated Infrastructure (CDI)@Alex VulMulti-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 RequirementMulti-Architecture SupportComponents used by vFW

-Healthcheck

-vFW




ARM

Functional RequirementETSI 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








(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.
  • No labels