Versions Compared

Old Version 3

changes.mady.by.user Jun Hu

Saved on

compared with

New Version Current

changes.mady.by.user Mike Elliott

Saved on

Key

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

Feature Name

Brief Description

Related Epic Number (if exists)

Release Targeted

Manage multiple ONAP instances

Multiple ONAP instances will be deployed in production environment.

OOM should be able to manage multiple ONAP instances. 

OOM-1323


Set operation restrictionThe system is in potential risks, since  OOM user grants Kubernetes administration role. OOM-1323
Track operation historyThe Management System should be able to track operation history.OOM-1323
Visualize Helm Values DataIn helm charts, the values files are distributed. So the UI should be able to fetch the real-time helm value and centralize those data. OOM-1323
User friendly UIshould provide an UI, which operator can access it to execute helm operation, monitor current helm value and operation history.OOM-1323
DBaaS

Components that use the same database technology, can share a single highly-available and scalable cluster with separate schemas and credentials.

Reduces footprint of ONAP deployment.

OOM-1175
Geographic distribution of ONAP

It should be possible to deploy a single ONAP instance (containing HA component instances) that spans across a geographically separated infrastructure.

Builds on node selector labels and affinity/anti-affinity rules delivered in Casablanca.

OOM-346