Agenda

• Calling all OOM committers and contributors - please attend the 1200EDT daily R1 blitz for OOM and HEAT around vetting the vFW - Vetted vFirewall Demo - Full draft how-to for F2F and ReadTheDocs
• JIRA board - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&view=planning&epics=visible
• Discuss Helm 2.6 upgrade in Rancher 1.6.11 (arrived 14 Nov) - we need to investigate/test the upgrade before forcing it in a template change
  
  • see following change that fixes vnc-portal and onap-log https://gerrit.onap.org/r/#/c/24225/
• Before submitting patches - test the entire OOM system (all pods) using the public repo - verify that no regressions occur (check against the CD server results) - especially for infrastructure changes
  Our currently supported setup is Rancher 1.6.10, Helm 2.3.0 and the latest Kubernetes (currently 1.8 but running 1.7.7) and Docker 1.12 (Note Rancher 2.0 is in testing on the latest Docker)
• continuedRelease 1.1 stable release
  • How to?
  • Propose meeting on a live system - blitz to verify issues - submit changes in that session
  • time: send out for 27, 28  and review next wed meet - todo
  • https://zoom.us/j/7939937123 will send out daily meeting 
• Architecture meeting: Tue:
  • S3P Carrier Grade release proposal : OOM CG deployment - OOM will be part of B* release
  • CD deployment, use consul HC, use distributed state of consul, 
• 4 Dec KubeCon (opnfv, VMware VIO - 2 teams - oom CaaS, and heat - for vFW - they need a lot of assistance 
• OPNFV - auto test group for now - getting DCAE going for OOM David B.
• goto Integration meet Tuesdays 10EDT 
  • OOM is more relevant for a smaller deployment (336G(included DCAE) vs (64 + DCAE), plus small HD
  • Key into 1.1 branch stability - CD duplicate to 1.1 along with master
• F2F in 2 weeks - 11 Dec - prep 8+ talks - help those involved - 25m - 45m
• vFW testing
• Epics for Beijing