Agenda

  • Pomba / CLI /  holmes / sniro removal from all.yaml? As they are not part of the release
  • Smarter choice of Pods (example DCAE SDC pods only if DCAE is enabled)
  • HTTPs only services, proposition to change the template.
  • Reintegration of Robot chart. (https://gerrit.onap.org/r/c/oom/+/101605)
  • Status on Postgres Encoding Jira 


Refactoring service templates.md

Smarter choice of Pods in Helm Charts.md


  • No labels

3 Comments

  1. Mike Elliott

    • Need to resolve failed DCAE patches in gating due to AFF cert manager
      • if rebasing does not resolve need to raise at TSC as blocking DCAE from merging for quite some time
      • Sylvain Desbureaux assisting to help patches pass gating
    • Postgres Encoding
    • Removal of unsupported projects from OOM onap-all.yaml override file
      • Pomba / CLI /  holmes / sniro would remain in codebase, just not deployed by default and as part of Gating
      • Need confirmation projects are not being tested by integration team Morgan Richomme Brian Freeman
      • DCAE wondering if Holmes should also be removed from DCAE deployment or to reference El Alto versions of Holmes in Frankfurt
      • Would need to be vetted by TSC - Mike Elliott to add to TSC agenda for Feb 13, 2020
    • Provide smarter deployments based on configuration (i.e. global.aafEnabled)
      • allows us to deploy just what is needed
      • should be able to use existing helm dependency management
      • Mike Elliott raise Jira to perform PoC to understand if valuable
    • Refactor Service templates
      • TLS enablement is configurable
      • toggles HTTP vs HTTPs
      • HTTPs exposed via nodeport (for today)
      • HTTP does not expose node port but leverages ingress as best practice going forward
      • Sylvain Desbureaux discuss with SECCOM for approval
    • ROBOT support for HTTP or HTTPs
    • CIS testing

    1. Morgan Richomme

      I do confirm

      In frankfurt we moved from 61 to 46 healthcheck tests as we removed Pomba, logging, CLI, Holmes (no Go for frankfurt)

      for Sniro there is no dedicated healthcheck but it is used for oof-sniro I supposed - we did not remove this test as OOF is part of F release

      Sniro is a simulator.

      For the moment robot and sniro simulator are installed at the same time than the SUT. maybe we could split the 2 install onap onap-tooling - but probably too late for F.

      SECCOM conclusions on security priorities for F: Docker and Kubernetes Security

      CIS testing is already integrated for F, it is tested on each Daily and gating...but not fixed yet, and it will probably not possible for F but it would be good to reduce the nb of Errors.

      Integration meeting notes: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2020/onap-int.2020-02-12-14.00.html


  2. Sylvain Desbureaux

    OOM Meeting Notes - 2020-01-22