Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tableenhancer
numberOfFixedRows1
numberOfFixedColumns4
decimalMark. (point)


Functional RequirementOwnerProject ImpactedPriorityM1 ScorecardTSC M1 ApprovalM3 ScorecardM3 TSC ApprovalM4 ScorecardTSC M4 ApprovalLink(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
Consistent ID of a Cloud Region (Dublin)SDNC & APPC , VID, SO, UUI, VFC, OOF2

Status
colourGreen

YY

Status
colourYellow

OOF does not realize this requirement

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-Cloud2

Status
colourGreen

Y

Status
colourGreen

M3 Gate (Dublin HPA)


Y

Status
colourYellow

Pending code review and integration

Green

Coding is done. Testing now. Finding some issues in Policy related CLI commands. Debugging now.<please provide gerrits awaiting review>


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 & Policy2

Status
colourGreen

Y

Status
colourGreen

M3 Gate (Dublin Scaling)

Y

Status
colourGreen
titleGreen

YScaling Use Case (Dublin)

DCAE: TO

CLAMP: Committed (Based on TechM resource commitment)

Policy: Committed (Based on TechM Resource Commitment)




K8S based Cloud Region SupportMulti-Cloud, AAI, SDC, SO0

Status
colourGreen

Y

Y

Status
colourGreen
titleGreen

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

YK8S 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
Change Management Dublin Extensions - Flexible designer/orchestratorSO, VID2

Status
colourGreen

SO (AT&T) and VID

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

Y

Status
colourGreen

Y

Status
colourGreen

VID and SO functionality completed

YChange 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

Status
colourGreen

Testing confirmed by Orange and AT&T

YY

Status
colourGreen

OOF functionality completed and last change to be merged;

The portion of code in APPC has been merged.

<if feature not complete already - move to OUTPLAN>

YChange Management Dublin Extensions

APPC (C),

OOF (C),

A&AI (TO)

APPC: Committed (Orange)

OOF: Committed (Orange)


Orange


Change Management Dublin Extensions - Schedule OptimizationOOF2

Status
colourGreen

Testing confirmed by AT&T

Y

Status
colourGreen

New CMSO APIs in Dublin

Y

Status
colourGreen

Feature completed; working on code coverage

YChange Management Dublin Extensions

OOF (C),

Policy (TO)

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

Status
colourGreen

Testing confirmed by AT&T

Y

Y

Status
colourGreen
titleGreen

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

Status
colourGreen

SO Only

Testing confirmed by SO Team

Y


Status
colourGreen

Y

Status
colourGreen

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

Status
colourGreen

ETSI Alignment

SOOL003 plug-in to SO

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


Y

Status
colourGreen

Y

Status
colourGreen
titleGreen

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

Yhttps://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

Status
colourRed

Architecture did not approve

N



???






TOSCA Task Force???4

Status
colourRed

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 integrationIntel

Alloted Network Function???4

Status
colourRed

N



???






Phase 1 - VSP Compliance Check

 SDC

CLI/VNFSDK

 3

Status
colourGreen

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

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

Y

Status
colourGreen

Y

Status
colourGreen

Y VSP Compliance Check within SDC (Dublin)


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

Vodafone, iconectiv, huawei




...