Allow a user to trigger redeployment of a ready cluster
Bug #1515682 reported by
Vladimir Kuklin
This bug report is a duplicate of:
Bug #1540558: Add ability to apply the changes to the cluster which is in the operational state.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Triaged
|
High
|
Fuel Python (Deprecated) | ||
Bug Description
Sometimes users want to be able to redeploy a cluster that they have after its successful deployment. This should be almost identical to classic puppet rerun, e.g. converging the cluster back to the desired state if there were any changes made manually or to just ensure consistency of the configuration on a regular basis.
| tags: | added: area-python |
| Changed in fuel: | |
| assignee: | nobody → Fuel Python Team (fuel-python) |
| Changed in fuel: | |
| status: | Confirmed → Triaged |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Alexander Saprykin (cutwater) |
| status: | Triaged → In Progress |
| Changed in fuel: | |
| status: | In Progress → Triaged |
| Changed in fuel: | |
| assignee: | Alexander Saprykin (cutwater) → Fuel Python Team (fuel-python) |
To post a comment you must log in.
