/
Non-functional requirements contribution

Non-functional requirements contribution

This page captures details about the non-functional requirements contributed to by the use case team, based on the TSC directive for Guilin.



Component

Jira

Requirement reference

Company

Description

Component

Jira

Requirement reference

Company

Description

DCAE

DCAEGEN2-2284: SON-Handler java upgradeClosed

REQ-351: ONAP must complete update of the java language (from v8 -> v11) Done

Wipro

Upgrade of SON-Handler MS to Java 11

DCAE

DCAEGEN2-2278: remove son-handler vulnerabilitiesClosed

REQ-323: Each project will update the vulnerable direct dependencies in their code baseDone

Wipro

Remove SON-Handler vulnerabilities

DCAE

DCAEGEN2-2329: REQ-358 No root (superuser) access to database from application containerClosed

REQ-358: No root (superuser) access to database from application containerDone

Wipro

No root (superuser) access to database from application container for a couple of MS

OOF

OPTFRA-792: REQ-366 Container must crash properly when a failure occursClosed

REQ-366: Containers must crash properly when a failure occursTo Do

Wipro

Container must crash properly when a failure occurs

OOF

OPTFRA-794: REQ-365 All OOF containers must have only one process per containerClosed

REQ-365: Containers must have no more than one main processTo Do

Wipro

All OOF containers must have only one process per container



Related content

Service Orchestrator Guilin Release M1
Service Orchestrator Guilin Release M1
More like this
Usecase UI Guilin Release Planning
Usecase UI Guilin Release Planning
More like this
Guilin Release Requirements
Guilin Release Requirements
More like this
Usecase UI - Functional Test Cases
Usecase UI - Functional Test Cases
More like this
Use Case Realization Call: Oct 29, 2020
Use Case Realization Call: Oct 29, 2020
More like this
Project Status in Honolulu Release
Project Status in Honolulu Release
More like this