On 07/12/2015 11:29 PM, Matt Fischer wrote:
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?
master for now. We will see if new tags are created
On Mon, Jul 13, 2015 at 07:50:59AM -0400, Emilien Macchi wrote:
On 07/12/2015 11:29 PM, Matt Fischer wrote:
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
On Sun, Jul 12, 2015 at 09:29:57PM -0600, Matt Fischer wrote:
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
Just curious how long ago was this? Because resource leaks have always been
My tempest experience is dated to Havana, so I'll consider it to be
completely out of date. Glad to he about all these improvements.
On Jul 13, 2015 2:12 PM, Matthew Treinish mtrein...@kortar.org wrote:
On Sun, Jul 12, 2015 at 09:29:57PM -0600, Matt Fischer wrote:
We used Tempest for a time
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
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
