...
M1 release planning - discuss thu LOG R2 M1 Beijing Release Planning
M1 maturity
Logging RI Work assignment - see structure and
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | LOG-118 |
|---|
|
,
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | LOG-111 |
|---|
|
...
Config TPL changes in OOM affecting logging including
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | LOG-129 |
|---|
|
simplify
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| 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 Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | OOM-460 |
|---|
|
How the new helm work (get JIRA) affects logging (config distribution and management?)
Notes