Allow to update or replace failed resources custom

Registered by huangtianhua

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://bugs.launchpad.net/heat/+bug/1490134, but it's better to register a blueprint to trace, also I will propose the series for other resources.

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:
milestone icon ocata-3
Started by
huangtianhua
Completed by
huangtianhua

Related branches

Sprints

Whiteboard

https://review.openstack.org/#/c/389117/
     Refactor _needs_update() for resource
https://review.openstack.org/#/c/403977/
      Don't replace failed cinder volume always
Gerrit topic: https://review.openstack.org/#q,topic:bp/custom-update-replace-for-failed-resources,n,z

Addressed by: https://review.openstack.org/409649
    Do not replace failed server always

Addressed by: https://review.openstack.org/410060
    Don't replace failed neutron resources always

Addressed by: https://review.openstack.org/415160
    Replace always if resource is in CHECK_FAILED

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.