Versions Compared

Key

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

...

PriorityM1 ScorecardTSC M1 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, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotesM4 Status
2

#action - Need to confirm testing resource to Yang Xu and what they will be able to test

Bin/Yang to sync-up

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



2HPA Testing confirmed by INTEL


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

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


CLAMP: Committed (Based on TechM resource commitment)

Policy: Committed (Based on TechM Resource Commitment)





0Testing confirmed by INTEL


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, VMWare

3Need to confirm testing resource to Yang XuTesting confirmed by INTEL


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

Multi-Cloud, Demo


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


MultiVIM/Cloud: partially committed based on VMware's contribution
VMware, Intel

2
Need to confirm  to Yang Xu and what they will be able to testChange Management Dublin Extensions - Flexible designer/orchestratorSO, VIDChange Management Dublin Extensions

SO (C),

VID (C)

SO: Committed (AT&T)

VID: pending final decision from Nokia


AT&T

Nokia




2



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

Change Management Dublin Extensions - Schedule OptimizationOOFChange Management Dublin Extensions

OOF (C),

Policy (TO)

OOF: Committed (AT&T)
AT&T

3


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

Self Serve Control Loop (Closed Loop Subcommittee)  Scott BlandfordDCAE, 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

DCAE Resource constraints

Policy: Resource Constraints

SDC: Resource Contrstraints

AT&T  
3

Fine-Grained Placement Service (F-GPS)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), 



3

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


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




3

ETSI Alignment (SO plug-in)SO, SDC, AAI, External APIhttps://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 Ericcson

AAI: Not Committed

SDC: no resources

SO: SOL005 Under discussion with Verizon.

AAI: no resources




4

OSAM/PNF??????







4

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

Alloted Network Function??????







 3

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

   

...