openstack/keystone
Code Issues Proposed changes

Dev doc update for moving abstract base classes out of core

Browse Source 
As part of an effort to remove backend dependencies on higher level
classes, this patch updates the dev docs, defining a standard as to
where abstract base classes are located and named.

Partial-Bug: #1563101

Change-Id: I784e344f333ee616bda800f63af0b1c149a529f3
This commit is contained in:
Ronald De Rose
2016-04-06 18:14:27 +00:00
parent dabf76f2cf
commit b316b14138
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/architecture.rst
+2 -1
View File
@@ -158,7 +158,8 @@ each service.
A general class exists under each backend to provide an
abstract base class for any implementations, identifying the expected service
implementations. The classes are named after the keystone release in which
implementations. The abstract base classes are stored in the service's backends
directory as ``base.py``. The classes are named after the keystone release in which
they were introduced. For eg. ``DriverV8`` for keystone release version 8.
The corresponding drivers for the services are: