Agenda

• DMaaP Strimzi PoC: @Fiachra Corcoran 

  • arch comittee link: ONAPARC-719: (ARC-PROPOSAL) - Simplify Kafka-based DMaaP configuration and enhance its security and integration Open 

  • poc: https://gerrit.onap.org/r/c/oom/+/123690

  • chart link: https://strimzi.io/charts/

  • current situation

    • DMaaP is old and not maintained for a while

    • Hidden dependencies

    • Hard to move to Java 11

  • proposal:

    • move to Strimzi (CNCF Sandbox)

      • using an operator

      • use "strimzi bridge" (equivalent to DMaaP MR but different REST Interface)

  • open questions

    • can we use an existing Kafka deployment?

      • yes!

    • can a publisher use strimzi and a subscriber dmaap MR ?

      • to be tested

    • same with counterpart?

      • to be tested

• Service Mesh: @Sylvain Desbureaux @Gareth Roper @Adrian Matthews Ondrej Frindrich

  • revamp of page: ONAP on Service Mesh

    • need to create CPS and DCAE Jira tickets

  • AAI: Ondrej Frindrich @Sylvain Desbureaux 

    • ready for review (https://gerrit.onap.org/r/c/oom/+/120964)

      • OK on Gate

      • OK on Orange with SM

      • NOK on Samsung without AAF

  • SDC: @Gareth Roper 

    • https://gerrit.onap.org/r/c/oom/+/122426

    • updated SDC to use latest patch of readiness

  • SO:

    • review pushed by end of week

  • CDS: @Othman Touijer 

    • started the work, still in exploratory phase

  • DCAE: @Gareth Roper Andrew Lamb

    • start of work done, lots of ms to update

    • postgresql to check

  • CPS: @Gareth Roper 

    • start to look at, looks simple to onboard

    • postgresql to check

  • QuitQuit Sidecar: @Gareth Roper 

    • Patchset provided: https://gerrit.onap.org/r/c/oom/readiness/+/123739

    • comments from @Sylvain Desbureaux 

      • try to use a single file

      • allow configuration of "quitquitquit" url

    • @Gareth Roper updated the patch

    • next steps:

      • @Sylvain Desbureaux and @Krzysztof Opasiak to review

      • if OK merge + release (4.0 I think)

  • testing part:

    • "unofficial gate" is used (https://gitlab.com/Orange-OpenSource/lfn/ci_cd/chained-ci/-/blob/master/pod_inventory/host_vars/onap_oom_pod4_sm_master.yml)

    • samsung community daily deployment work is ongoing

• SO Ingress TLS: @Sylvain Desbureaux 

  • https://gerrit.onap.org/r/c/oom/+/114236

  • patch updated today

• Outstanding patches

• Push helm charts: @Jessica Gonzalez @Sylvain Desbureaux 

  • testing part seems OK (https://nexus3.onap.org/#browse/browse:onap-helm-testing) →  @Sylvain Desbureaux to test

  • release part: wait for SO/CDS patch on Honolulu MR and should be good to try a "release"

• Gitlab migration: @Bengt Thuree (Unlicensed) @Jessica Gonzalez @Krzysztof Opasiak 

  • mirrorring of one repo is done (one branch only) as a temporary solution

  • CLA enforcement script PoC is done

  • JIRA tickets:

    • RELENG-3871 : Requirements Gathering - Done

    • RELENG-3920 : Create OOM namespace under LFN ONAP - Done

    • RELENG-3921 : Restrict merge requests creation to OOM commiters only

    • RELENG-3922 : Create oom repositories as they are in gerrit - Done

    • RELENG-3923 : Setup repo mirroring from gerrit to gitlab

    • RELENG-3924 : Add CI job definitions via gerrit ← Once it's done, we can move the script for CLA enforcement

    • RELENG-3925 : Step by step start locking oom repos in gerrit and unlocking them in

• M4:

  • needs to do the "M4" Jira tickets

    • no new repositories to add on documentation for OOM (and OSA)