Open Stack

Michael, I just wanted to make sure I understood your concern here…

These changes may cause an influx of tests, but from the DefCore perspective it’s still the set of tests that have been “blessed” that determine compliance, correct?  I realize the full set will get run, but it’s still a board+TC set of criteria that determine which tests are blessed.

So, other than possible overload in terms of getting new tempest tests created (not necessarily a bad thing), there isn’t any other issue here, I think?


Thanks,


--Randy

Founder & CEO, Cloudscaling
Board of Directors, OpenStack Foundation
+1 (415) 787-2253 [SMS or voice] 
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
CALENDAR: doodle.com/randybias









On Mar 20, 2014, at 4:01 PM, Michael Still <mikal at stillhq.com> wrote:

> Heya,
> 
> this came up in the defcore meeting today and I want to specifically
> call it out for your attention.
> 
> The lever that the defcore committee is using for compliance testing
> is tempest. There is a likelihood that telling vendors that their
> thing can only be defcore compliant if its tested with tempest will
> result in an increase in the number of tempest submissions, probably
> between the Icehouse release and about 90 days after.
> 
> Do you have any concerns with this I should be aware of?
> 
> Thanks,
> Michael
> 
> -- 
> Rackspace Australia
> 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140320/36402ef6/attachment.html>