Non-functional requirements contribution in Guilin
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 | @LUKAI | No root (superuser) access to database from application container for PM Mapper MS & DL-feeder. Query sent to DCAE team, and awaiting feedback. | |||
DCAE | LTTS | @Narayanasetty Sowmya | ||||
DCAE | CMCC | @LUKAI | ||||
ExtAPI | Wipro | @Priyadharshini B | Upgrade vulnerable outdated direct dependencies per SECCOM recommendations | |||
ExtAPI | https://lf-onap.atlassian.net/browse/EXTAPI-466 | Wipro | @Priyadharshini B | Containers must crash properly when a failure occurs. | ||
OOF | Wipro | @krishna moorthy | Upgrade Vulnerable Direct Dependencies | |||
OOF | Wipro | ONAP projects must use only approved and verified base images for their containers | ||||
OOF | Wipro | @krishna moorthy | No root access to database from application container | |||
OOF | Wipro | @krishna moorthy | OOF to use cert initializers for certificates | |||
SO | Wipro | @Priyadharshini B | Fix SO security vulnerabilities | |||
SO | Wipro | @Reshmasree c | No root (superuser) access to database from application container. No action to be taken from our use case team for this Jira as discussed with SO PTL. | |||
SO | Tech Mahindra | @Former user (Deleted) | ONAP project shall define code coverage improvements and achieve at least 55% code coverage. No action required as of now (as long as coverage is > 55%). | |||
SO | Tech Mahindra | @Former user (Deleted) | ONAP shall use STDOUT for logs collection |