Versions Compared

Old Version 3

changes.mady.by.user Michael Lando

Saved on

compared with

New Version Current

changes.mady.by.user Ofir Sonsino

Saved on

Key

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

...

  • Platform Maturity (i.e., S3P items)
    • Resiliency
      • Level 1 - test only based on the work from Beijing
      • DB Resiliency was a limitation in Beijing due to the Active/Standby nature of MySQL. MariaDB w/Galera provides an active-active clustered configuration, which will support local fail-over.
    • Scalability
      • Level 0
      Scalability
      • Level 1 will be a regression run on Casablanca release - anticipate this to be test only
    • Stability 
      • Level 1 will be a regression run on Casablanca release - anticipate this to be test only
      • Level 2 requirement is expected to be covered by the Integration team.
    • Security 
      • Required Level 1
      • Reach CI badging passing level
      • Encrypted communication enable https support. sdc will work in a mixe mode http interface will continue working but internal comunication will be done using https.
      • aaf integration is a stretch goal based on the a risk from portal.Address outstanding items related to CII Passing Badge:
      • Clearing Critical and Medium Nexus IQ Security alerts to the extent possible, Including no critical and high known vulnerabilities > 60 days old.
        • Addressing  security-related items from Passing Badge related to encryption
    • Performance
      • level 0 no work required.
    • Manageability
      • level 1
      • align with onap logging spec 1.
    Support new LCM action Reboot and various other enhancements to existing LCM actions (Tracked under Epic: APPC-899)
      • 2
    • Usability
      • level 1
      • User guide created update
      • Deployment documentation update
      • API documentation update
      • All new API’s must adhere to the ONAP API Common Versioning 
  • Documentation updates (readthedocs) for Casablanca, such as, but not limited to:
    LCM API Guide
    • Release Notes
  • Code Coverage for CDT (Javascript) - TBD, no commitment at this stage
  • Use Cases
    • ConfigScaleOut - Partially supported 
      • Support Retrieval of configuration data from AAI instead of having SO pass configuration data in payload - (investigate if we can we reuse the named query)
        • Dependency on SO to pass the vf-module-id of the vDNS instance that must be added.
        • Assumption is that AAI data needed is available
      • No commitment on Controller Type since requirements are still unclear.
    • Change Management - No Commitment
    • 5G/PNF - No Commitment (although APPC is listed as an impacted component, there does not appear to be any immediate requirement for Casablanca. Items noted are longer road map items)

Use Cases

SDC will contribute to support:

Use Case: Residential Broadband vCPE (Approved)

    • .
    • Enhance the available documentation to cover more of the application functionality and usability.
  • Functional requirments:
  • HPA
    • SDC will support the work done to support HPA in ONAP with the help from intel. 
  • Change Management
    • SDC will support the work being done for the change management work
    • SDC will enhance our capability in designing workflows and complete the E2E flow between SDC and so with the help from Amdocs.
  • Scaling
    • SDC will support the work being done for the scaling work.
  • 5G/PNF
    • the PNF support in sdc will be based on the capabilities from Beijing, no additional work is planned.
  • Architecture Alignment
    • sdc will start creating an infrastructure to support RTC
    • start supporting the sol004 csar pckage
  • HEAT support
    • sdc will continue to support the heat based deployment
  • Testing
    • enhance the sdc csit test scope
    • create cd testing for the sdc sub-components workflow and dcae-ds
    • add unit test coverage for the ui and reach 10% coverage
  • Enhancements
    • add more functionality to the sdc generic designer support

Use Cases

SDC will support the following use cases based on the current functionality:

CCVPN(Cross Domain and Cross Layer VPN) USE CASE

OpenSource Access Manager (OSAM) Use CaseUse Case: VoLTE(approved)

SDC will continue to support:

...

Use Case: VoLTE(approved)

Use Case: VoLTE(approved)

Minimum Viable Product

Describe the MVP for this release.

SDC:

deliver all the need dockers and DB needed to support sdc functionality and the needed scripts for deploying it in HEAT heat and in OOM.

WORKFLOW:

deliver all the need dockers needed to support workflow designer functionality and the needed scripts for deploying it in HEAT heat and in OOM.

DCAE-DS:

deliver all the need dockers needed to support dcae-ds functionality and the needed scripts for deploying it in HEAT heat and in OOM.

SDC SDK's:

sdc-destribution-client

sdc-tosca

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

Deliverable NameDeliverable DescriptionDeliverable Location
SDC Docker ImagesExecutableDocker image available on nexus3
SDC TOSCA SDKJAR fileAvailable on nexus as MAVEN dependency
SDC

Java Source CodeThe Java code for the main SDC components.sdc Git repositories
Deployment ScriptsChef recipes used to configure the Docker containers.sdc Git repositories

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

  • Jtosca
  • SDC Tosca
  • SDC Distribution Client
  • SDC base docker
  • SDC titan cassandra
  •  SDC SDC workflow designer 
  • DCAE-DS

Architecture

High level architecture diagram

ONAP Amsterdam ARC_1_0_0.pngImage RemovedImage Added

Platform Maturity

...

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Performance0

0

(stretch goal - 1)



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

(stretch goal - 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

(stretch goal - 2)




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

1

(stretch goal - 2)

+

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
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability0

0

(stretch goal - 1)



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

1

(stretch goal - 2)



  • 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; externalized configuration management
Usability01

1

(stretch goal - 2)



  • 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)
dmaapusing Cambria clientapi for pushing and retrieving notificationsavilablesdkTo fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

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


To fill out

Name

Description

Version

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
To fill outTo fill out
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
N/AN/ATo fill outTo fill out
Known Defects and Issues
Provide a link toward the list of all known project bugs.
 Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sdc and issuetype in (bug) and fixversion="Beijing Casablanca Release" and status not in (closed) 
serverId425b2b0a-557c-3c0c-b515-579789cceedb
...
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
sdc aaf integrationnonemove integration to dublinTo fill outTo fill outTo fill out
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
  • 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.
...