Versions Compared

Old Version 6

changes.mady.by.user Michael Lando

Saved on

compared with

New Version 7

changes.mady.by.user Michael Lando

Saved on

Key

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


Table of Contents
outlinetrue

Overview

...

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Performance0

0



  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability1

2



  • 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
Resiliency1

1




  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security1

1+

AAF integration and https support



  • 1 – 70% pass level 1 (CII Passing plus more)
  • 2 – 70% pass CII Silver (plus more)
  • 3 – 70% pass CII Gold (plus more)
  • 4 – 100% pass CII Gold
Scalability0

0



  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability1

1+loggin alignement with 1.2 loging spec



  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; externalized configuration management; adhere to application logging spec V1.2
  • 3 - tracing across components;
Usability1

1



  • 1– user guide; deployment documentation; API documentation (new APIs follow policy, rest Swagger 2.0); adherence to coding guidelines
  • 2 – API Documentation (changed and external APIs follow policy); UI consistency; usability testing; tutorial documentation
  • 3 – API Documentation (all follow policy)


API Incoming

...

Dependencies 

List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI 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

...

Portaluser management APIscrou api for user managementavilableexposed by portal sdk
destribution clientapis for retriving artifacts from catalogdownload artifactsavilableexposed by sdc part of external apis.

API Outgoing Dependencies 

API this release is delivering to other releases.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI 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 descriptiondmaapusing Cambria clientapi for pushing and retrieving notificationsavilablesdk

Third Party Products Dependencies -TBD

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).


Name

Description

Version

To fill outTo fill outTo fill out

Cassandra

Open-source distributed storage system

2.1.19
DockerVM container
ElasticSearchSearch framework2.4.6
titanOpen-source, distributed graph database

1.0.0

JettyOpen-source application server
9.3.X
UbuntuOpen-source software operating system16.0.4-LTS
kibanaanalytic disply server
4.3.3
vncvnc server used for ui testing
ubuntu-xfce-vnc:1.3.0

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

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.

  • validate uses cases and pairwise testing of sdc with other components
  • enhance the csait to include more tests

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 identifiedImpact
To fill outTo fill outN/AN/A

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 materialize (contingency).

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill outsdc aaf integrationnonemove integration to dublin

Resources

Fill out the Resources Committed to the Release centralized page.

...

  • 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...
Note
titleNote

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

...