...
The following table lists the new functional requirements for the Frankfurt Release:
| Requirements | Companies Supporting Requirement | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Fujitsu | ||||||||||
| AT&T Bell Canada Ericsson Huawei Orange | ||||||||||
| IBM | ||||||||||
| Ericsson Huawei | ||||||||||
| Huawei | ||||||||||
| Huawei | ||||||||||
| Ericsson IBM | ||||||||||
| Tech Mahindra | ||||||||||
| Wipro | ||||||||||
| AT&T | ||||||||||
| Orange Samsung |
Minimum Viable Product
The following epics represent the minimum viable product of the CCSDK Frankfurt Release:
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=CCSDK and issuetype in (epic) and fixversion="Frankfurt Release" and priority >= priority< high serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
| 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:
| 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.
...
API Incoming Dependencies
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| 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) |
|---|---|---|---|---|
| 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 |
|---|---|---|
| OpenDaylight | OpenDaylight SDN Controller Platform | Neon 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
| Milestone | Description | Date | Comments |
|---|---|---|---|
| M2/M3 | Functionality Freeze / API Freeze | ||
| Jan 3, 2020 | Last day to submit Frankfurt swagger / Yang changes to Gerrit | |
| Jan 6, 2020 | Release manager reviews worksheets to assess readiness for M2/M3 milestone | |
| Jan 9, 2020 | ||
| Jan 17, 2020 | Last day to submit code for initial release | |
| Jan 23, 2020 | ||
| M4 | Code Freeze | ||
|
| Feb 14, 2020 | Last day to submit Frankfurt code changes to Gerrit | |
| Feb 17, 2020 | Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:
| |
| Feb 19, 2020 | ||
| Feb 20, 2020 | ||
| RC0 | Release Candidate 0 | ||
| March 6, 2020 | Last date to submit code fixes for release candidate 0 | |
| March 9, 2020 | ||
| March 9, 2020 | ||
| March 12, 2020 | ||
| RC1 | Release Candidate 1 | ||
| March 20, 2020 | Last date to submit code fixes for Frankfurt release candidate 1 | |
| March 23, 2020 | ||
| March 23, 2020 | ||
| March 26, 2020 | ||
| RC2 | Release Candidate 2 | ||
|
| April 3, 2020 | Last date to submit code fixes for final Frankfurt release (RC2) | |
| April 6, 2020 | ||
| April 6, 2020 | ||
| April 9, 2020 | ||
| Release Sign-Off | Final TSC Sign-Off | April 23, 2020 | Frankfurt Release Sign-Off |
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation
...