Zun

heal non-existent containers in docker

Registered by weikeyou on 2018-03-07

When update containers states, if Container was recorded in DB but missing in docker, The process sets the state of the container with the auto_remove attribute to DELETED, and does nothing to the container without "auto_remove". The purpose of the BP is to heal those containers with rebuilding them.

Blueprint information

Status:: Complete

Approver:: hongbin

Priority:: Medium

Drafter:: weikeyou

Direction:: Approved

Assignee:: weikeyou

Definition:: New

Series goal:: None

Implementation:: Implemented

Milestone target:: None

Started by: hongbin on 2018-04-22

Completed by: hongbin on 2018-04-22

Related branches

Related bugs

Sprints

Whiteboard

(hongbin 2018-03-07) This feature could be useful but it fundamentally change the existing behavior (no auto-healing). In addition, it doesn't match the user experience in Docker. IMHO, we need to implement an option to enable/disable this feature. If it is disable, Zun shouldn't do the auto-healing (as it is).

Gerrit topic: https://review.openstack.org/#q,topic:bp/heal-non-existent-containers-in-docker,n,z

Addressed by: https://review.openstack.org/553698
Add auto_heal to container

Addressed by: https://review.openstack.org/555694
Heal non existent containers in docker

Addressed by: https://review.openstack.org/558201
Add auto_heal to api-ref

(?)

Work Items

This blueprint contains Public information

Everyone can see this information.

Subscribers

No subscribers.