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 Istanbul release contains a number of enhancements primarily centered around 5G use cases and ORAN integration.

We are continuing work on OpenDaylight Decoupling in Istanbul by refactoring our installation packages to allow us to deploy the same CCSDK artifacts unaltered on different OpenDaylight releases, with only a separate release-specific installation bundle for Karaf feature dependency declarations (karaf "feature.xml" files).

The Istanbul release also includes a major release upgrade in OpenDaylight to the OpenDaylight Silicon release.

As a proof of concept of OpenDaylight Decoupling, we plan to install the same CCSDK maven artifacts in OpenDaylight Phosphorus (the release after Silicon), only varying the Karaf feature declarations to match Phosphorus versions.

Requirements

The following table lists the new functional requirements CCSDK is committing to support for the Istanbul Release:

Minimum Viable Product

The following epics represent the minimum viable product of the CCSDK Istanbul Release:

The following epics are also in scope for Istanbul, but are not considered of the minimum viable product.  In the event of unanticipated resource constraints, these could be reduced in scope or deferred without impacting any functionality deemed by the TSC as critical for Istanbul.

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

The following epics are committed for the CCSDK Istanbul Release:

The following epics are also in scope for Istanbul, but are not considered of the minimum viable product.  In the event of unanticipated resource constraints, these could be reduced in scope or deferred without impacting any functionality deemed by the TSC as critical for Istanbul.

Stories

Bugs

Longer term roadmap

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

Release Deliverables

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

Sub-Components

Please see the INFO.yaml files associated with each repo as the authoritative sources of information - https://gerrit.onap.org/r/admin/repos/q/filter:ccsdk

Architecture

High level architecture diagram

CCSDK is delivered as a set of libraries accessible as Maven dependencies, as well as a set of base Docker containers. The docker containers themselves are intended to be used by other projects as a basis for their own controller-specific docker containers.

The following diagram illustrates how CCSDK is used by the controller projects:

Open

Platform Maturity

Please fill out the centralized wiki page: Istanbul Release Platform Maturity

API Incoming Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

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.

N/A - CCSDK does not have direct interfaces of its own. It is tested as part of its client (SDNC)

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.

None

Known Defects and Issues

Please refer to "Bugs" section above

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

Please update any risk on the centralized wiki page - Istanbul Risks

Resources

Please see the INFO.yaml files associated with each repo as the authoritative sources of information - https://gerrit.onap.org/r/admin/repos/q/filter:ccsdk

Release Milestone

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

Team Internal Milestone

Documentation, Training

Please update the following centralized wiki: Istanbul Documentation

That includes

• Team contributions to the specific document related to he project (Config guide, installation guide...).

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