On Tuesday, 26 July 2016 13:23:05 CEST Hayes, Graham wrote: > On 26/07/2016 14:18, Doug Hellmann wrote:
> >>> And just to satisfy my own curiosity, how does someone looking at the > >>> internals of tempest know what's on the stable API and what's not > >>> considered stable? Are the parts of the API documented separately > >>> somehow or is there a different part of the code tree to look at? > >> > >> tempest.lib is the stable part (previously split in a separate > >> tempest-lib > >> repository, which is now deprecated as the code was put back into the > >> main > >> tempest repository): > >> http://docs.openstack.org/developer/tempest/overview.html#library > > > > That seems quite clear, thanks. > > it is actually a bit more - > > http://docs.openstack.org/developer/tempest/plugin.html This is the documentation on how plugins should be implemented, i.e. how the plugin code can consume the stable API described above. It's really a bit of boilerplate about the custom configuration options and the registration of the classes. -- Luigi __________________________________________________________________________ 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
