Ensure settings changes only touch affected configurations
Registered by
Alex Schultz
When rerunning a task a second time with specific configuration changes, we expect:
1) Re-running of a Task with changes in input data results in changes made only in configuration parameters for which input values were changed
2) Re-running of a Task does not result in unnecessary restart and/or downtime of cloud services
3) If a service restart or downtime is required when configuration changes are required, a notification the end user prior to running the change should be done.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Essential
- Drafter:
- Alex Schultz
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
9.0
- Started by
- Alex Schultz
- Completed by
- Szymon Banka
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Fix cinder type ensurabilty
(?)
Work Items
Dependency tree

* Blueprints in grey have been implemented.