Versions Compared

Key

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

...

Project NameEnter the name of the project
Target Release NameCasablanca Release
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Amdocs, Nokia

...

  1. S3P improvements
  2. VNF Scaling enhancements
  3. PNF support
  4. Scheduling capabilites
  5. PNF support
  6. (stretch goal)

Use Cases

VID will continue supporting the following use case:

Use Case: Residential Broadband vCPE (Approved)

Use Case: vFW/vDNS (Approved)

Use Case: VoLTE(approved)

Use Case Proposal - VNF Scale Out

And will add support to the following:

Centralized Representation and Consistent Identification of Cloud Regions In ONAP

Scaling Use Case Extension

Change Management Extensions (partially)

Deployment of the hybrid 5G Network (PNF/VNF)

Change Management Extensions (best effort)

Centralized Representation and Consistent Identification of Cloud Regions In ONAP (best effort)

Minimum Viable Product

  • Instantiation of service, vnfs and vf modules
  • change management 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
Performance00
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability12
  • 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
Resiliency22
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security11

Reaching 100% for CII passing badge;

Switch to HTTPS;

Integrate with AAF

Jira Legacy
serverSystem Jira
columnskey,summary,type,status
maximumIssues20
jqlQuerykey = VID-257
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • 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
Scalability11
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11(with logiing v1.2 spec support)

Jira Legacy
serverSystem Jira
columnskey,summary,type,status
maximumIssues20
jqlQuerykey = VID-253
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11

Jira Legacy
key
serverSystem Jira
columnskey,summary,type,status
maximumIssues20
jqlQuerykey = VID-256
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176VID-256

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

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
Scale out (endpoint TBD)SO API for VNF scale outTBDTBDTBD
Service instantiation - /ecomp/mso/infra/serviceInstances/v6SO API for service instantiation with PNF supportTBDTBDTBD
  • API Outgoing 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

...