** Work in Progress**
Architecture Changes since Beijing
There are no significant architecture changes for OOM in the Casablanca release.
The focus for this release is in the following areas:
- Persistent Storage
- pluggable persistent storage technologies
- standardized Helm Templates (introduced in Beijing) evolved slightly to support global configuration and sub chart overrides of Storage Classes
- delivering support for using GlusterFS as a storage class provisioner - OOM-1228Getting issue details... STATUS
- Resource Limits
- CPU and Memory limits per Helm Chart
- Improves Pod placement based on resources available to a Kubernetes Cluster
- OOM working with project teams for accurate values
- Common "shared" Helm Charts
- mariadb-galera cluster
- postgres
- cassandra
- Platform Resiliency
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.
Information/Data Model Alignment
OOM does not ingest the ONAP data model.