Skip to end of metadata
Go to start of metadata

DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

Info

Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. Use the Wiki to document the release plan. Don't provide PowerPoint. Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.

Overview

Project NameEnter the name of the project
Target Release NameDublin Release
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company (Alphabetical Order)Amdocs, AT&T, Bell Canada, China Mobile, Ericsson, Huawei, Intel, Nokia, Orange, Tech Mahindra, VDF, ZTE

Scope

What is this release trying to address?


The Dublin Release will be focusing on the following areas:

  • Platform Maturity (i.e., S3P items)
    • Resiliency
      • Level 2 - regression from Beijing, plug close gap on DB resiliency.
      • DB Resiliency was a limitation in Beijing due to the Active/Standby nature of MySQL. MariaDB w/Galera provides an active-active clustered configuration, which will support local fail-over.
    • Scalability
      • Level 1 will be a regression run on Dublin release - anticipate this to be test only
    • Stability
      • Level 1 will be a regression run on Dublin release - anticipate this to be test only
      • Level 2 requirement is expected to be covered by the Integration team.
    • Security
      • Level 1 definition has changed in Dublin. Not clear we are achieve Level 1
      • Address outstanding items related to CII Passing Badge:
        • Clearing Critical and Medium Nexus IQ Security alerts to the extent possible
        • Addressing 2 other security related items from Passing Badge related to encryption
      • Secure DMaaP topics (Dependency on DMaaP project) - Stretch Goal
        • DMaaP indicated delivery would be Sept, plus
        • DMaaP story is still not written to enable APPC to assess impact at this stage.
  • Documentation updates for Dublin, such as, but not limited to:
    • API Guide improvements
    • Developer guide
    • Release Notes
  • Code Coverage for UI of the Monitoring Pages(Javascript) - TBD, no commitment at this stage

Use Cases and Functional Requirements

Describe the use case this release is targeted for (better if reference to customer use case).

The use cases supported in Beijing release will continue to be supported as part of regression assuming all other components do likewise.CCVPN

SO will contribute to the following use cases as part of the functional requirements.

  • VNFM SOL003 adapter support : Resources commitment from Ericsson and Nokia
  • CCVPN extension : Resources commitment from CMCC, VDF, ZTE.
  • Change Management Extension : Commitment based on support from ATT resources.(Scope TBD)
  • PNF extension  : Resource commitment from Nokia.
  • HPA extension (Hardening) for the other existing usecases : Support from Intel
  • Support Multi Cloud for cloud agnostic orchestration : Support from Intel and VMware.
  • Consistent ID of a cloud region : Support from ATT (Testing effort)
  • Internal architecture improvements and work towards modularity:
    • So Monitoring pagination
    • S3P
    • Documentation improvements
    • UT and CSIT improvements
  • BBS : Resource commitment under discussion (Nokia/Huawei/Swisscom??).
  • 5G Support : (Under discussion ATT/Intel/vmware/Ericcson/Amdocs??)
  • Removal of Manual interventions : (Under discussion Tech mahindra, ATT...??)
  • SOL005 adapter support : Resources from Verizon (under discussion of the usecsase to be used is not yet clear)

Minimum Viable Product

Same as was defined for Casablanca.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Stories

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Longer term roadmap

The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make no assumptions about the network. Support configuration and lifecyle management of VNF/VNFC in a generic fashion so that on-boarding any new VNF/VNFC is just a matter of configuration and data. Longer term items include:

  • Align to the modularity architecture proposed as part of ONAP by the architecture team.
  • Support different types of clouds, working through Multi cloud;

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.


Deliverable NameDeliverable DescriptionDeliverable Location
SO Docker ImagesExecutableDocker image available on nexus3
MariaDB Docker ImageExecutableDocker image available on nexus3
SO LibsJar filesAvailable on nexus
Deployment ScriptsChef recipes used to configure the Docker containers.

found on SO Git repositories

Sub-Components

onap/so/api-handler-infra

onap/so/bpmn-infra

onap/so/catalog-db-adapter

onap/so/openstack-adapter

onap/so/request-db-adapter

onap/so/sdc-controller

onap/so/sdnc-adapter

onap/so/so-monitoring

onap/so/vfc-adapter

ONAP Dependencies

List the API this release is expecting from other releases. Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

SDCAPIs for distribute service modelsDefined in AmsterdamDelivered in AmsterdamInterfaces Link
A&AIAPIs for inventory dataDefined in AmsterdamDelivered in AmsterdamInterfaces Link
SDN-CAPIs for network controllerDefined in AmsterdamDelivered in AmsterdamInterfaces Link
APP-CAPIs for application controllerDefined in AmsterdamDelivered in AmsterdamInterfaces Link
VF-CAPIs for Network ServiceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Multi-VIMAPIs for Multi-VIMDefined in AmsterdamDelivered in AmsterdamInterfaces Link
OOFAPIs for placement and homingDefined in BeijingDelivered in BeijingInterfaces Link
DCAEFor PNF instantiation message from DCAE over DMaapDefined in CasablancaDelivered in CasablancaInterfaces Link

API Outgoing Dependencies

API this release is delivering to other releases.

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

Create service instanceCreate a service instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Delete service instanceDelete a service instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Create vnf instanceCreate vnf instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Delete vnf instanceDelete vnf instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Create vf module instanceCreate vf module instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Delete vf module instanceDelete vf module instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Create volume group instanceCreate volume group instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Delete volume group instanceDelete volume group instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Create network instanceCreate network instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Delete network instanceDelete network instanceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Get orchestration requestsGet orchestration requestsDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Get a specific orchestration requestGet a specific orchestration requestDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Create E2E serviceCreate E2E serviceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Delete E2E serviceDelete E2E serviceDefined in AmsterdamDelivered in AmsterdamInterfaces Link
Query progress statusQuery progress statusDefined in AmsterdamDelivered in AmsterdamInterfaces Link

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Archiecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.


For details on the SO architecture, refer to the SO User Guide.


Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability

1 - project team

2 - Integration team

Integration team did a 72 hour test in Beijing

1 - project team

2 - Integration team

Assume Integration team will address Level 2 -  72 hour test in Dublin

  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency2

2

In Dublin we will address Resiliency at the DB level since that was a constrain in Beijing. this will be possible with the move to Maria DB w/Galera


  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security1

1?

Level 1 definitions in Dublin where changed.


  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability11
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability1

1

Recommendation for Dublin is Level 2; however, Level 2 requirements are unclear and cannot be committed to.


  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability1

1

For Level 2

All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines;  ?? Does this apply to Reboot?

Swagger 2.0? - dependent on what Oxygen supports

E2E tutorial ???


  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation


  • Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system. Confirm that resources have been allocated to perform such activities.

  • CSIT tests added as part of R1 will continue to be supported in R3
  • Pairwise testing will be done in the WindRiver Dev lab similar to what was done in R3.
  • Epics are created to track testing activities to address Platform Maturity items.
  • Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release. List identified release gaps (if any), and its impact.

Gaps identifiedImpact
To fill outTo fill out
  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

  • Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Risk identifiedMitigation PlanContingency Plan
Resource commitment for certain requirements is not yet clear.To check and get details for the sepcific requirementsRemove the requirements from the scope of Dublin






  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

  • Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

DateProjectDeliverable
To fill outTo fill outTo fill out
  • Documentation, Training

  • Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  • Highlight the team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

Note

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.


Documentation updates planned for Beijing release are tracked under Documentation Epic: SO-675

Other Information

  • Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

  • Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible. List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ). In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.


Charter Compliance

The project team comply with the ONAP Charter.




  • No labels

2 Comments

  1. Hi,

    I am trying to connect to the SO mariaDB in a cluster but the pod when deployed is marked as completed (not running). Is there a new consolidated DB for SDNC/SO MariaDB-galera delivered?

    The pod i see is:

    dev-mariadb-galera-mariadb-galera-0


    Thanks



  2. Hi ,

    I am trying to setup service orchestration with docker by referring the below and the container not getting started.

    https://docs.onap.org/en/dublin/submodules/so.git/docs/developer_info/Building_SO.html#build-docker-images

    Thanks 

    Maheswari R