...
- 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
- Reviews in progress/coming in
- https://gerrit.onap.org/r/#/q/status:open+oom
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-151 - 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
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-324 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAF-170 - 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