Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

VFC work needs to be assigned

OOM-372 assigned to FMO (OPNFV needs DCAEGEN2 working as well - will coordinate with David B. and Helen)

branching? new code for beijing should not be in master

Follow up with david to create branch for beijing

new sprint with David

break the tarball news: Mandeep: auto-updating config


OOM-344 - Getting issue details... STATUS

sharing k8s config map - pods must be in the same namespace - all of oom in single namespace - will block all configuration epics

This is a k8s restriction on config-maps not sharable outside the namespace

Introduce WIKI Design page for epics on design issues - like for example the shared config above that Mandeep is looking at


  • No labels