Agenda

  • Mike out today - James MacNider and Michael O'Brien are running the meeting
  • Helm Chart ownership transfer progress (OOM-1240)
    • Agreed at PTL meeting this week - will work with James Forsyth and A&AI team to transfer AAI Helm Charts out of OOM repo and into A&AI oom repo (POC)
    • Met with LF to work through 
      • creation of OOM subrepos per project (Jira being raised to track)
      • updated build process to build dockers and helm charts as one unit
    • Helm Chart versioning for traceability (timestamped: 4.0.0-201901291200)
    • Work with Gary Wuto migrate away from Integration Manifests and towards OOM overrides
      • possible introduction of new Helm plugin to scrape all docker versions from Helm Charts and optionally audit images against Nexus
  • Dublin Release 4.0.0 - Dublin Sprint 1


  • No labels

2 Comments

  1. Michael O'Brien

    gerrit reviews -  CIMAN-217 - Getting issue details... STATUS

    arm -  CIMAN-217 - Getting issue details... STATUS

    Q) 3.0.0-ONAP tag - for friday 3.0.1-ONAP will available - via integration team sign off

    3.0.0 failures (appc, dmaap, aai)  

    see for known issues (3.0.0, 3.0.1, dublin  TSC-92 - Getting issue details... STATUS

    TSC-101 - Getting issue details... STATUS


    Q) adding committers

    I will paste Mike's page for committer template - he sends out a vote to all committer,  Mike sends the results to the LF

    follow/copy  and re-fill out james template for each dev OOM


    Q) Connor dmaap. - Mariadb timings up - dr not mr - more intermittent on aws - based on sequential timing

    check internal dependency init containers that dr-db is below the other 2 drs for

    DMAAP-1010 - Getting issue details... STATUS

    re-review https://gerrit.onap.org/r/#/c/75974/ in terms of numbers for dublin

    Log Streaming Compliance and API#DeploymentDependencyTree-Containerlevel


    Q) on blocking  OOM-1572 - Getting issue details... STATUS  for dcae and dmaap work at the 5g edge - Dominic Lunanuova - need status on the work - Mike Elliott

    Q) docker manifest as source of truth?

    TSC-86 - Getting issue details... STATUS

    follow https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/onap-oom-heat.html?highlight=manifest%20csv

    Gary Wu plan is to remove the manifest csv and make oom chart values.yaml the truth. - double commits to oom/integration for now.  plan is to have 2 oom branches (release/staging) - created early in the dev cycle

    need to still do validation on the manifest that they are in nexus3 (future dockerhub) - need a validation script to verify the images - OOM-328 for example - double duty - as prepull and verify script on the images - rest check to nexus3 needs to be the priority -  check without actually pulling.

    OOM/Integration team work together - but out of band commits need to be managed  - enforce the process

    integration team needs committer access to the values.yaml changes in the branches above - or a tight loop on the actual values.yaml merge

    @Nicolas Jun Hu - handling staging/release image tags in oom (as yaml override?) - PTLs could release earlier so we can use the non-STAGING tag.

    Todo: discuss earlier docker image release tag process - not just at RC0-3

    Or use a secondary nexus3 or docker hub repo for the dev images https://hub.docker.com/u/onap


    TODO: Master stability best practices discussion - continue for next meet to come up with details


  2. Michael O'Brien

    make a note to close off one of the 2 sprints https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&projectKey=OOM