63f6adf68e
Following the decomposition of the core step on the 'direct' deploy interface, this change decomposed the iscsi and ansible deploy. Co-Authored-By: Dmitry Tantsur <dtantsur@protonmail.com> Change-Id: I537c6f6cf66c80b67b9045ea0618b02b7b93d36c Story: #2006963 Task: #40152
29 lines
1018 B
YAML
29 lines
1018 B
YAML
---
|
|
features:
|
|
- |
|
|
The ``deploy`` deploy step of the ``iscsi`` deploy interface has been
|
|
split into three deploy steps:
|
|
|
|
* ``deploy`` itself (priority 100) boots the deploy ramdisk
|
|
|
|
* ``write_image`` (priority 80) writes the image to the disk exposed
|
|
via iSCSI.
|
|
|
|
* ``prepare_instance_boot`` (priority 60) prepares the boot device and
|
|
writes the bootloader (if needed).
|
|
|
|
Priorities 81 to 99 to be used for in-band deploy steps that run before
|
|
the image is written. Priorities 61 to 79 can be used for in-band deploy
|
|
steps that modify the written image before the bootloader is installed.
|
|
- |
|
|
The ``deploy`` deploy step of the ``ansible`` deploy interface has been
|
|
split into two deploy steps:
|
|
|
|
* ``deploy`` itself (priority 100) boots the deploy ramdisk
|
|
|
|
* ``write_image`` (priority 80) writes the image to the disk and configures
|
|
the bootloader.
|
|
|
|
Priorities 81 to 99 to be used for in-band deploy steps that run before
|
|
the image is written.
|