Versions Compared

Old Version 10

changes.mady.by.user Ofir Sonsino

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.

...

Project NameEnter the name of the project
Target Release NameBeijing Release
Project Lifecycle StateMature Incubation (Refer to ONAP Charter, section 3.3 Project Lifecycle for further information)
Participating Company AT&T, Amdocs, Nokia

Scope

What is this release trying to address?

...

VID will contribute to the following use cases:

Use Case: VoLTE(approved)

VID will continue to support to the following use case:

Use Case: Residential Broadband vCPE (Approved)

Use Case: vFW/vDNS (Approved)


Minimum Viable Product

  • Read only "ONAP global role" permission for VID users
  • Specific role assignment for components instantiations 
  • Change management for selected work flows (Upgrade and Configuration)
  • PNF support
  • Tenant Isolation for test environments
  • Owning entity 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.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance001Do benchmark
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability0172 hours test
  • 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
Resiliency12Use Galera cluster
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01Cover 50% with JUnits
  • 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
Scalability01Test single site horizontal
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability110
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11Update user guides
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agree 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.

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
TBDHigh level description of the APIDate for which the API is reviewed and agreedTBDLink toward the detailed API descriptionNANANANANA

  • Third Party Products Dependencies

...

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.

...