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

Compare with Current View Page History

« Previous Version 27 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: Dublin Proposed Scope_V11_Draft.xlsx

This is not yet the Dublin Release scope. Release Scope will be finalized by M1 Release Planning.

Projects intended to participate within Dublin release are posted in wiki.

New projects proposal are posted here. These projects need to be reviewed and approved by TSC.

Some of the Use Cases, Functional and non functional requirements are carried over from previous releases as they required multiple releases to be implemented.

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 

PriorityUse CaseOwnerProjects 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, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)

Company

Engagement

NotesM4 Status

1-regression

3-enhancements

vFW

Policy/(APPC)

HPA



XSAll: Test Only except Policy/(APPC)

Policy: Committed

(APPC): ?

Policy: Committed

(APPC): ?
AT&T

1vDNSIntegration TeamHPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests


1VoLTE

Integration Team

HPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests


1vCPE with or without TOSCAIntegration TeamHPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests


2CCVPN Use Case Extension (IM & Data Model, Intelligent Traffic Scheduling, Service Order & Activation)DCAE, ExternalAPI, SO, SDC, AAI, Modeling, OOFCCVPN Use Case (Dublin)







25GSDC, SO, VNFSDK, AAI, DCAE, SDNC,CCSDK, VID, AAI/ESR, VFC,APPC, DMaaP5G Use Case







0BBSDavid Perez CaparrosAAI, CLAMP, DCAE,ExternalAPI, SO, Policy, OOF, ExternalAPIBBS Broadband Service Use Case (Dublin)




Nokia, Swisscom, 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.

Functional Requirements

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







2Continuation of HPA (Dublin)Alexander VulComponents used by vFW, vDNS, vCPE, VoLTEContinuation of HPA (Dublin)







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







0K8S based Cloud Region SupportMulti-Cloud, AAI, SDC, SOK8S based Cloud Region Support




Intel, VMWare

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

MultiCloud + Demos


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







2Change Management Dublin ExtensionsAjay MahimkarSDC, SO, VID, OOF, Policy, AAI, SO, OOF, AAI, APPC/SDNCChange Management Dublin Extensions







3Model driven Control Loop Design (part of Close Loop sub-committee)SDC, DCAE, CLAMP, Policy

Ease of creating analytic components and on-boarding DCAE micro services

Model driven Control Loop Design









3Fine-Grained Placement Service (F-GPS)Multi-Cloud, OOFhttps://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2







3Modularity

SO, SDC, VFC, APPC

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







3ETSI 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







4OSAM/PNF??????







4TOSCA 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







4Alloted Network Function??????







(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

PriorityNon 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, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotesM4 Status
1Improve our E2E Process AutomationAAI, SO, SDC, APPC, VFC, CCSDK + Documentation







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







1CI/CD

Infrastructure


TSC-25 - Getting issue details... STATUS









1Document as You CodeALLTracked in JIRA - Label: Documentation







1Security 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









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







1S3P - Provide Upgrade CapabilitiesOOM + ALLDublin Release Platform Maturity







1Move Helm Chart (OOM) at project levelOOM + ALL








1oParent Integration to fix vulenaribilities

Security Subcommitee

Yang Xu

Integration +ALL








1CIST running OOMPTLsNeed to assess
Infrastructure capacity






2S3P- Geo-RedundancyOOM/MUSIC Integration to ONAP ComponentsDublin Release Platform Maturity







2SOL 004 (VNF Package Security)Samuli KuuselaSDC, VNFSDK(?)








3PNF/xNF









4S3P - Service Mesh (ISTIO)Security & Architecture SubcommittessALL 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







4S3P Manageability - Logging Capabilities??????







(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