Release Planning Template : CCSDK Amsterdam Release

Release Planning Template : CCSDK Amsterdam Release

DRAFT PROPOSAL FOR COMMENTS

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

Info

Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.


Overview

Project Name

Enter the name of the project

Project Name

Enter the name of the project

Target Release Name

Amsterdam

Project Lifecycle State

Incubation

Participating Company 

AT&T, AMDOCS, Huawei, China Mobile

Scope

What is this release trying to address?

This project provides a common set of reusable code that can be used across multiple controllers. The code could be used in other components but would not be an end solution for use cases by itself and would not be deployed on its own. 

While controllers are encouraged to use the common controller SDK libraries, usage of this common code is optional.  Our goal is to provide code that is sufficiently flexible that there is no need for controllers to implement their own custom solutions, but we recognize that there are valid reasons why specific controllers might need to implement their own solutions and would not prevent them from doing so.

The following is a list of libraries that CCSDK plans to support:

  • SDN-C core : core platform needed to execute directed graphs

  • SDN-C adaptors : set of adaptors used by directed graphs to talk to other ONAP components or external services, including other controllers

  • SDN-C northbound : northbound interfaces to SDN-C

  • SDN-C plugins : add-on functionality used by directed graphs

  • SDN-C oam : tools for operations, administration and maintenance of controller

  • Common microservice / VF lifecycle management capabilities

  • Common health checks

  • Common APIs

  • Common logging

  • Common model management (e.g. Yang, TOSCA)

  • Common resource management (e.g. IP management, DNS naming, keystore, containers)

Use Cases

The use cases supported in the Amsterdam release are:

  • Virtual Domain Name Server (vDNS)

  • Virtual Firewall (vFW)

  • Virtual Voice over LTE (vVoLTE)

  • Virtual Customer Premise Equipment (vCPE)

Minimum Viable Product

The Minimum Viable Product for Amsterdam is the set of capabilities needed to support the use cases listed above.

Functionalities

TBD

Epics

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Stories

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

 

Longer term roadmap

The intent of the CCSDK project is to provide a common set of libraries that can be used to create new types of controllers.  We anticipate that over time, the set of common functionality will grow as functionality that was originally delivered as part of a specific controller is generalized and migrated to the CCSDK project.

We also recognize that there will be times when a specific controller might need to develop its own implementation of functionality that is contained within CCSDK.  It is not the intent of this project to preclude controllers from doing so if that project sees such a need.

Release Deliverables

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

Deliverable Name

Deliverable Description

Deliverable Location

Deliverable Name

Deliverable Description

Deliverable Location

CCSDK Source Code

Source code for CCSDK project

ONAP gerrit

CCSDK Maven Artifacts

Compiled code that can be referenced in other projects as maven dependencies

ONAP Nexus

CCSDK Docker Containers

Docker containers associated with SDNC project:

  • Controller (OpenDaylight) container

  • Database container

  • Directed Graph Builder container

ONAP Nexus

Documentation

User and developer guides

ONAP Wiki

CCSDK CI/CD automation

Scripts to automate compilation and deployment of maven artifacts and docker containers

ONAP gerrit

ONAP Jenkins