On 1 May 2015 at 05:39, Sean Dague <s...@dague.net> wrote: > On 04/30/2015 12:53 PM, Matt Riedemann wrote: > <snip> >> Yeah why would you not include admin tests? Like listing services and >> hosts in nova? > > It is extremely easy to say "why not include *, it's valid function" and > we're going to end up with an hour long smoke test. > > At some point, you have to cut. Nova... can you boot a server, cool. Can > it get on the network? Glance, can I feed you an image and it looks like > it works. Great. Keystone, you do something with users right, can I add one? > > There are so many features in OpenStack that we need to be aggressive on > keeping this paired down. > > My thought is Smoke is not intended to be validation your cloud is > working. It's validation that the cloud isn't a giant pile of fail. It > might be a medium pile of fail, but some basic ops are working, so > that's cool.
+1 That said, I think having *a* admin call is worthwhile in smoke, because that (privileges working) is a good representative example of the broad ways in which things could be systemically broken. But it needed be explicit: If admin calls are implicit in setting up user tests, that would be more than sufficient IMO. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
