...

Scope

What is this release trying to address?

...

The Casablanca Release will be focusing on the following areas:

• Upgrade of ODL to Oxygen (CCSDK dependency)
• Upgrade to Karaf 4
• Migrate DB to use Maria DB with Galera (CCSDK dependency)
• Platform Maturity (i.e., S3P items)
  • Resiliency
    • Address DB Resiliency, which 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.
  • Security
    
    • Address outstanding items related to CII Passing Badge, which includes:
      • Clearing all Critical and Medium Nexus IQ Security alerts
      • Addressing 2 other security related items from Passing Badge
  • 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.
  • Scalability
    • Level 1 will be a regression run on Casablanca release - anticipate this to be test only

• Support new LCM action Reboot and various other enhancements to existing LCM actions (Tracked under Epic: APPC-899)
• Documentation updates for Beijing
• Code Coverage for CDT TBD

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.

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

• Scaling Use Case - 
  
  • APPC will support retrieving the data to be configured from AAI. This however has a dependency on SO to provide the vnf_Id of the vDNS that was instantiated..
  • Discussions around how Controller Type will be handled are still to 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.

Minimum Viable Product

Describe the MVP for this releaseSame 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.

...

...

Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

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 authentication of APIs
• 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

For the Casablanca release, APPC has dependencies on the following three projects for specific deliverables:

• CCSDK - - Oxygen ODL & MariaDB plus Galera
• SO - for scale out scenario to deliver the correct data to retrieve AAI information

Architecture

High level architecture diagram

...

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.

Image Added

Platform Maturity

...

...

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.

...

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

...

The project team comply with the ONAP Charter.