Over the weekend I spent some time working on my experiments using
gabbi[1] with tempest. I had previously got gabbi-tempest[2]
working, based on some work by sileht, but it was only addressing a
single service at a time. For the sake of placement-related tests,
it's useful to be able to talk to the compute api and the placement
api at the same time. Now it does.
I've just now used it to confirm a placement bug [3] with this gabbi
file:
https://github.com/cdent/gabbi-tempest/blob/master/gabbi_tempest/tests/scenario/gabbits/multi/base.yaml
It's still rough around the edges, but it has proven useful and
should be doubly so in the face of multiple nodes. Especially useful
to me is how visible it makes the various APIs and the interactions
thereof. Writing the tests without a client is _very_ informative.
If you'd like to help make it better, find me or just go ahead and
make a pull request. At some point it may be interesting to explore
the option of "put a gabbit in dir X" and tempest will run it for
you.
[1] https://gabbi.readthedocs.io/en/latest/
[2] https://github.com/cdent/gabbi-tempest
[3] https://bugs.launchpad.net/nova/+bug/1707252
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
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
