Merge "Document the custom-agent deploy interface"

doc/source/admin/interfaces/deploy.rst

@@ -133,3 +133,16 @@ Ramdisk deploy
 The ramdisk interface is intended to provide a mechanism to "deploy" an
 instance where the item to be deployed is in reality a ramdisk. It is
 documented separately, see :doc:`/admin/ramdisk-boot`.
+
+.. _custom-agent-deploy:
+
+Custom agent deploy
+===================
+
+The ``custom-agent`` deploy interface is designed for operators who want to
+completely orchestrate writing the instance image using
+:ironic-python-agent-doc:`in-band deploy steps from a custom agent image
+<admin/hardware_managers.html>`. If you use this deploy interface, you are
+responsible to provide all necessary deploy steps with priorities between
+61 and 99 (see :ref:`node-deployment-core-steps` for information on
+priorities).

doc/source/admin/node-deployment.rst

@@ -116,6 +116,13 @@ An example by passing a JSON string:
 Format of JSON for deploy steps argument is described in `Deploy step format`_
 section.
 
+Excluding the default steps
+---------------------------
+
+Starting with the Xena release, you can use the new :ref:`custom-agent-deploy`
+interface to exclude the default step ``write_image`` and skip bootloader
+installation in the ``prepare_instance_boot`` step.
+
 Writing a Deploy Step
 ---------------------