Open Stack

I just want to raise a quick concern here about tests cleaning up
after themselves - as it currently stands, running the refstack client
against one of our clusters results in dozens of routers, networks,
subnets, ports, etc all being left behind when the tenants created by
tempest are deleted.

We've got some code to do cleanup for all of these resources after a
tempest run, but I'm wary of needing to do even more cleanup for other
tests in each project.

On Thu, Feb 26, 2015 at 12:39 PM, Van Lindberg
<van.lindberg at rackspace.com> wrote:
> Hi John,
>
> I have been looking at ways to expand the test suite too, and I am glad to see these. I would suggest that we adopt the same sort of process that we are proposing for the capabilities themselves:
>
> - Spec release N would include new "advisory" tests
> - Spec release N+1 would include the tests as "mandatory" unless there was some problem identified.
>
> I'm also a little worried about the overloading of tempest and wanting to make the tools slightly more standalone.
>
> What do you think?
>
> - Van
>
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee