diff --git a/doc/source/contributor/index.rst b/doc/source/contributor/index.rst index d6274ec30..c6f7c46c2 100644 --- a/doc/source/contributor/index.rst +++ b/doc/source/contributor/index.rst @@ -61,10 +61,11 @@ traditional database scaling techniques. For sake of consistency and because there was initially intent to make the entities in the placement service available over RPC, -:oslo.versionedobjects-doc:`versioned objects <>` are used to provide the +:oslo.versionedobjects-doc:`versioned objects <>` were used to provide the interface between the HTTP application layer and the SQLAlchemy-driven -persistence layer. Even without RPC, these objects provide useful structuring -and separation of the code. +persistence layer. In the Stein release, that interface was refactored to +remove the use of versioned objects and split functionality into smaller +modules. Though the placement service does not aspire to be a `microservice` it does aspire to continue to be small and minimally complex. This means a relatively diff --git a/doc/source/contributor/testing.rst b/doc/source/contributor/testing.rst index 04575cef0..25f0d8211 100644 --- a/doc/source/contributor/testing.rst +++ b/doc/source/contributor/testing.rst @@ -18,8 +18,8 @@ Most of the handler code in the placement API is tested using `gabbi`_. Some utility code is tested with unit tests found in `placement/tests/unit`. The back-end objects are tested with a combination of unit and functional tests -found in ``placement/tests/unit/objects/test_resource_provider.py`` and -`placement/tests/functional/db`. +found in ``placement/tests/unit/objects`` and +``placement/tests/functional/db``. When writing tests for handler code (that is, the code found in ``placement/handlers``) a good rule of thumb is that if you feel like there