Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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:

  1. 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-1228 - Getting issue details... STATUS
  2. 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
  3. Common "shared" Helm Charts
    • mariadb-galera cluster
    • postgres
    • cassandra
  4. Platform Resiliency
    • Backup and Restore  OOM-1232 - Getting issue details... STATUS
    • Node Selectors  OOM-1229 - Getting issue details... STATUS
    • Enable (Anti)Affinity Rules  OOM-1231 - Getting issue details... STATUS


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.

  • No labels