e1a0864635
While the prior sevice steps patch had a huge portion of the needed code already due to copy-pasta, this change finishes wiring in the ability for the agent to be launched for service steps and heartbeat to occur, combined with support to retrieve service steps from the running agent, ultimately to enable operators to take a deployed node, and ask Ironic to make changes, or my more favorite use case, go benchmark it for a while. Also edits the service steps release note to remove the outstanding issue, and makes some minor corrections in the code which was copied but didn't quite have testing wired up yet. Change-Id: Ibfe42037b520a76539234cf1a5e19afd335ce8a8
15 lines
723 B
YAML
15 lines
723 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds a new Ironic capability called ``service_steps`` which allows a
|
|
deployed ``ACTIVE`` node to be modified utilizing a new API provision
|
|
state verb of ``service`` which can include a list of ``service_steps``
|
|
to be performed. This work is inspired by ``clean_steps`` and
|
|
``deploy_steps`` and similar to those efforts, this functionality will
|
|
continue to evolve as new features, functionality, and capabilities
|
|
are added.
|
|
- Adds a new driver method decorator ``base.service_step`` which operates
|
|
exactly like the existing ``base.clean_step`` and ``base.deploy_step``
|
|
decorators. Driver methods which are decorated *can* be invoked utilizing
|
|
the service steps.
|