...
M1 release planning - discuss thu LOG R2 M1 Beijing Release Planning
M1 maturity
Logging RI Work assignment - see structure and
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-118 |
---|
|
,
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-111 |
---|
|
...
Config TPL changes in OOM affecting logging including
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-129 |
---|
|
simplify
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-129 |
---|
|
OOM meet questions: Logging config (need jira) separate or combined (talk with Borislav Glozman - including the other work for the config pod splitting in
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | OOM-460 |
---|
|
How the new helm work (get JIRA) affects logging (config distribution and management?)
Notes