Notes

• Beijing Branch
  • Strategy: cutting branch today 20180606 (changes before only for image changes)
    • Issue with : https://gerrit.onap.org/r/#/c/50587/ (hc ok, will retest - may merge the 32-11 nodeport change)
  • Change management: patches after the branch? INT team will pickup a dot release if possible (containing the patches)
  • (discussion on dot release : Mike, Frank,
    • - release not fully stable anyway - dependency in 2 parts (oom chart changes and project config/code changes in re-released docker images)
• Mikes values.yaml overrides for production deployments - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-927

• Working with LF to get centralized helm chart repository - no more make or clone commands locally - just helm install
  • Could use combination of LF repo and local repo
    
    
• go over bugs 
  • https://gerrit.onap.org/r/#/c/48093/
  • AAF startup issue
• https://gerrit.onap.org/r/#/q/status:open+project:+oom
• Q) appc issues: High: Aaron Hay

  • Jira Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1124

  • config gets reset in workaround - pushing review to casablanca - https://gerrit.onap.org/r/50409
  • without change above - need to apply odl config changes outside of a helm upgrade
  • can cherry pick to the branch
  • Need to discuss change management for beijing
    
    
• Q) AAF integration (SDC, AAI and Logging implementors so far)
• SO is passing only windriver periodically - failing in tlab and aws
• Talk to seshu on http://jenkins.onap.info/job/oom-cd-master/3103/console