Hi Dan, I think the ask isn't for a standard interface, in terms of an API to all test engines, it's about having a standard format for the results input into the portal, so we don't have to update the portal every time new testing is being added to our programs (which is what Trevor is working on).
Cheers, Lincoln On Tue, Aug 6, 2019 at 11:58 PM <xuda...@huawei.com> wrote: > Hi Trevor, > > For your first point, Dovetail now supports running test cases by shell > commands besides Docker containers. Also we are considering to add an > option to call test cases by APIs provided by each project. Not sure if > these work for VVP. > > About the standard interface of the portal, I am not sure if it does need > this. The portal aims at compliance certification, so what's the point of > it to provide a standard interface to all test engines to upload the > results? If so, how can it control and ensure the credible of the results? > Maybe I missed some important info about this, please let me know if I do > miss something. > > Thanks, > Dan > > > -----Original Message----- > From: opnfv-tech-discuss@lists.opnfv.org [mailto: > opnfv-tech-discuss@lists.opnfv.org] On Behalf Of Trevor Lovett > Sent: Tuesday, August 06, 2019 9:53 PM > To: complia...@lists.lfnetworking.org; 'opnfv-tech-discuss@lists.opnfv.org' > <opnfv-tech-discuss@lists.opnfv.org> > Cc: Panagiotis Karalis <pkara...@intracom-telecom.com>; STARK, STEVEN < > ss8...@att.com>; WRIGHT, STEVEN A <sw3...@att.com> > Subject: Re: [opnfv-tech-discuss] [compliance] OVP VNF Upload Requirements > to OVP > > Thanks, Xudan. > > I posted on question on the wiki related to step 1. > > In the package testing, dovetail did not upload anything to the portal. > It was still a manual upload step. > > We based on recommendation not to use Dovetail on the following... > > 1) The Heat-based lifecycle tests are packaged with ONAP itself and reside > on a docker container. This means to invoke dovetail which in turn > launches another docker container (VVP), we'd need to allow a Docker in > Docker in Docker scenario. This is technically possible, but it is a > security concern as you need to pass the host docker daemon through the > stack of Docker containers. This was not something we felt comfortable > suggesting to the ONAP community. We'd likely need an alternate way to > invoke dovetail (i.e. cloning from source or true K8 pod/service that could > be invoked) > > 2) Since the lifecycle tests are already packaged with ONAP, we didn't see > much benefit in forcing users to install another component that was only > needed to repackage the results. > > 2) We likely would have needed additional updates to dovetail to parse the > new results which we felt wasn't really necessary if dovetail isn't driving > the tests. > > Our thinking was that there would be less moving pieces to setup, > integrate, and maintain if the portal published a standard interface for > the test engines to publish their results in. > > 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 | trevor.lov...@att.com > > -----Original Message----- > From: complia...@lists.lfnetworking.org [mailto: > complia...@lists.lfnetworking.org] On Behalf Of xuda...@huawei.com > Sent: Tuesday, August 06, 2019 2:20 AM > To: complia...@lists.lfnetworking.org; 'opnfv-tech-discuss@lists.opnfv.org' > <opnfv-tech-discuss@lists.opnfv.org> > Cc: Panagiotis Karalis <pkara...@intracom-telecom.com> > Subject: Re: [compliance] OVP VNF Upload Requirements to OVP > > 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://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_dovetail_Results-2BRequirements-2Bof-2BOVP-2BPortal&d=DwIFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=g9LhwjMTPM4AuoWvYyDmqA&m=x33AfCc9ro0KlUYmF5tImeQh4YjwxvT9zgRJcJzXGw0&s=oSiJJTMZThYPcPb7GpELcls2UGfByoK7dV9ib5pVBLk&e= > > > > -----Original Message----- > From: complia...@lists.lfnetworking.org [mailto: > complia...@lists.lfnetworking.org] On Behalf Of Trevor Lovett > Sent: Friday, July 26, 2019 5:29 AM > To: 'opnfv-tech-discuss@lists.opnfv.org' < > opnfv-tech-discuss@lists.opnfv.org>; complia...@lists.lfnetworking.org > Cc: STARK, STEVEN <ss8...@att.com>; WRIGHT, STEVEN A <sw3...@att.com> > 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://urldefense.proofpoint.com/v2/url?u=https-3A__vnf-2Dverified.lfnetworking.org_&d=DwIFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=g9LhwjMTPM4AuoWvYyDmqA&m=x33AfCc9ro0KlUYmF5tImeQh4YjwxvT9zgRJcJzXGw0&s=YCNQQI1BhOI_6vfcvOORWeB4Nd62vLwIxddnAjMvWMA&e= > > 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://urldefense.proofpoint.com/v2/url?u=https-3A__vnf-2Dverified.lfnetworking.org_&d=DwIFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=g9LhwjMTPM4AuoWvYyDmqA&m=x33AfCc9ro0KlUYmF5tImeQh4YjwxvT9zgRJcJzXGw0&s=YCNQQI1BhOI_6vfcvOORWeB4Nd62vLwIxddnAjMvWMA&e=) > 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 | trevor.lov...@att.com > > 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 (#304): > https://lists.lfnetworking.org/g/compliance/message/304 > Mute This Topic: https://lists.lfnetworking.org/mt/32779108/923460 > Group Owner: compliance+ow...@lists.lfnetworking.org > Unsubscribe: > https://lists.lfnetworking.org/g/compliance/leave/3707686/886985669/xyzzy > [lylav...@iol.unh.edu] > -=-=-=-=-=-=-=-=-=-=-=- > > -- *Lincoln Lavoie* Senior Engineer, Broadband Technologies 21 Madbury Rd., Ste. 100, Durham, NH 03824 lylav...@iol.unh.edu https://www.iol.unh.edu +1-603-674-2755 (m) <https://www.iol.unh.edu/>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23444): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23444 Mute This Topic: https://lists.opnfv.org/mt/32743003/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-