st implementation of Daas -
Destruction as a Service.
Martina
Do you think this would be an interesting evolution of destroystack, or
is that different enough in goals that we should think about this
problem separately.
-Sean
On 04/02/2014 08:55 AM, Martina Kollarova wrote:
Hi Sean
Hi Sean,
I'm already working on something similar. What I'm trying to do is not
a service, but a set of tests that would be able to run commands on the
nodes and restart services, kill disks, etc. The basic idea is to
inject some fault, see if everything still works as expected and
restore th
On Wed 18 Sep 2013 12:34:46 PM CEST, Kashyap Chamarthy wrote:
On 09/18/2013 03:37 PM, Martina Kollarova wrote:
There is a lack of design documentation and specification in the blueprints,
creating test
plans is problematic and requires a lot of communication with the developers. I
was
't support
formatting, but we can link them there.
Are there perhaps some better solutions for this? Would it be worth our
time to try this?
[1] https://github.com/mkollaro/openstack-testplans
Martina Kollarova
--
irc: mkollaro
___
OpenStack-d
Jenkins keeps running all the tests, even if the basic pep8 test fails,
and runs all of the (very slow) Tempest Quantum tests, even though
almost all of them are failing.
I propose that it should fail and stop all of the other tests once there
is a failure in a voting test. For non-voting test
