OOM Requirements Gathering for Release Planning
- Mike Elliott
- jh245g@att.com
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. | ||
Set operation restriction | The system is in potential risks, since OOM user grants Kubernetes administration role. | ||
Track operation history | The Management System should be able to track operation history. | ||
Visualize Helm Values Data | In helm charts, the values files are distributed. So the UI should be able to fetch the real-time helm value and centralize those data. | ||
User friendly UI | should provide an UI, which operator can access it to execute helm operation, monitor current helm value and operation history. | ||
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. | ||
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. |