DRAFT PROPOSAL FOR COMMENTS

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

Overview

Scope

What is this release trying to address?

The Casablanca 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 Casablanca release - anticipate this to be test only
  • 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
    
    • Level 1 definition has changed in Casablanca. 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, not currently committed for Casablanca
      
      • DMaaP indicated delivery would be Sept, plus
      • DMaaP story is still not written to enable APPC to assess impact at this stage.
        

• Support new LCM action Reboot and various other enhancements to existing LCM actions (Tracked under Epic: APPC-899)
• Documentation updates for Casablanca, such as, but not limited to:
  
  • LCM API Guide
  • Release Notes
• Code Coverage for CDT (Javascript) - TBD, no commitment at this stage
  
• Use Cases
  • ConfigScaleOut - Partially supported
    
    • Support Retrieval of configuration data from AAI instead of having SO pass configuration data in payload - (investigate if we can we reuse the named query)
      • Dependency on SO to pass the vf-module-id of the vDNS instance that must be added.
        
    • No commitment on Controller Type since requirements are still unclear.
      
  • Change Management - Commitment based on support from ATT resources
  • 5G/PNF
    

Use Cases

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.

• Scaling Use Case - 
  
  • SO will support retrieving the data to be configured from AAI. This however has a dependency on SO to  pass the vf-module-id of the vDNS that was instantiated..
  • Discussions around how Controller Type will be handled are still too vague and unclear, so no commitment can be made to support this. APPC will continue to support APPC and SDNC via the Client Library as was done in Beijing.
• CCVPN Use Case
  • Support the Cross Domain Cross Llink Virtual Private Network between 2 ONAP instances.
• HPA extension for the other existing usecases
• PNF resources orchestration 
  
  

Minimum Viable Product

Same as was defined for Beijing with the adding of CDT.

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

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 controller architecture proposed as part of ONAP by the architecture team.
• Work with SDNC team to converge on a single controller design tool
• Support different types of clouds, currently only support Openstack;

Release Deliverables

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

Sub-Components

NA

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

API this release is delivering to other releases.

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.

• 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.

• Known Defects and Issues

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

• 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).

• 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
  • ...

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.