Agenda

• JIRA board updateOOM Readiness for Amtsterdam- https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&view=planning&epics=visible
• OOM Amsterdam Readiness 
  • Closing all Amsterdam bugs
  • OOM Amsterdam Release notes
• OPNFV PlugFest assistance Dec 4-8 - https://wiki.opnfv.org/display/EVNT/Plugfest+Planning+Page
• Discussion about the F2F in Dec 11-13 - https://lists.onap.org/pipermail/onap-discuss/2017-November/006274.html
• Demo: Continuous Delivery POC - https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Auto+Continuous+Deployment+via+Jenkins+and+Kibana
• Discuss commits including component committers - if aai or log component in OOM is modified - include developers from those projects in the review
  • Best practice: involve the component teams when there are impacts to other components. 
  • OOM wants to become on the "best practices" side rather than implementing all OOM configs
• Discuss WIKI design pages for large stories/epics - JIRA Design Pages
  
• kubecon
• Shay (Unlicensed) OOM-63: deploying K8S using TOSCA is now available. Code will be committed on the Beining release
  • Next step will be to deploy ONAP applications through OOM on the TOSCA deployed k8s.
• David S to figure out what is rquired to make sure the OOM code gets part of the release. Gildas Lanilis Gmail ?
• close all high bugs for A* release
• A* release notes required
• doc release notes required - Michael to arrange with doc team
• Borislav will be a committer when the TSC approval goes through
• verify vfc failing in heat as well for oom-19 oom-333
• OOM-311 update with so pass - passing for last 3 days - see http://jenkins.onap.info/job/oom-cd/123/console
• Michael check on vfc JIRAs - Discuss with Ran for HEAT status on these
•  Michael recheck dcaegen2 status
• post link to vFW to meeting minutes - Running the ONAP Demos and ONAP on Kubernetes
• Post JIRA for generating config file per use use case -vVolte etc..
• OOM-324 - look at it for logging help
• Roger - Carrier Grade page updates - please review federation and upcoming diagrams
• Note: AT&T is looking at large deployments for above
• Discuss KubeCon assistance work - 3 pieces of work
• 8+ OOM F2F discussions - need to collaborate
• KubeCon mini summit available
• move JIRA design page to per project - OOM Design
• OOM-63 shay naeh (at SC- F2F) (alternate for rancher boostrap of K8s) - uses helm charts - need documentation link - getcloudify.org
• 1.1.0 branch - put major fixes only
• master continue committing as usual
• onap dockerhub images - should they migrate to nexus3?
• Discuss versioning work as part of global config - Mayank Gupta
• Discuss cloudify. helm, kubernetes - how they work together for Beijing - ie support hybrid environments