Hi Trevor, I have created a wiki page [1] to give some description about the results format for OVP Portal. Hope it helps. Also Panos may help to update it because he is more familiar with the source code of the portal.
BTW, I still suggest to use Dovetail to get this file and then upload it to the portal because the portal is binding with Dovetail. Could you give some more details about why can't use Dovetail this time? The Dovetail team are very glad to work together with you to try to solve this problem. Thanks, Dan [1] https://wiki.opnfv.org/display/dovetail/Results+Requirements+of+OVP+Portal -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Lovett Sent: Friday, July 26, 2019 5:29 AM To: '[email protected]' <[email protected]>; [email protected] Cc: STARK, STEVEN <[email protected]>; WRIGHT, STEVEN A <[email protected]> Subject: [compliance] OVP VNF Upload Requirements to OVP We are working on the next stage of VNF validations in ONAP and focusing on onboarding and instantiation. We previously used dovetail and tar'ed up the log files to be uploaded to https://vnf-verified.lfnetworking.org/ We can't use Dovetail this time to drive the tests as the tests will be driven by the ONAP integration/testsuite Robot scripts. We'd like to understand what the OVP portal (https://vnf-verified.lfnetworking.org/) expects in terms of the tar.gz file that will be uploaded. Are there specific files that are parsed for information or will any arbitrary tar.gz file work? This is a rough proposal of how the directory will be structured: result.json (new - summarizes the overall outcome and pass/fail of the macro steps) onap-vvp-logs/ (existing - package validation results) report.json (existing - VVP output report) onap-instantiation-logs (new - onboarding and instantiation results) stack-validation-report.html (compares instantiated VNF against Heat and Preload) robot-test-results.html (details the individual test steps and their results) log.html (detailed logs generated by robot during test setup and execution) We would appreciate any feedback on the directory structure so that we can produce something compatible with OVP. If there are specific data elements that need to be parsed out of the results can you please provide details on how they should be formatted? If needed we can tee this up for the weekly CVC meeting to discuss in more detail. Thanks, Trevor Lovett Lead Member of Technical Staff AT&T Labs, Operational Automation and Program Management AT&T Services, Inc. Dallas, TX m 314.401.8702 | [email protected] This email and any attachments are confidential AT&T property intended solely for the recipients. If you received this message in error, please notify me and immediately delete this message from your computer. Any retention, distribution, or other use of this email is strictly prohibited. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#295): https://lists.lfnetworking.org/g/compliance/message/295 Mute This Topic: https://lists.lfnetworking.org/mt/32603497/944374 Group Owner: [email protected] Unsubscribe: https://lists.lfnetworking.org/g/compliance/leave/2134106/1698490046/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23439): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23439 Mute This Topic: https://lists.opnfv.org/mt/32645679/21656 Group Owner: [email protected] Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
