Refactor tripleo update to offer the user more feedback and control.
The update process is a black box that offer no control to the user.
In particular the "overcloud update run" is one long playbook with
"steps". This makes it hard for the user to understand what is
happening. This is also an one off action. When it fails the user
has no choice but to start it all over again. To address both issues
we should give the user a semantic description of each step and offer
a way to restart the update process from any step.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Sofer Athlan-Guyot
- Direction:
- Needs approval
- Assignee:
- Sofer Athlan-Guyot
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Addressed by: https:/
Switch update to per step tasks.
Gerrit topic: https:/
Addressed by: https:/
Add a strict option to per role tasks file generation.
Addressed by: https:/
add update and post update tasks and a extra debug step.
Addressed by: https:/
Properly collect tasks with or conditional in step file.
Addressed by: https:/
WIP: Complete refactor update: use step file, add information for user.
Addressed by: https:/
Add a strict option to per role tasks file generation.
Addressed by: https:/
Add update and post update tasks to step generated file.
Addressed by: https:/
Properly collect tasks with or conditional in step file.
Addressed by: https:/
Add a strict option to per role tasks file generation.
Addressed by: https:/
Add update and post update tasks to step generated file.
Addressed by: https:/
Properly collect tasks with or conditional in step file.
Addressed by: https:/
Update, avoid task skipping by directly importing step file.
