Versions Compared

Old Version 8

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.


Table of Contents
outlinetrue

Overview

...

  • Platform Maturity (i.e., S3P items)
    • Resiliency
      • Level 1 - test only based on the work from Beijing
    • Scalability
      • Level 0
    • 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 Reach CI bagging badging passing level
      • encrypted 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 strach stretch goal based on the a risk from portal.
    • Performance
      • level 0 no work required.
    • Manageability
      • level 1
      • align with onap logging spec 1.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:
    • Release Notes.
    • enhance Enhance the available documentation to cover more of the application functionality and usability.
  • functional 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
  • enhancementsEnhancements
    • add more functionality to the sdc generic designer support

...

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

...

Platform Maturity

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.

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)

...

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.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

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

...

Risk identifiedMitigation PlanContingency Plan
sdc aaf integrationnonemove integration to dublin

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.