Merge lp://staging/~niedbalski/charms/trusty/cinder/remove-unused-services into lp://staging/~openstack-charmers-archive/charms/trusty/cinder/next
Status: | Rejected |
---|---|
Rejected by: | Edward Hope-Morley |
Proposed branch: | lp://staging/~niedbalski/charms/trusty/cinder/remove-unused-services |
Merge into: | lp://staging/~openstack-charmers-archive/charms/trusty/cinder/next |
Diff against target: |
84 lines (+70/-0) 2 files modified
actions.yaml (+6/-0) actions/remove_services.py (+64/-0) |
To merge this branch: | bzr merge lp://staging/~niedbalski/charms/trusty/cinder/remove-unused-services |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Edward Hope-Morley | Needs Fixing | ||
Billy Olsen | Needs Fixing | ||
Review via email:
|
Description of the change
Dear Maintainer,
This is a patch for adding a new action 'ha-remove-
the rationale behind this is to expose a way to cleanup the services
table on the database from unused ones , those services were
created by cinder before the storage relation is joined (particularly
for stateless ones).
This is a workaround for LP: #1493931 in order to keep the
output of cinder service-list clean after deploying a HA.
Thanks.
Unmerged revisions
- 153. By Jorge Niedbalski
-
Changed session
- 152. By Jorge Niedbalski
-
Corrected schema
- 151. By Jorge Niedbalski
-
Changed according to @wolsen observations.
- 150. By Jorge Niedbalski
-
action_set format
- 149. By Jorge Niedbalski
-
action_set format
- 148. By Jorge Niedbalski
-
action_set format
- 147. By Jorge Niedbalski
-
Added hooks path
- 146. By Jorge Niedbalski
-
Added missing symlink for action
- 145. By Jorge Niedbalski
-
- Added a new action for removing unused services
after the unit is related to a stateless backend such as the
cinder backend via cinder-ceph. Per bug #1493931.Reference: https:/
/bugs.launchpad .net/charms/ +source/ cinder- ceph/+bug/ 1493931
Jorge,
Thanks for the patch! I think this is starting to be a nice work around for the bug. I've made some inline comments which I think need to be addressed.
Perhaps we should first disable the service (cinder service-disable) prior to removing it? Sure its defunct, but it might be nice to also qualify the deletion statement with a disabled qualifier.
Additionally, in >= Liberty, cinder includes the cinder-manage service remove [name], which I think should be the preferred method with this as an option for < liberty.