Overview

Scope

What is this release trying to address?

• Platform Maturity (i.e., S3P items)
  • Resiliency
    • Level 1 - test only based on the work from Beijing
  • Scalability
    • Level 0
  • Stability 
    
    • Level 1 will be a regression run on Casablanca release - anticipate this to be test only
    • Level 2 requirement is expected to be covered by the Integration team.
  • Security 
    
    • Required Level 1
    • reach CI bagging passing level
    • encrypted communication enable https support. sdc will work in a mixe mode http interface will continue working but internal comunication will be done using https.
    • aaf integration is a strach goal based on the a risk from portal.
  • Performance
    
    • level 0 no work required.
  • Manageability
    
    • level 1
    • align with onap logging spec 1.2
  • Usability
    • level 1
    • User guide created update
    • Deployment documentation update
    • API documentation update
    • All new API’s must adhere to the ONAP API Common Versioning 

• Documentation updates (readthedocs) for Casablanca, such as, but not limited to:
  
  • Release Notes.
  • enhance the available documentation to cover more of the application functionality and usability.
• functional requirments:
• HPA
  • SDC will support the work done to support HPA in ONAP with the help from intel. 
• Change Management
  
  • SDC will support the work being done for the change management work
  • SDC will enhance our capability in designing workflows and complete the E2E flow between SDC and so with the help from Amdocs.
• Scaling
  
  • SDC will support the work being done for the scaling work.
• 5G/PNF
  
  • the PNF support in sdc will be based on the capabilities from Beijing, no additional work is planned.
• Architecture Alignment
  
  • sdc will start creating an infrastructure to support RTC
  • start supporting the sol004 csar pckage
• HEAT support
  
  • sdc will continue to support the heat based deployment
• Testing
  
  • enhance the sdc csit test scope
  • create cd testing for the sdc sub-components workflow and dcae-ds
  • add unit test coverage for the ui and reach 10% coverage
• enhancements
  • add more functionality to the sdc generic designer support

Use Cases

SDC will support the following use cases based on the current functionality:

CCVPN(Cross Domain and Cross Layer VPN) USE CASE

OpenSource Access Manager (OSAM) Use Case

SDC will continue to support:

Use Case: vFW/vDNS (Approved)

Use Case: Residential Broadband vCPE (Approved)

Use Case: VoLTE(approved)

Use Case: VoLTE(approved)

Minimum Viable Product

SDC:

deliver all the need dockers and DB needed to support sdc functionality and the needed scripts for deploying it in HEAT heat and in OOM.

WORKFLOW:

deliver all the need dockers needed to support workflow designer functionality and the needed scripts for deploying it in HEAT heat and in OOM.

DCAE-DS:

deliver all the need dockers needed to support dcae-ds functionality and the needed scripts for deploying it in HEAT heat and in OOM.

SDC SDK's:

sdc-destribution-client

sdc-tosca

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

Stories

Longer term roadmap

SDC aims to position itself as the main design IDE in ONAP. SDC works towards creating a fully model-driven design experience.

Release Deliverables

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

Sub-Components

List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

subcomponents:

• Jtosca
• SDC Tosca
• SDC Distribution Client
• SDC base docker
  
• SDC titan cassandra
  
• SDC workflow designer 
  
• DCAE-DS

Architecture

High level architecture diagram

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.

API Incoming 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 Outgoing Dependencies 

API this release is delivering to other releases.

Third Party Products Dependencies -TBD

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

9.3.X

4.3.3

ubuntu-xfce-vnc:1.3.0

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

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.

• validate uses cases and pairwise testing of sdc with other components
• enhance the csait to include more tests

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.

Known Defects and Issues

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

Risks -TBD

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 materialize (contingency).

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.

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

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.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.