OOM Meeting Notes - 2018-06-13
Notes
Branches - here are now five branches:
amsterdam (inactive),
release -1.0.0 (inactive),
beijing - will be updated only for critical fixes,
2.0.0-ONAP - fixed (this branch represents the official beijing tags)
master - which is used for ongoing development
Review of gerrit:
Fix SDNC portal liveness initialDelaySeconds - apply to both beijing/master
Fix Policy Nexus liveness initialDelaySeconds - apply to both beijing/master
Reconfigure haproxy to use dns resolution - apply to both beijing/master
All three are low impact fixes
Quick review of potential Casablanca work items:
Features
- Geo-Redundancy
- Backup & Restore
- OpenStack credential validation
- Single DB instances to clusters
- MariaDB to Galera migration
- DBaaS
- Reduce Config Size
- Improve startup time
- Pre-baked images
- Reduce # base images
- Log Shipper as DaemonSet
- Consul Agent as DaemonSet
- Secret integration with AAF
- SO Tiller Plugin
- Anti-affinity rules
- Centralized Manifest
- Resource Limits
- Use-Case environment files
- Operation without internet access
- private repo
- Real-time health check
- Storage Architecture
- central PVs with component PVCs
- multiple storageClasses (with implementations)DevOps
- Long lived CD system
- Work with Clover/Wenjing
- +1 Auto VerifyProduction
- System Health
- Fault Tolerance
- Startup Order
- RBAC
- kubectl restrictions
- Testing
- kubemonkey
- load balancer testing
- heal after pod failure
OOM Release Planning and creation of Epics/Stories will take place during the next couple weeks
During the Architecture face-to-face meeting in Vancouver a subset of these items were presented - https://wiki.onap.org/download/attachments/8225716/OOM%20Goals%20-%20Casablanca.pdf?version=5&modificationDate=1527513689000&api=v2
In addition to these work items the point was made that support for OOM on more cloud platforms (OpenShift) is also likely and welcome