Versions Compared

Old Version 146

changes.mady.by.user Cecilia Corbi

Saved on

compared with

New Version 147

changes.mady.by.user Michael O'Brien

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add logging deployment streaming plan diagram
  1.  – is the last day for Service Providers to include their requirements into this page
  2.   – is the last day for providing use case/functional requirements as a candidates for Dublin
  3.    - 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
  4. Vf2f in December – making a decision of what is indeed included in Dublin, based on Service providers priorities and projects’ commitments

...

REQDublin Requirement, along with link for details or descriptionService 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

  • vFW as use case (with firewall as container, sink and generators as VMs)
  • EdgeXFoundry use case

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

2Continue 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?)

3Start 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
4Implementation of “ONAP managing 5G as transport for CCVPN”  usecase

Verizon

Deutsche Telekom - P2

Vodafone - P1



Use case (CCVPN) extension, no details available
5Change Management extension including 5G requirements

Orange - P1

AT&T - P1

Vodafone - P2


Ajay Mahimkar

Lukasz Rajewski to be confirmed

Functional requirement (Change Management) extension
6True 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 DebeauModelling enhancement (SDC, SO, AAI)
8Tooling 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
9Provide 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

  • CIA Project - reducing image sizes
  • OOM -
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-1175
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
- Description of the LCM model
- Monitoring of the state
- Requirements towards VNF providers

Deutsche Telekom - P1

Vodafone - P1


Michael O'Brien - for Logging

Architecture enhancement (Controller (SDNC, APPC, VF-C), SO, Modelling, Log (Pomba?))

VNFRQTS

Logging Dublin Scope

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-707

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-876

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

17Classification 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
18PNF 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

19The 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)

Logging Dublin Scope

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-707

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-877

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-487

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1110

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-178

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-376

See deployment diagram for streaming compliance plan

Image Added


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
21Some 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 -

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1175
, Mike Elliott)

22Onap'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

23Ability 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
25Multi-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.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-346

Note: Project teams can build on platform capabilities to provide application level geo support.

26PNDA 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)
27ONAP 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 -

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1193


28Enhanced ONAP CI (description is under Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals)

Bell Canada - P1

Deutsche Telekom - P1

Vodafone - P3 

Telecom Italia



S3P
29Use 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)
30VNF 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

31OSAM

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"

Edge Automation Functional Requirements for Dublin

More information here:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-280

China Mobile - P1

Vodafone - P3

Edge Automation Functional Requirements for Dublin


Srinivasa Addepalli (Temporary)

Functional requirements: Edge Automation WG – Ramki Krishnan, Raghu Ranganathan

Projects: DCAE, CLAMP, A&AI (TBD), Multi-VIM/Cloud (TBD)

33

BroadBand Service requirements:
- support for nomadic PNF (discovery, re-registration),
- service change order using External API,
- E2E service reconfiguration,
- consider scalability of ONAP components to support provisioning and assurance of high number of customer facing service instances (AAI, SO...)

BBS Broadband Service Use Case (Dublin)


Swisscom - P1

Vodafone - P3

Telecom Italia


David Perez Caparros

Chaker Al-Hakim

Use case


345G requirement: 5G middle/backhaul modeling and orchestration

China Telecom - P1

China Mobile - P2

Vodafone - P2 

Telecom Italia



Use case - details are needed
35

Consistent ID of a Cloud Region (Dublin)

AT&T - P1


Bin Yang

Functional requirement

SO,VID,SDNC,OOF, UUI,VFC

 36

Evolve OOM to support Multi-site deployments of ONAP and meet Operator requirements

(Likely aligns/overlaps with requirement #25 above)

AT&T - P2

Vodafone - P2 


Mike Elliott

 Project (OOM and (likely) all components it deploys)

Please see OOM comments added to #25

 37

 Continue progress on S3P levels across components

  • Complete unfinished Casablanca S3P requirements by component
    • For example: CADI/AAF integration, support for HTTPS/encrypted communications, Adherence to ONAP Logging Spec
  • Measured progress on CII badging level and unit test coverage percentages
AT&T - P2

China Mobile - P3

Vodafone - P3 


Michael O'Brien (Logging)

S3P Most (all?) components depending on current S3P levels achieved

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-380

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-877

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-876

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-376

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-494

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-707

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-178

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-487



 38 The End-End use cases that define the functionality of ONAP releases, and are tested by Integration test should include validation of the example VNFs used by ONAP (e.g. vFW)   using the test scripts for HEAT templates (from VVP project) or TOSCA ( from VNFSDK project)

AT&T - P3

Vodafone - P3 

run validation tests on the VNFs used by ONAP during integration test - TOSCA packaged VNFS using VNFSDK validation scripts and HEAT VNFS using VVP

Steven wright

Integration project

VNFSDK @ victor gao

VVP @ Steven wright @ Trevor Lovett

INT @ Helen Chen

applies to ALL uses cases tested by ONAP

ALL ONAP VNFS should have their conformance to VNFRQTS documented in ReadTheDocs for the Release. This should include links to the VNF Packages used for onboarding. 

 39 Using "Cloud Services Architecture" constructs in building service level APIs Verizon


40

Continuation of HPA (Mostly Hardening - Add new e2e test cases, automate the integration steps for continuous testing). Automation for various use cases (vFW, vDNS with different HEAT templates, vCPE with different TOSCA templates)

Exceptions:

  • Bring ONAP and Openstack based based cloud regions manually.
  • Register cloud regions via ESR in ONAP.

Automation scripts to do following:

  • Create CSAR from demo repository.
  • Onboard CSAR in SDC using SDC API
  • Prepopulate SDNC items
  • Upload HPA policies using POLICY FW API
  • Instantiate service and VNF using SO API
  • Check that VNF workloads are instantiated with right cloud region and flavor.
  • Check that VNFs are working.
  • Bring down the VNF
  • Start next automated test

Even though this work is as part of HPA, we hope that this work helps in stabilization of code, checking for any regression on continuous basis.




Alex Vul
41VSP Compliance Check within SDCVodafone
abdel.rabiVSP Compliance Check within SDC (Dublin)

...