Versions Compared

Old Version 1

changes.mady.by.user Dan Timoney

Saved on

compared with

New Version 2

changes.mady.by.user Dan Timoney

Saved on

Key

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

...

Project NameEnter the name of the project
Target Release NameFrankfurt
Project Lifecycle StateIncubation
Participating Companies AT&T, Bell CanadaEricsson, EricssonFujitsu, IBM, Huawei, Nokia, Orange, Samsung, Tech Mahindra, Wipro

Scope

What is this release trying to address?

...

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

Fujitsu Jira LegacyserverSystem Jira
RequirementsCompanies Supporting Requirement

Jira Legacy
serverSystem Jira

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyREQ-37

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

33

AT&T

Bell Canada

Ericsson 

141

Huawei

Orange

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

267

37

IBM
Fujitsu

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

84

162

Ericsson
AT&T

Huawei

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

53

154

Huawei
IBM

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

96

267

Huawei Jira LegacyserverSystem Jira

IBM

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

Ericsson

IBM

Jira Legacy
serverSystem Jira

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyREQ-42Tech Mahindra

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

158

76

Wipro
Ericcson

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 SDNC Frankfurt Release:

...

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


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

Docker containers associated with SDNC project:

  • Ansible server container
  • Controller (OpenDaylight) container
  • DMAAP listener container
  • SDC (UEB) listener container
ONAP Nexus
DocumentationUser and developer guidesONAP Wiki
SDNC 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 SDNC section of that page for subcomponent list of SDNC.

...

API Incoming Dependencies


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
A&AI : VNFAPI used to read/write information about VNFsDefined in seed codeIncluded in seed codeTBD
SDC : distributionAPI used to distribute artifacts from SDC to subscribersDefined in seed codeIncluded in seed codeTBD
DMaaPAPI used to receive DHCP event notification8/23/178/23/17DMaaP API


API Outgoing Dependencies


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
HealthcheckAPI used to verify that platform is available and healthyIncluded in seed codeDelivered in seed codeTBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki)
Generic VNF API

API used to request resources for VNFs. Will be deprecated in Beijing in favor of Generic Resource API.

Note: This API is deprecated in Frankfurt and will be removed in Guilin

Included in seed codeDelivered in seed codeTBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki)
Generic Resource APIAPI used to request resources for VNFs. This API is a superset of the generic VNF API, which it replacesIncluded in Amsterdam releaseDelivered in AmsterdamTBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki)

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


M4Code Freeze


  • Code due for 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 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

...