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
Some developers can create a branch themselves - if you see a "create branch" button
https://gerrit.onap.org/r/#/admin/projects/oom,branches
Follow up with david to create branch for beijing
new sprint with David
break the tarball news: Mandeep: auto-updating config
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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 OOM-344
Roger, David, We need to declare OOM and HEAT ready for release at the same time
We will need to test both systems within the same 24 hour period
Since monday - only changes to fix the vFW are allowed to be merged - so theoretically we should
Need wiki for F2F - link to
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Review Carrier grade page
Comply to RC2 - David
Vote to make Borislav and official committer