Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

  • Config Management
  • HA in OOM
  • Deployment for new containers
  • Following OOM Logging guidelines for new projects / adjust logging for existing projects
  • OOM CI triggered by component teams commits - what is the impact to component teams here? hook OOM to the job builder of each component teams
  • Backup and Restore: 
  • Upgradability / Rollbacks: comply to a "rest" API for upgrade, downgrade of the platform, how do we support rolling upgrade? should we support 2 versions of a component at the same time?
  • Health Monitoring: request component teams to provide REST level monitoring, and probably deeper health check so that OOM can provide a consistent view across, enabling DEBUG, 
  • Recoverability: components should be mostly stateless at target. Need to define what could be done for Beijign
  • Graceful shutdown: support k8s graceful shutdown feature
  • Storage: comply to a common persistent volume strategy, 
  • No labels