Open Stack

Greg,
For compliance it is sufficient to run https://refstack.openstack.org/#/guidelines.
But it is good if you can also submit fill Tempest run.
That is used internally by refstack to identify which tests to include in the future.
This can be submitted anonymously if you like.
Thanks,
Arkady

From: Waines, Greg [mailto:Greg.Waines at windriver.com]
Sent: Thursday, March 15, 2018 9:05 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests

Re-posting this question to ‘OPENSTACK REFSTACK’,
Any guidance on what level of compliance is required to qualify for the OpenStack Logo ( https://www.openstack.org/brand/interop/ ),
See questions below.

Greg.

From: Greg Waines <Greg.Waines at windriver.com<mailto:Greg.Waines at windriver.com>>
Date: Monday, February 26, 2018 at 6:22 PM
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests


I have a commercial OpenStack product that I would like to claim compliancy with RefStack
·         Is it sufficient to claim compliance with only the “OpenStack Powered Platform” TESTS ?
o    i.e. https://refstack.openstack.org/#/guidelines
o    i.e. the ~350-ish compute + object-storage tests
·         OR
·         Should I be using the COMPLETE API Test Set ?
o    i.e. the > 1,000 tests from various domains that get run if you do not specify a test-list

Greg.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180315/6eebd525/attachment.html>