Versions Compared

Old Version 3

changes.mady.by.user Mike Elliott

Saved on

compared with

New Version 4

changes.mady.by.user Mike Elliott

Saved on

Key

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

...

  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 GlusterFS for using GlusterFS as a storage class provisioner 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyOOM-1228
  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
    • cassandraELK  Jira LegacyserverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyOOM-1101
  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
    • Enable (Anti)Affinity Rules 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyOOM-1231

...

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

No impact on OOMOOM does not ingest the ONAP data model.