Page History

...

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
     server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-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  JiraserverONAP JIRAserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyOOM-1101
4. Platform Resiliency
   
   • Backup and Restore 

     Jira
     server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-1232

   • Node Selectors 

     Jira
     server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-1229

   • Enable (Anti)Affinity Rules 

     Jira
     server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-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.