Versions Compared

Old Version 12

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version Current

changes.mady.by.user Dan Timoney

Saved on

Key

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

...

Table of Contents
outlinetrue

Overview

Project NameEnter the name of the project
Target Release NameDublin
Project Lifecycle StateIncubation
Participating Company AMDOCS, AT&T, Bell Canada, Ericsson,Huawei, IBM, Tech Mahindra

Scope

What is this release trying to address?

...

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) 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:

  • Controller container
  • Database container
  • Admin portal 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 (Deprecated) page on this wiki.  Please see the SDN-C section of that page for subcomponent list of SDN-C.

...

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance00Awaiting guidance from Benchmark subcommittee
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01SDNC will perform 72 hour soak at component level. We assume that integration team will also do a 72 hour ONAP soak which includes SDNC.
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency12In Beijing, CCSDK will support a clustered OpenDaylight configuration in Kubernetes, as well as a clustered database, to allow for automated detection and recovery within a site. SDNC will use that configuration to meet this requirement. See SDN-C Clustering on Kubernetes for further details
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01SDNC will improve test coverage to > 50%
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage + 50% test coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability01SDNC can be scaled either by adding additional OpenDaylight containers and/or database containers, or by deploying multiple instances of SDNC cluster.
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11SDNC will support ONAP standard logging.
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11See readthedocs and wiki.
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

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 APIAPI used to request resources for VNFs. Will be deprecated in Beijing in favor of Generic Resource API.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 PlatformFluorine


Testing and Integration Plans

...

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 identifiedImpact
To fill outTo fill out

Known Defects and Issues

Provide a link toward the list of all known project bugs.

...

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).

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

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.

...

The following table shows the major project milestones and intermediate milestones for the Dublin release. 


MilestoneDescription DateComments
M1End of release planning
Formal commitment to release scope

  • M1 worksheets ready for review
Jan 22, 2019Release manager reviews worksheets to assess readiness for M1 milestone

  • TSC M1 approval vote
Jan 24, 2019


M2Functionality Freeze


  • Stable user stories baselined
Feb 15, 2019

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

  • TSC M2 approval vote
Feb 21, 2019


M3API Freeze


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

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

  • TSC M3 approval vote
March 14, 2019


M4Code Freeze


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

  • M4 worksheets ready for review
April
2
9, 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
11, 2019


RC0Release Candidate 0


  • Code due for RC0 fixes
April 19, 2019Last 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


RC1Release Candidate 1


  • Code due for RC1 fixes
May 3, 2019Last 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


RC2Release Candidate 2


  • Code due for final Dublin fixes
May 17, 2019Last 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-OffFinal TSC Sign-OffMay 30, 2019Dublin Release Sign-Off

Documentation, Training

  • Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  • Highlight the team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

...