Allow to update or replace failed resources custom
Recently I developed some custom resource plugins to integrate our production, and the mechanism of replacing failed resource is so bad, the state of resource is UPDATE(*)_FAILED in heat, but actually it is in active underlying, what's more is that we can't to re-create some resources with same properties as old ones, because there is nothing we can do before replacing, e.g we do something for nova server, detaching port from the old server to make sure we can create a new server and attach the same port. But not every resource can apply this mechanism.
I have proposed a bug https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- huangtianhua
- Direction:
- Approved
- Assignee:
- huangtianhua
- Definition:
- Approved
- Series goal:
- Accepted for ocata
- Implementation:
- Implemented
- Milestone target:
- ocata-3
- Started by
- huangtianhua
- Completed by
- huangtianhua
Related branches
Related bugs
Sprints
Whiteboard
https:/
Refactor _needs_update() for resource
https:/
Don't replace failed cinder volume always
Gerrit topic: https:/
Addressed by: https:/
Do not replace failed server always
Addressed by: https:/
Don't replace failed neutron resources always
Addressed by: https:/
Replace always if resource is in CHECK_FAILED