Support a new deletion policy to stop first

Registered by huangtianhua

In some user cases, user want to stop the nova server first to do some cleanup work before to terminate the server, one example:
Magnum using heat to deploy kubernate cluster, each node will register to the mater node when creation, and the ones to be terminated should to logout first.
But now in heat, if the count of ResourceGroup is scale-down, the resource is deleted directly, because we don't have the corresponding deletion policy to stop first before terminate. This blueprint aim to add such deletion policy.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
huangtianhua
Direction:
Needs approval
Assignee:
huangtianhua
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Thomas Herve

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-stop-deletion-policy,n,z

Addressed by: https://review.openstack.org/243012
    Support 'Stop' deletion policy for resource

Addressed by: https://review.openstack.org/243507
    Support 'Stop' deletion policy for resource

Addressed by: https://review.openstack.org/243443
    Define engine service in setUp()

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.