OOM Casablanca - M3 Architecture Review

Architecture Changes since Beijing

There are no significant architecture changes for OOM in the Casablanca release.

The focus is on incremental improvements in the following areas, as presented at the Casablanca Architecture F2F in Vancouver:

Persistent Storage
- pluggable persistent storage technologies to expand beyond static host path configuration + NFS backend
- evolve standardized Helm Templates (introduced in Beijing) to support global configuration and sub chart overrides of Storage Classes
- provide support for GlusterFS as the first storage class provisioner https://lf-onap.atlassian.net/browse/OOM-1228
Resource Limits
- apply CPU and Memory limits to Helm Charts in order to improve Pod placement based on resources available in a Kubernetes Cluster
- OOM working with teams to gather accurate values per project https://lf-onap.atlassian.net/browse/OOM-1145
Common "shared" Helm Charts
- project teams benefit from "sharing" common Helm Charts that reference common images and tested functionality
  - mariadb-galera cluster https://lf-onap.atlassian.net/browse/OOM-1176
  - mariadb (standalone) https://lf-onap.atlassian.net/browse/OOM-1164
  - postgres cluster OOM-1178: Create Charts for common Postres ClusterClosed
  - cassandra OOM-1177: Create Charts for common CassandraClosed
  - redis OOM-1179: Create Charts for common RedisClosed
Platform Resiliency
- Backup and Restore tools and procedures OOM-1232: Provide a Backup and Restore SolutionClosed
- Node Selectors for Pod placement OOM-1229: Add nodeSelectors to Helm chartsClosed

Software Changes since Beijing

Upgrading from Helm 2.8.2 to 2.9.1.

API Updates

OOM does not provide any external APIs.

S3P Updates

OOM uses Kubernetes to help ONAP applications to reach their S3P goals. Usability and Manageability come through the use of Helm to configure and deploy ONAP.

(115%)

Information/Data Model Alignment

OOM does not ingest the ONAP data model.