Versions Compared

Key

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

...

Describe the problem being solved by this release.

The VF-C  Beijing release has two primary objectives: 1. improving platform maturity ; 2. supporting use cases.  

Functionality enhancement to existing use cases, NS/VNF scaling, HPA feature support, indirect mode

...

System maturity enhancement, add integration with OOM/ Logging/A&AI-IM


Features and Functionality for this Release:

...

Integration specification for OOM/ Logging/A&AI-IM

Functionalities

...

H

Functionality Name

In or Out

Priority

Stretch

OOM Integration

IN

Integration with OOM

A&AI -IM Integration

In

M

Integration with A&AI- IM

Logging Integration

In

M

Integration with Logging

...

Deliverable Name

Deliverable Description

NS/VNF Scaling API

NS/VNF Scaling API to So/Policy/UUI

Optimized NS/LCM API

Provide the Optimized NS/LCM API/UUI

Indirect mode proxy

Provide Indirect mode proxy function

HPA feature parse

Provide HPA feature parse function

GVNFM with improvement function

Provide GVNFM which can used to support vFW/vLB use case

Source CodeSource code for all VF-C components
Maven ArtifactsMaven Artifacts for all VF-C components
Docker ContainersDocker container  associated with VF-C componets
DocumentationVF-C detailed documentation


Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01Awaiting guidance from Benchmark subcommittee
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01We assume that integration team will do a 72 hour ONAP soak which includes VF-C.
  • 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
Resiliency12automated detection and recovery
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01

increase test coverage to 50%


  • 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
Scalability00(*)
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability01support ONAP standard logging.
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11onap.readthedocs.io
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...