Integration Team Deck presented on 5/26: https://wiki.onap.org/download/attachments/11930007/houston.pdf?version=2&modificationDate=1622039605578&api=v2
What does the ONAP TSC consider as minimum Integration scope to support the ONAP Community?
#1 Ensure that the Gating is up and running and daily results are available and identify any blocker by raising JIRA ticket
#2 Perform 72H stability test run on any ONAP Release package (final containers), provide report and identify any blocker by raising JIRA ticket
#3 Help to include in CI Chains any new automated test developed by the ONAP Use Case/Requirement Integration Lead
Other considerations:
SECCOM:
- Dev/Update of the security tests
- Update of the recommendations/waivers in the code (not in the wiki)
- Management of the baseline images
ONAP "Use Case/Requirement" Integration Lead is responsible of the testing of their current and previous use case(s), feature(s) and spec(s).
LF IT:
– Repository management (creation, INFO.yaml update, alias)
– Jenkins CI management (tools imposed by LF IT)
Release Manager:
- Weekly Gating results follow-up
- Release Candidate version tracking
- Create Integration Sign-Off Tasks