Agenda:

• Updates on OOM development
  • Global state is that all containers are deployable with OOM. AAF was completed. DCAEg2 deployer onboarded as well.
• OOM vs Amsterdam release
  • Pushing for OOM to be part of the Amsterdam release. Worst case OOM will be part of Amsterdam 1.2.0 release,.
• M4 (code freeze) readiness
  • Question: who is creating the Beijing branches?
  • Jenkins job in progress to clear the "Nexus binary" blocker
• Questions
  • Should we externalize common values from YAML to have centralized place to have common default values?
    • One key requirements: need to make sure that each project is independent. 
      • The current proposal allows each individual project or deployment to override a parent value 
      • HELM allows to override default values. A good example could be that there is a default image (staging-latest) but that any project could override the default image with a specific version. 
  • There are inconsistencies in the way image references are made (1 line vs split)
    • helm recommendation is to split
    • we will create bugs in JIRA to track and fix the inconsistent references
• David from Orange will work with the Integration team to run the OOM project within the Integration team. First objective is to have a CI integration with ONAP, OOM and OPNFV. Mike Elliott offered to help. He setup OOM in the Integration environment.
  • There is a project within OPNVF to install k8s on bare metal
  • Recommendation for David: install a local Nexus server to avoid long download times
• Michael O'Brien - (deprecated as of 20170508) - use obrienlabs is attending a meeting for OPNVF every monday to discuss OOM integration. David S and David Blaisonneau to be added to the list by Michael O'Brien - (deprecated as of 20170508) - use obrienlabs
• OOM documentation has been officially added to readthedocs.io. 
• Consul is now running and available to do health checks on many of the components. The overall health check is targeted for Beijing release.
• Next Steps
  • Formalize the scope for Beijing release. Overall goal for OOM/Beijing is to allow for PRODUCTION (robustness, auto-healing, scaling, etc) and ease of operations.