 REQ-340 - ONAP to support Multi - tenancy To Do
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-340 |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| |
REQ-374 - ONAP shall use STDOUT for logs collection To Do | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-374 |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| Pattern of the logging to be standardized. Append the log4j with the appender ( on OOM). | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SO-3077 |
|---|
|
|
REQ-369 - Replace nfs share with storage class as a default deployment option To Do | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-369 |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| Gating and daily deployment impact... (Deployment scripts) |
REQ-364 - Replace NodePorts with ingress controller as a default deployment option To Do | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-364 |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| 30227 and 20225 should be Robot Pod Refactoring (Oom based) | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SO-3078 |
|---|
|
|
REQ-360 - Application config should be fully prepared before starting the application container To Do | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = SDC AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-360 |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| spring boot based application should be ok, will need to re-check with Kryzstof (Oom based) |
Image ModifiedREQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. To Do | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-350 |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| CII badging improvement - Contributors : ?
- Seshu Kumar Mudiganti
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SO-3079 |
|---|
|
|
REQ-359 - Container rootfs must be mounted readOnly To Do | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,updated,assignee,priority,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = SO AND issuetype in (Epic, Story, Task, bug) AND "Epic Link" = REQ-359 |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| Springboot startup should take care of this, need to check with Kryzstof. (Oom based) |