...

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project=sanbox CCSDK and issuetype in (story) and fixVersion = "Frankfurt Release"
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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

Deliverable Name	Deliverable Description

To fill outTo fill out

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

...

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

Sub-Components

Subcomponents of each ONAP project may be found on the Resources and Repositories page on this wiki. Please see the CCSDK section of that page for subcomponent list of CCSDK.

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 Architecture 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.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:

Image Added

Platform Maturity

Please fill out the centralized wiki page: Frankfurt Release Platform Maturity v1

API Incoming Dependencies

...

API

...

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API

Name	API Description	API Definition Date	API Delivery date	API Definition link (i.e.swagger)

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

API Outgoing Dependencies

...


A&AI : schemas	A&AI schemas used by CCSDK aaa-service module	Defined in seed code	Included in seed code	TBD
SDC : distribution client	API used by ueb-listener (in CCSDK sdnc-northbound repo) to receive artifacts from SDC	Defined in seed code	Included in seed code	TBD

API Outgoing Dependencies

API Name	API Description	API Definition Date	API Delivery date	API Definition link (i.e.swagger)

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

Third Party Products Dependencies

...

Maven libraries	Libraries used as dependencies by SDN-C, APP-C, DCAE and OOM	Included in seed code	Delivered in seed code	Javadoc will be provided
Docker containers	Base docker containers will be provided which can be used by SDN-C and APP-C as a basis for their docker containers	Included in seed code	Delivered in seed code

Third Party Products Dependencies

Name	Description	Version

To fill outTo fill outTo fill out

In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.

OpenDaylight

OpenDaylight SDN Controller Platform

Neon SR1

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.

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.

Gaps identified	Impact
To fill out	To fill out

Known Defects and Issues

Please refer to Frankfurt Defect Status

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 - Frankfurt Risks

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.

...

Milestone Description Date Comments
M2/M3 Functionality Freeze / API Freeze

Stable user stories baselined
Feb 15, 2019

M2 worksheets ready for review
Feb 19, 2019 Release manager reviews worksheets to assess readiness for M2 milestone

TSC M2 approval vote
Feb 21, 2019

M3 API Freeze

Final API definitions (swagger, Yang) due
March 8, 2019 Last day to submit Dublin swagger / Yang changes to Gerrit

M3 worksheets ready for review
March 12, 2019 Release manager reviews worksheets to assess readiness for M3 milestone

TSC M3 approval vote
March 14, 2019

M4 Code Freeze

Code due for Dublin user stories
March 29, 2019 Last day to submit Dublin code changes to Gerrit

M4 worksheets ready for review
April 2, 2019
Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:
All repos must have >= 50% code (line) coverage in Sonar
No failed Jenkins jobs
All CSIT tests pass
Healthchecks pass

TSC M4 approval vote
April 4, 2019

RC0 Release Candidate 0

Code due for RC0 fixes
April 19, 2019 Last date to submit code fixes for release candidate 0

RC0 release artifacts available
April 23, 2019

RC0 worksheets ready for review
April 23, 2019

TSC RC0 approval vote
April 25, 2019

RC1 Release Candidate 1

Code due for RC1 fixes
May 3, 2019 Last date to submit code fixes for release candidate 1

RC1 release artifacts available
May 7, 2019

RC1 worksheets ready for review
May 7, 2019

TSC RC1
May 9, 2019

RC2 Release Candidate 2

Code due for final Dublin fixes
May 17, 2019 Last date to submit code fixes for final Dublin release (RC2)

RC2 release artifacts available
May 21, 2019

RC2 worksheets ready for review
May 21, 2019

TSC RC2
May 23, 2019

Release Sign-Off Final TSC Sign-Off May 30, 2019 Dublin Release Sign-Off

Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

...

Versions Compared

Old Version 5

New Version 6

Key

Sub-Components

Sub-Components

Architecture

High level architecture diagram

Platform Maturity

API Incoming Dependencies

API Outgoing Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Known Defects and Issues

Risks

Resources

Release Milestone

Team Internal Milestone

Documentation, Training

Milestone	Description	Date	Comments
M2/M3	Functionality Freeze / API Freeze
	Stable user stories baselined	Feb 15, 2019
	M2 worksheets ready for review	Feb 19, 2019	Release manager reviews worksheets to assess readiness for M2 milestone
	TSC M2 approval vote	Feb 21, 2019
M3	API Freeze
	Final API definitions (swagger, Yang) due	March 8, 2019	Last day to submit Dublin swagger / Yang changes to Gerrit
	M3 worksheets ready for review	March 12, 2019	Release manager reviews worksheets to assess readiness for M3 milestone
	TSC M3 approval vote	March 14, 2019
M4	Code Freeze
	Code due for Dublin user stories	March 29, 2019	Last day to submit Dublin code changes to Gerrit
	M4 worksheets ready for review	April 2, 2019	Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks: All repos must have >= 50% code (line) coverage in Sonar No failed Jenkins jobs All CSIT tests pass Healthchecks pass
	TSC M4 approval vote	April 4, 2019
RC0	Release Candidate 0
	Code due for RC0 fixes	April 19, 2019	Last date to submit code fixes for release candidate 0
	RC0 release artifacts available	April 23, 2019
	RC0 worksheets ready for review	April 23, 2019
	TSC RC0 approval vote	April 25, 2019
RC1	Release Candidate 1
	Code due for RC1 fixes	May 3, 2019	Last date to submit code fixes for release candidate 1
	RC1 release artifacts available	May 7, 2019
	RC1 worksheets ready for review	May 7, 2019
	TSC RC1	May 9, 2019
RC2	Release Candidate 2
	Code due for final Dublin fixes	May 17, 2019	Last date to submit code fixes for final Dublin release (RC2)
	RC2 release artifacts available	May 21, 2019
	RC2 worksheets ready for review	May 21, 2019
	TSC RC2	May 23, 2019
Release Sign-Off	Final TSC Sign-Off	May 30, 2019	Dublin Release Sign-Off

Page Comparison

Versions Compared

Old Version 5

New Version 6

Key

Sub-Components

Sub-Components

Architecture

High level architecture diagram

Platform Maturity

API Incoming Dependencies

API Outgoing Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Known Defects and Issues

Risks

Resources

Release Milestone

Team Internal Milestone

Documentation, Training