Open Stack

Thanks for the clarification.  Yeah.  No interop interaction  to see here.  These are not the api's you are looking for;-)

I think Chris Dent's response  about extending the gabbi based tests is great.  

I'm a firm believer in never discouraging anyone from writing more tests, especially when current coverage isn't complete.  But that doesn't mean I want them in the gate.  But also, since developers gain a lot of understanding through reading code, the test code itself could help devs better understand the extent and limitations of the placement api's.  Or not.

I just can't keep from encouraging devs to write tests.

--Rocky
 
> From: Sean Dague [mailto:sean at dague.net]
> On 06/22/2017 01:22 PM, Matt Riedemann wrote:
> <snip>
> > Rocky, we have tests, we just don't have API samples for documentation
> > purposes like in the compute API reference docs.
> >
> > This doesn't have anything to do with interop guidelines, and it
> > wouldn't, since the Placement APIs are all admin-only and interop is
> > strictly about non-admin APIs.
> 
> I think the other important thing to remember is that the consumers of the
> placement api are currently presumed to be other OpenStack projects.
> Definitely not end users. So the documentation priority of providing lots of
> examples so that people don't need to look at source code is not as high.
> 
> I'm firmly in the camp that sample request / response is a good thing, but
> from a priorities perspective it's way more important to get that on end user
> APIs than quasi internal ones.
> 
> 	-Sean
> 
> --
> Sean Dague
> http://dague.net
> 
> __________________________________________________________
> ________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev