ONAP projects must use only approved and verified base images for their containers
Description
50% Done
blocks
clones
is blocked by
is duplicated by
relates to
Activity
Show:
Former user December 1, 2020 at 7:27 PM
"Req or Use Case" = "Non-Functional Requirement" has been deprecated. Please update this issue.
See this email for details: https://lists.onap.org/g/onap-requirements-sub/message/1844
Former user October 19, 2020 at 1:35 PM
- suggest changing status to yellow. Update scope to "reduced scope". Repeat for Honolulu.
Former user October 19, 2020 at 7:45 AM
Full distros still used as base images
Former user October 12, 2020 at 6:46 PM
Please complete the RC0 scorecard for this issue.
Former user September 18, 2020 at 8:44 PM
The TSC approved to continue this requirement as part of the Guilin Release.
This decision will be reviewed at RC0 depending on the progress.
— TSC M4 Approval : GO —
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Requirement Type
Best Practice (new code only)Fix versions
Priority
HighEpic Name
ONAP Requirements Template
Details
Details
Assignee
Former userReporter
Former userRequirement Type
Best Practice (new code only)
Fix versions
Priority
HighEpic Name
ONAP Requirements Template
Created May 27, 2020 at 6:41 PM
Updated January 10, 2021 at 4:59 PM
Description of Use Case / Requirement:
We are shipping container images as our official release artifacts. We need to make sure that we comply with all licenses used in base images. This infeasible when projects use dozen of different base images.
Owners (one of these should be the Assignee - use @ notation):
Link to HLD/LLD (if any):
Dependency Relationships with Other Projects:
Project Impact (Test Only (TO), Code (C)):
Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.
Integration Leads (use @ notation):
Company Engagement: