Versions Compared

Key

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

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 discussed at the Casablanca Architecture F2F in Vancouver:

  1. 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 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyOOM-1228
  2. 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 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyOOM-1145
  3. Common "shared" Helm Charts
    • project teams benefit from "sharing" common Helm Charts that reference common images and tested functionality 
      • mariadb-galera cluster 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyOOM-1176
      • mariadb (standalone) 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyOOM-1164
      • postgres cluster 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyOOM-1178
      • cassandra 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyOOM-1177
      • redis 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyOOM-1179
  4. Platform Resiliency
    • Backup and Restore 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyOOM-1232
    • Node Selectors 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyOOM-1229


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.