SO Weekly Meeting 2020-12-02

Agenda Topics:

Project Status in Guilin Release

Guilin Milestone Status

Guilin Impact View per Component

Guilin Release Requirements

Guilin release - non-functional requirements proposed list

New:

Guilin Exception Request for SO

Service Orchestrator Guilin Release M4

RC2 Criteria

Blocking issues :

License scan issues:

SO-3292: Issue with the license scan on the JBoss lib used in SOClosed

https://gerrit.onap.org/r/c/oom/+/111328

SO-3243: SO-bpmn-infra Container after Java 11 upgrade encountering SunCertPathBuilder Exception: unable to find valid certification path to requested target in CSITClosed

SO committer promotion:

Service Orchestrator

Way forward for Honolulu:

Open

What went wrong:

1. Communication with OOM was not effective

2. OOM delays impacted SO feature delivery delays

3. • Master branch was not stable because a lot of features and Java 11 upgrade and certificate issues

4. • Some testing required additional OOM changes

5. • OOM best practices were not broadcasted to the feature teams

6. • Security best practices / guidance came out in the middle/late of development cycle

7. • Image release number changed multiple times during the Guilin release

What was good:

1. The team could come out of the difficult time and meet the target

2. Response time from SO team was really good

3. In the end the issues were are fixed a release was fix.

What can be improved:

1. Reduced code fragments (new projects on the gerrit) for build

2. Introduce the gating as part of the jenkins verification process  (2 edged sword to deal with, work with the details).

3. Increase in auto verification

4. • OOM best practices / guidance should come earlier and documented