helm-service-cleanup

Registered by Serguei Bezverkhi on 2017-01-26

When a service example cinder gets deployed with helm charts and then removed, it leaves some leftovers like cinder database, some service/user records in keystone. All these leftovers prevents successful subsequent deployment of cinder. The root cause of this is the way how openstack components react on already existing objects. Instead of exiting without action of detection of this objects, they fail.
The same issue will be applied to all openstack processes which creating databases and running manage db process.

Blueprint information

Status:
Started
Approver:
Steven Dake
Priority:
Medium
Drafter:
Serguei Bezverkhi
Direction:
Approved
Assignee:
Serguei Bezverkhi
Definition:
Approved
Series goal:
Accepted for master
Implementation:
Good progress
Milestone target:
milestone icon 0.7.0
Started by
Serguei Bezverkhi on 2017-01-28

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/for,n,z

Addressed by: https://review.openstack.org/425875
    adding cleanup service for cinder

Gerrit topic: https://review.openstack.org/#q,topic:bp/helm-service-cleanup,n,z

Addressed by: https://review.openstack.org/426400
    PS Adds keystone cleanup service

Addressed by: https://review.openstack.org/426438
    PS adds glance cleanuip service

Addressed by: https://review.openstack.org/427215
    PS adds neutron cleanup service

Addressed by: https://review.openstack.org/427354
    PS adds nova cleanup service

(?)

Work Items

Work items:
(unassigned): TODO
(unassigned)rabbitmq: TODO
(unassigned)memcached: TODO
(sbezverk)keystone: DONE
(sbezverk)glance: DONE
(sbezverk)neutron: DONE
(sbezverk)nova: DONE
(sbezverk)cinder: DONE
(unassigned)openvswitch db/vswitchd: TODO
(unassigned)horizon: TODO
(unassigned)heat: TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.