Re: [openstack-dev] [nova] determining or clarifying a path for gabbi+nova

2016-05-25 Thread Chris Dent
On Wed, 25 May 2016, Sean Dague wrote: I still would rather not put gabbi into the compute API testing this cycle. Instead learn from the placement side, let people see good patterns there, and not confuse contributors with multiple ways to test things in the compute API. Because that requires

Re: [openstack-dev] [nova] determining or clarifying a path for gabbi+nova

2016-05-25 Thread Sean Dague
On 05/25/2016 02:54 PM, Andrew Laski wrote: > > > On Wed, May 25, 2016, at 11:13 AM, Chris Dent wrote: >> >> Earlier this year I worked with jaypipes to compose a spec[1] for using >> gabbi[2] with nova. Summit rolled around and there were some legitimate >> concerns about the focus of the spec

Re: [openstack-dev] [nova] determining or clarifying a path for gabbi+nova

2016-05-25 Thread Chris Dent
On Wed, 25 May 2016, Andrew Laski wrote: After reading this my first thought is that gabbi would handle what I'm testing in https://review.openstack.org/#/c/263927/33/nova/tests/functional/wsgi/test_servers.py, or any of the other tests in that directory. Does that seem accurate? And what would

Re: [openstack-dev] [nova] determining or clarifying a path for gabbi+nova

2016-05-25 Thread Andrew Laski
On Wed, May 25, 2016, at 11:13 AM, Chris Dent wrote: > > Earlier this year I worked with jaypipes to compose a spec[1] for using > gabbi[2] with nova. Summit rolled around and there were some legitimate > concerns about the focus of the spec being geared towards replacing the > api sample