Page Comparison

** 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 on incremental improvements in the following areas, as presented at the Casablanca Architecture F2F in Vancouver:

1. Persistent Storage
   • pluggable persistent storage technologies standardized to expand beyond static host path configuration + NFS backend
   • evolve standardized Helm Templates (introduced in Beijing) evolved slightly to  to support global configuration and sub chart overrides of Storage Classes
   • delivering provide support for GlusterFS  as the first storage class provisioner 

     Jira Legacy
     server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1228

2. Resource Limits
   
   • apply CPU and Memory limits per Helm ChartImproves limits to Helm Charts in order to improve Pod placement based on resources available to in a Kubernetes Cluster
   • OOM working with project teams for to gather accurate values per project 

     Jira Legacy
     server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1145

3. Common "shared" Helm Charts
   • mariadb-galera cluster
   • postgres
   • cassandra
   • ELK project teams benefit from "sharing" common Helm Charts that reference common images and tested functionality 
     • mariadb-galera cluster 

       Jira Legacy
       server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1176

     • mariadb (standalone) 

       Jira Legacy
       server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1164

     • postgres cluster 

       Jira Legacy
       server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1178

     • cassandra 

       Jira Legacy
       server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-

     1101
   Platform Resiliency
   
   • Backup and Restore 

     • 1177

     • redis 

       Jira Legacy
       server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-

     1232Node Selectors 

     • 1179

4. Platform Resiliency
   
   • Backup and Restore tools and procedures 

     Jira Legacy
     server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-

     1229Enable (Anti)Affinity Rules 

     1232

   • Node Selectors for Pod placement 

     Jira Legacy
     server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-12311229

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

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