We used Tempest for a time against our production environment. It was a pain to clean up but ephemeral test jobs solves that for you. A few questions: What version of tempest will be using? Will we maintain a blacklist if there are known failures? (although this is a pain to keep updated) On Sun, Jul 12, 2015 at 8:44 PM, Emilien Macchi <emilien.macchi at gmail.com> wrote: > Hi, > > I would like to propose to run Tempest at the end of the beaker jobs, for > testing purpose now. > > As a start, we would accept 0 & 1 as return code, because this is really > experimental. > Though I think it will be interesting to see how it behaves, specially > when we implement new configurations or plugins in our modules. > > I already did a PoC for puppet-keystone: > https://review.openstack.org/198561 > (failing because it needs more work to pass keystone v3 tests but v2 tests > are successful). > As you can see the code is really light, since we use puppet-tempest. > > Any suggestion is welcome ! > > -- > Emilien Macchi > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150712/a18a2218/attachment.html>