2a6b5c14d5
This change decomposes the current deploy step of the direct deploy into multiple deploy steps: * deploy (priority 100) * write_image (priority 80) * prepare_instance_boot (priority 60) Note that this patch breaks backwards compatibility with 3rd party drivers that inherit AgentDeploy rather than the base agent class. Co-Authored-By: Dmitry Tantsur <dtantsur@protonmail.com> Change-Id: Ief586473aca0e22b74efe83ef70c354fd5df17bf Story: 2006963 Task: 37778
18 lines
661 B
YAML
18 lines
661 B
YAML
---
|
|
features:
|
|
- |
|
|
The ``deploy`` deploy step of the ``direct`` deploy interface has been
|
|
split into three deploy steps:
|
|
|
|
* ``deploy`` itself (priority 100) boots the deploy ramdisk
|
|
|
|
* ``write_image`` (priority 80) downloads the user image from inside
|
|
the ramdisk and writes it to the disk.
|
|
|
|
* ``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.
|