Agenda

• AAI shrink continuation: @Sylvain Desbureaux

  • removal of r/f/t proxies

  • automatic certificates retrieval

    • AAI: done

    • AAI Resources: ongoing: https://gerrit.onap.org/r/c/oom/+/116386

    • AAI Traversal: not started

    • AAI Sparky BE: not started

  • removal of components

    • data router

    • elasticsearch

    • search data

• Certificates in Guilin and Master: @Sylvain Desbureaux

  • certificates with early expiration date, move to automatic certificate generation:

    • AAI: merged

    • music: https://gerrit.onap.org/r/c/oom/+/117540 (merged)

    • aai sparky be (will be done after AAI Resources)

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

    • message router: https://gerrit.onap.org/r/c/oom/+/117674

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

  • what do we do for Guilin?

    "cherry pick" the automatic retrieval

    put regenerated hardcoded certificates

    first regenerate hardcoded certs (7.0.1) and in a second time push automated cert retrieval in end of branch

• Work in how to productize ONAP: Patrik Romsak (DT)

  • deployment per component

    • rationale:

      • smooth the deployment

      • simplify replacement of one component by home grown one

      • simplify upgrade

    • how it's done:

      • in DT gitlab

      • gitlab is used as helm repo ("chart creation" is done via gitlab ci)

      • able to deploy a component only (but knowledge of require

      • d components for a specific component is needed)

        • some dependencies are "hidden"

          • certWrapper

          • repositoryGenerator

      • all is done via gitlab ci pipeline

      • k8s is deployed via RKE

      • PaaS components:

        • Traefik (Ingress)

        • Prometheus (prometheus operator)

          • any specific metrics used (@Marat Salakhutdinov )? → basic one for K8S for now

          • integration team (@Morgan Richomme and @Natacha Chéreau  are also desperately looking for metrics  )

        • Elasticsearch (via another k8s cluster)

  • main issue: upgradability (@Marat Salakhutdinov )

    • first on component

    • then (or in // ) in OOM

• Dual stack (ipv4/ipv6) CI in Nokia and how to push to community:  @Daniel Milaszkiewicz

  • almost finished the CI

  • needed to be done: publish the results in the community

    • database for results: http://testresults.opnfv.org/onap/api/v1/results

      • done

    • pushing results to logs.onap.org: let's start a discussion with @Morgan Richomme & LF IT in order to provider access.

• helm release: @Sylvain Desbureaux

  • helm repo in nexus: work done on jenkins side. Just need to trigger

  • next steps:

    • be sure doc is OK

    • be sure we can have several versions in //