From 3081eb0a92553598f3d818df6c7e42760a14e93a Mon Sep 17 00:00:00 2001 From: Lilia Sampaio Date: Thu, 24 Sep 2015 15:14:49 +0000 Subject: [PATCH] Update architecture docs to mention new driver interfaces This patch updates the architecture documentation to include mentions of the new Boot and RAID driver interfaces. It also adds the Inspect interface, which we apparently forgot in the past. Change-Id: I2d3319ca82d3fe56df9dd294968344f53cf7ff90 --- doc/source/dev/architecture.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/source/dev/architecture.rst b/doc/source/dev/architecture.rst index 46aebfa81d..351df2626b 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 ------------------------------