Versions Compared

Old Version 3

changes.mady.by.user Yan Yang

Saved on

compared with

New Version 4

changes.mady.by.user Yan Yang

Saved on

Key

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

...

2. Supporting use cases identified by ONAP and integration:  VoLTE, vCPE, HPA, Centralized Representation and Consistent Identification of Cloud Regions In ONAP

3. Enhancement to VF-C existing features; Integration with OOF 

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

...

Hardware Platform Enablement In ONAP

Centralized Representation and Consistent Identification of Cloud Regions In ONAP

VNF Auto Scaling - stretch goal 

...

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name

Deliverable Description

To fill outTo fill out
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.

...

Indicate where your project fit within the ONAP Archiecture diagram.

TBD (add new R3 arch diagram with new components and interface)

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance11
  • 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+
  • 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
Scalability01
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11+
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11+
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

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

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out

Catalog API (SDC)

API to read the NS and VNF Catalog




Parser API(Modeling)

API for parsering TOSCA file




Micro-services bus API

API for registration and use of micro-services bus




Multi-vim API

API to allocate resource to VIM




DCAE VES collector SB API

API to push vnf fcaps data to VES collector




A&AI API

API to store inventory




OOF APIAPI to chose VIM which is used to deploy VNF
Link toward the detailed API description



  • API Outgoing Dependencies

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)

NSLCM API Definition

Network services lifecycle management APIs, including scaling API



To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out

Link toward the detailed API description

VNFM Driver API Definition

VNFM Driver component northbound APIs, including scaling API




VNF LCM API Definitionprovide VNF lifecycle management APIs


  • Third Party Products Dependencies

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

NameDescriptionVersion
To fill outTo fill outTo fill outactiviti workflow engine

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...