Versions Compared

Old Version 14

changes.mady.by.user Huabing Zhao

Saved on

compared with

New Version Current

changes.mady.by.user Huabing Zhao

Saved on

Key

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

...

  • to support all the use cases (as a common service)
  • to provide access to new  version of ONAP APIs via MSB
  • to implement the S3P requirements
  • to fix the issues reported by other projects and users
  • to support service mesh efforts (limited resources)

Use Cases

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

As a common service project, MSB is the upstream of other projects to provide inter-service communication infrastructure, so it will be involved in the use cases indirectly. 

Just list the use cases of VF-C and MultiCloud project which depends on MSB here  , other use case will also be supported if msb involvement is needed.

Use Case:

Residential Broadband vCPE (Approved)

CCVPN Use Case (Dublin)

vFW/vDNS

vCPE

Functional Requirements:

Hardware Platform Enablement In ONAP

Centralized Representation and Consistent Identification of Cloud Regions In ONAP

Auto Scaling - stretch goal Release 4 (Dublin) Use Cases and functional requirements

Minimum Viable Product

  • Internal API Gateway:  Service API gateway which serve as a transparent inter-service communication proxy  to provide service discovery/routing/load balancing inside ONAP system.

  • External API Gateway:  Service API Gateway which serve as an entrance to allow external system access to ONAP services.

  • Service Discovery:  Provides service registration and discovery for ONAP microservices, which leverage Consul and builds an abstract layer on top of it to make it agnostic to the registration provider.

  • JAVA SDK: Provides a JAVA SDK for rapid microservices development, including service registration, service discovery, request routing, load balancing, retry, etc.

  • Swagger SD: Swagger SDK could be used to generate the server stub and client part in different language.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance12Capture the baseline performance of API Gateway, such as QPS Latency Transfer/sec.
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability1272 hours soak test with random transactions from ONAP microservices via Internal API Gateway.
  • 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
Resiliency22MSB integrates with OOM and leverage kubernetes to provide automated 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)
Security011Reach the 50% Test Coverage, get CII Passing badge(now 98%).
  • 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
Scalability11Provide cluster deployment for MSB components to achieve single site horizontal scaling.
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11MSB provide access logging at API gateway.
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability12Provide all the required documentation.
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

Risk identifiedMitigation PlanContingency Plan



Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...