openstack/ironic
Code Issues Proposed changes

Add vendor step placement suggestion

Browse Source 
As discussed on irc[1], we felt the need to document the stance
on placement of vendor specific steps, in terms of what we as a
project would prefer to do and prefer to avoid.

[1]: http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2018-08-30.log.html#t2018-08-30T16:00:57

Change-Id: I795ac06a0c249697ed2f6d066dc46069c7e0f8ae
This commit is contained in:
Julia Kreger 2018-08-30 11:33:25 -07:00 committed by Dmitry Tantsur
parent 0a10eb7794
commit 199e490cbc
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/contributor/architecture.rst
View File

@ -55,6 +55,16 @@ decorator on an interface method. For example
Here the ``spacing`` argument is a period in seconds for a given periodic task. Here the ``spacing`` argument is a period in seconds for a given periodic task.
For example 'spacing=5' means every 5 seconds. For example 'spacing=5' means every 5 seconds.
Driver-Specific Steps
---------------------
Drivers may have specific steps that may need to be executed or offered to a
user to execute in order to perform specific configuration tasks.
These steps should ideally be located on the management interface to enable
consistent user experience of the hardware type. What should be avoided is
duplication of existing interfaces such as the deploy interface to enable
vendor specific cleaning or deployment steps.
Message Routing Message Routing
=============== ===============