Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following table lists the new functional requirements for the Frankfurt Release:

RequirementsCompanies Supporting Requirement

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-37

Fujitsu

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-33

AT&T

Bell Canada

Ericsson 

Huawei

Orange

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-267

IBM

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-84

Ericsson

Huawei

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-53

Huawei

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-96

Huawei

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-38

Ericsson

IBM

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-42

Tech Mahindra

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-158

Wipro

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-174

AT&T

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-182

Orange

Samsung


Minimum Viable Product

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

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=CCSDK and issuetype in (epic) and fixversion="Frankfurt Release" and priority >= priority< high
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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


Deliverable NameDeliverable DescriptionDeliverable Location
CCSDK Source CodeSource code for CCSDK projectONAP gerrit
CCSDK Maven ArtifactsCompiled code that can be referenced in other projects as maven dependenciesONAP Nexus
CCSDK Docker Containers

Docker containers associated with SDNC project:

  • Controller (OpenDaylight) container
  • Database container
  • Directed Graph Builder container
ONAP Nexus
DocumentationUser and developer guidesONAP Wiki
CCSDK CI/CD automationScripts 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.

...

API Incoming Dependencies


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
A&AI : schemasA&AI schemas used by CCSDK aaa-service moduleDefined in seed codeIncluded in seed codeTBD
SDC : distribution clientAPI used by ueb-listener (in CCSDK sdnc-northbound repo) to receive artifacts from SDCDefined in seed codeIncluded in seed codeTBD


API Outgoing Dependencies


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
Maven librariesLibraries used as dependencies by SDN-C, APP-C, DCAE and OOMIncluded in seed codeDelivered in seed codeJavadoc will be provided
Docker containersBase docker containers will be provided which can be used by SDN-C and APP-C as a basis for their docker containersIncluded in seed codeDelivered in seed code

Third Party Products Dependencies

NameDescriptionVersion
OpenDaylightOpenDaylight SDN Controller PlatformNeon SR1

Testing and Integration Plans

...

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

Team Internal Milestone


MilestoneDescription DateComments
M2/M3Functionality Freeze / API Freeze


  • Final API definitions (swagger, Yang) due
Jan 3, 2020Last day to submit Frankfurt swagger / Yang changes to Gerrit

  • M2/M3 Jiras ready for review
Jan 6, 2020Release manager reviews worksheets to assess readiness for M2/M3 milestone

  • TSC M2/M3 approval vote
Jan 9, 2020



  • Code due for initial release
Jan 17, 2020Last day to submit code for initial release

  • Initial release builds available
Jan 23, 2020
M4Code Freeze


  • Code due for
Dublin
  • Frankfurt user stories
Feb 14, 2020Last day to submit Frankfurt code changes to Gerrit

  • M4 worksheets ready for review
Feb 17, 2020

Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:

  • All repos must have >= 55% code (line) coverage in Sonar
  • No failed Jenkins jobs
  • All CSIT tests pass
  • Healthchecks pass

  • M4 release builds available
Feb 19, 2020

  • TSC M4 approval vote
Feb 20, 2020


RC0Release Candidate 0


  • Code due for RC0 fixes
March 6, 2020Last date to submit code fixes for release candidate 0

  • RC0 release artifacts available
March 9, 2020

  • RC0 Jiras ready for review
March 9, 2020

  • TSC RC0 approval vote
March 12, 2020


RC1Release Candidate 1


  • Code due for RC1 fixes
March 20, 2020Last date to submit code fixes for Frankfurt release candidate 1

  • RC1 release artifacts available
March 23, 2020

  • RC1 Jiras ready for review
March 23, 2020

  • TSC RC1
March 26, 2020


RC2Release Candidate 2


  • Code due for final
Dublin
  • Frankfurt fixes
April 3, 2020Last date to submit code fixes for final Frankfurt release (RC2)

  • RC2 release artifacts available
April 6, 2020

  • RC2 Jiras ready for review
April 6, 2020

  • TSC RC2
April 9, 2020


Release Sign-OffFinal TSC Sign-OffApril 23, 2020
Frankfurt Release Sign-Off

Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

...