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 Dublin Release will be focusing on the following areas:

• Upgrade of ODL to Fluorine SR2 (CCSDK dependency)

• Platform Maturity (i.e., S3P items)  https://lf-onap.atlassian.net/wiki/display/DW/Dublin+Release+Platform+Maturity
  
  

  •  Green color → Target level ( details see Platform Maturity below)

  • Performance:  Level 1, Level 2 (Stretch)
    
    

    • Level 1: baseline performance criteria identified and measured  (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)

    • Level 2: performance improvement plan created 

    • unzip feature.zip during building docker.

    • Remove un-used bundles from CCSDK’s odlsli - depends on CCSDK

  • Stability: Level 1 (remain test coverage 50%)
    
    

    • Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)

    • Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)

    • Configuration Enhancement https://lf-onap.atlassian.net/wiki/display/DW/APPC+Configuration+Enhancement - Stretch goal

  • Resiliency: Level 2
    
    

    • Level 2: support automated failure detection & rerouting 

      • within a single geographic site

      • stateless components: establish baseline measure of failed requests for a component failure within a site 

      • stateful components: establish baseline of data loss for a component failure within a site

    • OOM: move to variable for database’s user/password

    • CSIT OOM - Integration team

  • Security: Level 1, level 2 (Stretch)

    • Level 1: CII Passing badge

      • Including no critical and high known vulnerabilities > 60 days old

    • Level 2: CII Silver badge, plus:

      • All internal/external system communications shall be able to be encrypted: there is http internal connection between CDT and APPC, we need to find the resource to migrate from http to https.

      • All internal/external service calls shall have common role-based access control and authorization using CADI framework.

  • Scalability: Level 1
    
    

    • Level 1: supports single site horizontal scale out and scale in, independent of other component

    • APPC does not support dynamic cluster configuration in k8s only support static cluster configuration

    • Clustering env with downstream: netconf,  ansible

    • Using Alpine linux distribution docker image as base.

  • Manageability: Level1, Level 2 (Stretch)
    
    

    • Level 2:

      • A component can be independently upgraded without impacting operation interacting components

      • Component configuration to be externalized in a common fashion across ONAP projects

      • All application logging to adhere to ONAP Application Logging Specification v1.2

      • Implement guidelines for a minimal container footprint - See this presentation and follow the Container Image Minimization Guidelines

  • Usability: Level 1

    • Level 1:

      • User guide created

      • Deployment documentation

      • API documentation

      • Adherence to coding guidelines

• Documentation updates (readthedocs) for Dublin, such as, but not limited to:
  
  

  • LCM API Guide

  • Release Notes

  • CDT GUI Guide

• Code Coverage for CDT (Javascript) - TBD, no commitment at this stage
  
  

• Use Cases

  • Closed Loop / Integrate automation test
    
    

  • Change Management - APPC will continue supporting it.
    
    
    

Use Cases

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

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

• Closed Loop / Integrate automation test
  
  

• Change Management (will be done by Orange team)
  
  

Minimum Viable Product

Same as was defined for Casablanca, but with the adding of increasing better performance for starting application, geo-redundancy etc. For details, please see above on S3P section

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

List all sub-components part of this release.
Activities related to sub-components 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.

ONAP Dependencies

List the other ONAP projects you depend on.

APPC depends on the the following components as part of the general ONAP architecture:

• SDC: Rest based interface exposed by SDC. APPC receives notifications from SDC on VNF information. SDC team provides an SDC Listener, which is used by APPC. (Currently we have no use case for this, although supported)

• AAI: APPC retrieves and updates VNF data from/to AAI.

• DMaaP: Message bus for communication with other components in the solution (SDC, DCAE, MSO, Portal, OOM)

• CCSDK - APPC currently gets ODL & DB package from CCSDK; CCSDK and APPC currently must align on ODL version. 

• AAF - AAF is used for ODL API authorization

• MultiVIM - APPC can access Openstack via MultiVIM or CPD-PAL. MultiVIM is optional for APPC at this stage. Support of MultiVIM is limited to the Generic_Restart action only.

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 Dublin+Architecture.

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 APPC architecture, refer to the APPC User Guide.

Open

Platform Maturity

Refering to CII Badging Program and S3P, 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 project is expecting from other projects.
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 Outgoing Dependencies

API this project is delivering to other projects.

API Name

• Third Party Products Dependencies

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

Name

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.

• 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 the 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 Dublin release are tracked under Documentation Epic: APPC-1275: R4 - DocumentationClosed

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.