Notes

• Discussion open

• Segment on documentation @Roger Maitland

• helm chart work review

• Redhat is joining

• M4 close around 28th march - architectural changes coming in (including DCAEGEN2 when released, SO, SDN-R (new component))
  integration of this work will be around code freeze time unless we get ahead of the changes

• SDC changes to review

• all devs don't post in draft mode when in final review

• Borislav on 722/733

• appc not shifting to mariadb yet for beijing - long term with galera

• new b* deployment is based on helm charts - ie: mariadb (single configuration of a cluster = galera) - will work with teams just after b* release

• mariadb question: ports? - need container name (inside each pod) collision strategy (values.yaml files, cover off chart.yaml)

• dmaap because it is common needs special handling - policy decision point needs to listen on dmaap

• JIRA - epic required for above 

• AAFi integration offline with @Roger Maitland

• Welcome Red Hat @Tal Liron and @Frank Zdarsky

Other notes

• Reviews in progress/coming in

• https://gerrit.onap.org/r/#/q/status:open+oom

• MULTICLOUD-151: Logging EnablementClosed

• Minor security review of OOM on nodeports - recommendation is to do the same cert/user/pass like aai-service - project will implement

• security team is working with AAF - raised container issue for 

• OOM-324: AAF Service Container logging errorClosed

• AAF-170: AAF container failure tracking for OOM-324Closed

• IBM is bringing up OOM (in addition to existing Azure and AWS teams) - they have a blog and will transition it to onap https://developer.ibm.com/code/howtos/get-onap-up-and-running-on-icp/

• Prep for M4 code freeze