SP priorities for Dublin
- Alla.Goldner
- Michael O'Brien
- Cecilia Corbi
Nov 1, 2018 – is the last day for Service Providers to include their requirements into this page
Nov 15, 2018 – is the last day for providing use case/functional requirements as a candidates for Dublin
Nov 29, 2018 - is the last day for getting all of the requirements (architecture, security, projects, S3P etc.) and getting a single consolidated list so all of the projects have full picture of what is required from them. By this date, all use cases/functional requirements need to be discussed with a different projects, and demanded scope of development should be clear to the projects
Vf2f in December – making a decision of what is indeed included in Dublin, based on Service providers priorities and projects’ commitments
REQ | Dublin Requirement, along with link for details or description | Service Provider Requesting (incl. SP name and requirement priority e.g. p1, p2, p3) | How to test (existing or new use case) | Owner (person) | Owner (project(s), S3P, functional requirement/use case) |
|---|---|---|---|---|---|
1 | K8S based Cloud-region support
| Verizon: P1 Vodafone - P3 | vFW use case (existing but with Helm charts) EdgeXFoundry use case (new use case) | @Victor Morales | Impacted projects: Multi-Cloud, SDC, SO, VNFSDK,VNFRQTS ( Containerized VNF Onboarding, Helm Charts)(?) functional requirement |
2 | Continue SOL 003 Alignment work in VF-C - Aligned with VF-C PTL. Content will be finalized as part of Dublin planning | Verizon Deutsche Telekom - P3 China Mobile - P2 Vodafone - P1 Telecom Italia - P2 | Project (VFC) development, VNFRQTS (VNF Life Cycle Operations?) | ||
3 | Start SOL 005 Alignment work ( with basic interfaces ) between SO & VF-C - Had handshake with SO and VF-C PTLs. Content will be finalized as part of Dublin planning | Verizon Deutsche Telekom - P3 China Mobile - P2 Vodafone - P2 Telecom Italia - P2 | Projects (VFC, SO) development | ||
4 | Implementation of “ONAP managing 5G as transport for CCVPN” usecase | Verizon Deutsche Telekom - P2 Vodafone - P1 | Use case (CCVPN) extension, no details available | ||
5 | Change Management extension including 5G requirements | Orange - P1 AT&T - P1 Vodafone - P2 | @Ajay Mahimkar @Lukasz Rajewski to be confirmed | Functional requirement (Change Management) extension | |
6 | True orchestration. We still need too many manual tasks to deploy a service (preload, various requests to deploy a service...) | Orange - P1 Verizon - P1 Deutsche Telekom - P1 Swisscom - P1 Bell Canada - P0 Vodafone - P1 Telecom Italia - P1 | @Alexis de Talhouët @Eric Debeau | Architecture enhancement (SO, SDNC, CDS) | |
7 | Service modeling extension. Need to define service parameter and their link with VNF or network parameter. Need to define parameters that can be modified by end-user | Orange - P2 Vodafone - P2 | @Eric Debeau | Modelling enhancement (SDC, SO, AAI) | |
8 | Tooling to operate ONAP: provide set of tools to configure ONAP via GUI (eg users, roles...), to restore the set of database... | Orange - P2 Verizon - P1 Deutsche Telekom - P3 Vodafone - P3 Telecom Italia - P3 | Project (OOM) development | ||
9 | Provide accurate documentation for operational teams, for newcomers | Orange - P0 Verizon - P0 Deutsche Telekom - P1 China Mobile - P1 Swisscom - P1 Vodafone - P0 Telecom Italia - P1 | Documentation, all projects | ||
10 | External API extension to include service modification | Orange - P2 Verizon - P3 Deutsche Telekom - P3 China Mobile - P3 Swisscom - P1 Vodafone - P2 Telecom Italia - P2 | BBS use case (proposal) | @Matthieu Geerebaert | Project (External API) development |
11 | No more hard coded components for the use-cases. ONAP is a platform to run various use-cases (similar to requirement #6 and #24) | Orange - P2 Verizon - P1 Deutsche Telekom - P1 Swisscom - P1 Vodafone - P1 Telecom italia | Architecture enhancement | ||
12 | Footprint optimization: reduce image size, avoid image duplications, reduce memory requirements. | Orange - P1 Verizon- P1 Deutsche Telekom - P2 Swisscom - P3 Vodafone - P3 | @Mike Elliott @Adolfo Perez-Duran @Sylvain Desbureaux To be confirmed | Projects (OOM + All projects) enhancements
| |
13 | Stability first. Code must be more robust, more secure. Integration must focus on code stability and not on use-cases verification | Orange - P0 Verizon - P0 Deutsche Telekom - P0 Swisscom - P0 Vodafone - P0 Telecom Italia - P1 | S3P (Integration + All projects) | ||
14 | 5G requirements (cf ORAN) PNF discovery Support of parameters/algorithm/model configurations | Orange - P1 Deutsche Telekom - P2 AT&T - P2 Vodafone - P3 Telecom Italia - P1 | Use case 5G (SDC, AAI, APPC, etc.) VNFRQTS ( covering PNFs) | ||
15 | Core Service/VNF LCM state and transition model | Deutsche Telekom - P1 Vodafone - P1 | @Michael O'Brien - for Logging | Architecture enhancement (Controller (SDNC, APPC, VF-C), SO, Modelling, Log (Pomba?)) VNFRQTS | |
16 | Focus on Platform Automation Usecases (e.g. Scale In-Out, Upgrade of VNFs) to show the E2E Management capabilities of ONAP (addition to lines 6, 11) (similar to requirement #6 , #24 , #11) | Deutsche Telekom - P1 AT&T - P1 (Assuming it overlaps with Req# 5 & 30) Vodafone - P1 Telecom Italia | Use cases (platform capabilities) VNFRQTS | ||
17 | Classification of core dependencies between e.g. Service/VNF components to support root cause analysis and alignment of change procedures (LCM) | Deutsche Telekom - P2 Vodafone - P2 | Modelling enhancement | ||
18 | PNF Modelling and Lifecycle Management to support the well defined exposure of the service endpoints (e.g. support for Edge/OSAM usecases) | Deutsche Telekom - P2 Swisscom - P1 AT&T - P1 Turk Telekom - P1 Vodafone - P3 Telecom Italia - P1 | Use case 5G (PNF support (Modelling, SDC) VNFRQTS | ||
19 | The logs of SO, SDC, SDNC, DCAE, and AAI need to be optimized. The log location of error is not particularly clear | China Telecom - P1 Deutsche Telekom - P3 Vodafone - P3 | @Michael O'Brien | S3P and projects (SO, SDC, SDNC, DCAE, and AAI) LOG-707: Logging El-Alto (moved from) Dublin ScopeClosed LOG-487: LOG Pipeline Integrity: Docker to Filebeat to Logstash to ElasticSearch to KibanaClosed SO-1110: Re-add Filebeat sidecars to SO after 2-9 container refactorClosed LOG-178: Log Specification Alignment - each onap componentClosed See deployment diagram for streaming compliance plan  | |
20 | Tomcat, mongodb, zookeeper, it is recommended that each docker use a unified version | China Telecom - P1 Deutsche Telekom - P2 China Mobile - P3 Vodafone - P3 | S3P and projects | ||
21 | Some dockers use mysql in onap, some use mariadb, different dockers use the same database version is also inconsistent, resulting in very confusing, it is recommended to have a unified version and software. | China Telecom - P1 Deutsche Telekom - P2 China Mobile - P3 Vodafone - P3 | S3P and projects (SDNC,APP-C,PORTAL,VID,NBI,CLAMP,Policy,SO OOM - OOM-1175: Shared Database InstancesClosed, @Mike Elliott) | ||
22 | Onap's heat and oom mode deployments require openstack support, so how onap handles and breaks some of the limitations of openstack, such as the limit of 100 stacks. | China Telecom - P1 Deutsche Telekom - P3 Vodafone - P3 | See @Roger Maitland and @Eric Debeau comments below OOM ?S3P | ||
23 | Ability to model running instance of VNF / NS and associate it as part of NS Design (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals) | Verizon Deutsche Telekom - P3 China Mobile - P1 Vodafone - P1 Telecom Italia - P1 | Modelling enhancement | ||
24 | Enable Self-Service use of ONAP (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals) (similar to requirement #6 and #11) | Bell Canada - P1 Deutsche Telekom - P2 Vodafone - P2 Telecom Italia - P2 | Architecture enhancement | ||
25 | Multi-site / Geo-redundancy (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals) | Bell Canada - P1 Deutsche Telekom - P2 Vodafone - P2 | @Mike Elliott | S3P and Architecture enhancement OOM providing additional geo-diversity platform capabilities. OOM-346: Platform Resiliency (Recoverability, High-Availability, Geo-Diversity)Closed Note: Project teams can build on platform capabilities to provide application level geo support. | |
26 | PNDA integration (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals) | Bell Canada - P1 Deutsche Telekom - P1 China Mobile - P1 Vodafone - P2 | Project (DCAE, CLAMP) | ||
27 | ONAP Databases as a service (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals) | Bell Canada - P1 Deutsche Telekom - P2 China Mobile - P3 Vodafone - P3 | @Mike Elliott | Project (OOM) Building on Casablanca deliverables to provide MariaDB Cluster as first DBaaS implementation - OOM-1193: Create Shared Instance of MariaDB-GaleraClosed | |
28 | Enhanced ONAP CI (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals) | Bell Canada - P1 Deutsche Telekom - P1 Vodafone - P3 Telecom Italia | S3P | ||
29 | Use of secure credentials storage for native ONAP functionality (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals) | Bell Canada - P1 Deutsche Telekom - P2 Vodafone - P2 | Project (AAI) | ||
30 | VNF scaling enhancements: Manual and Automatic Scale In | AT&T - P1 Vodafone - P1 | @Scott Blandford | Functional requirement Impact Details Here. APPC, SDC, SDNC, DCAE, OOF, Policy, SO, CLAMP, VID, VNFRQTS | |
31 | OSAM | AT&T - P1 Swisscom - P2 Turk Telekom - P1 Vodafone - P3 Telecom Italia | Use case | ||
32 | Edge Automation WG - "Analytics-as-a-service for Service Assurance" Fine Grain Placement Service (F-GPS) Edge Automation (Dublin) More information here: ONAPARC-280: Service Assurance with Big Data Analytics |