Mike has a conflict today, Prudence took notes.

Offline Installer:

Ingress Controller PoC


OOM staging branch

  • Gary Wu provided the context of the reason for OOM staging branch
  • this branch is to replace integration/version-manifest/src/main/resources/docker-manifest-staging.csv
  • the integration team uses this branch daily (stating today July 10, 2019) for the deployment in the integration lab
  • the master branch will only support released images
  • Answer to last week's question:
    • patches on staging branch can then be abandoned? No.  Since the master branch is only meant to have released images, the staging branch acts like our "old" master branch
  • Action: Gary Wuto update the wiki page which described the manifest to this new approach


Reduce ONAP footprint

  • Yang Xuran into memory issue again during testing.
  • would like to know that plan for this and would like to be involved in the future meetings regarding this topic
  • Any user stories created for this?


OOM charts to the project team

  • the team would like to know the plan for this in El Alto
  • Dan Timoney talked about it at the SDNC meeting today
  • Integration team would like to be included in the plan for El Alto


Venkata Harish Kajur reported his change for OOM-1936 - Getting issue details... STATUS (Helm chart generation) will be ready by this Friday.  


Attendees


  • No labels