OOM Meeting Notes - 2019-07-10
- Prudence Au
- Gary Wu
Mike has a conflict today, Prudence took notes.
Offline Installer:
@Michal Ptacek offline installer team finished the Dublin content and created Dublin branch. And currently working with Orange on the CI pipeline.
And waiting for the committer(s) approval. Action: @Mike ElliottDocumentation: https://docs.onap.org/en/dublin/submodules/oom/offline-installer.git/docs/index.html
Ingress Controller PoC
@Lucjan Bryndza, @Sylvain Desbureaux and @Borislav Glozman regarding the missing piece for patch https://gerrit.onap.org/r/c/oom/+/90608
automatic injection doesn't work yet, still being done manually. @Lucjan Bryndzato investigate further
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
DONE: @Gary Wu has updated El Alto instructions at Managing Container Image Tags.
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: Helm Chart GenerationClosed(Helm chart generation) will be ready by this Friday.
Attendees
