diff options
author | Jenkins <jenkins@review.openstack.org> | 2015-09-24 19:31:42 +0000 |
---|---|---|
committer | Gerrit Code Review <review@openstack.org> | 2015-09-24 19:31:42 +0000 |
commit | 21b83107a637fa1c1cd2737f2ed64ec5072865dc (patch) | |
tree | e5a8163161e1b1f79885e0810a287491eb8e0476 | |
parent | 073ab02477daf039dec17adcc6775dbb843d6225 (diff) | |
parent | 3081eb0a92553598f3d818df6c7e42760a14e93a (diff) | |
download | ironic-21b83107a637fa1c1cd2737f2ed64ec5072865dc.tar.gz |
Merge "Update architecture docs to mention new driver interfaces"
-rw-r--r-- | doc/source/dev/architecture.rst | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/source/dev/architecture.rst b/doc/source/dev/architecture.rst index 46aebfa81..351df2626 100644 --- a/doc/source/dev/architecture.rst +++ b/doc/source/dev/architecture.rst @@ -64,12 +64,13 @@ There are three categories of driver interfaces: Ironic's API. If a driver implements this interface, it must adhere to the standard. This is presented to encourage vendors to work together with the Ironic project and implement common features in a consistent way, thus - reducing the burden on consumers of the API. - The Standard interfaces are `management` and `console`. + reducing the burden on consumers of the API. The Standard interfaces are + `management`, `console`, `boot`, `inspect`, and `raid`. - The `Vendor` interface allows an exemption to the API contract when a vendor wishes to expose unique functionality provided by their hardware and is - unable to do so within the `core` or `standard` interfaces. In this case, Ironic - will merely relay the message from the API service to the appropriate driver. + unable to do so within the `Core` or `Standard` interfaces. In this case, + Ironic will merely relay the message from the API service to the appropriate + driver. Driver-Specific Periodic Tasks ------------------------------ |