Functionality related to deploying and undeploying.
Continue deployment after finishing an async deploy step.
This function calculates which step has to run next and passes control into do_next_deploy_step. On the first run, deploy steps and templates are also validated.
task – a TaskManager instance with an exclusive lock
Do deployment, starting from the specified deploy step.
task – a TaskManager instance with an exclusive lock
step_index – The first deploy step in the list to execute. This is the index (from 0) into the list of deploy steps in the node’s driver_internal_info[‘deploy_steps’]. Is None if there are no steps to execute.
Prepare the environment and deploy a node.
Execute a requested step against a child node.
task – The TaskManager object for the parent node.
step – The requested step to be executed.
None on Success, the resulting error message if a failure has occured.
Start deployment or rebuilding on a node.
This function does not check the node suitability for deployment, it’s left up to the caller.
task – a TaskManager instance.
manager – a ConductorManager to run tasks on.
configdrive – a configdrive, if requested.
event – event to process: deploy or rebuild.
deploy_steps – Optional deploy steps.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.