This page captures details about the non-functional requirements contributed to by the use case team, based on the TSC directive for Guilin.
Note: Apart from the list provided below, the 2 new MS to be introduced in DCAE (DES and Slice Analysis MS) shall comply with the relevant non-functional requirements for Guilin release.
Component | Jira | Requirement reference | Company | Name | Description | |
---|---|---|---|---|---|---|
DCAE | CMCC | No root (superuser) access to database from application container for PM Mapper MS & DL-feeder | ||||
DCAE | LTTS | narayanasetty.sowmya@Ltts.com | ||||
ExtAPI | Wipro | priyadharshini.b96@wipro.com | Upgrade vulnerable outdated direct dependencies per SECCOM recommendations | |||
ExtAPI |
-
EXTAPI-466Getting issue details...
STATUS
| Wipro | priyadharshini.b96@wipro.com | Containers must crash properly when a failure occurs. | ||
OOF | Huawei | Upgrade Vulnerable Direct Dependencies | ||||
OOF | Wipro | ONAP projects must use only approved and verified base images for their containers | ||||
OOF | Wipro | No root access to database from application container | ||||
OOF | Wipro | OOF to use cert initializers for certificates | ||||
SO | Wipro | Fix SO security vulnerabilities | ||||
SO | Wipro | No root (superuser) access to database from application container | ||||
SO | Tech Mahindra | ONAP project shall define code coverage improvements and achieve at least 55% code coverage | ||||
SO | Tech Mahindra | ONAP shall use STDOUT for logs collection |