Provide a script to automate cleanup of _base
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| OpenStack Compute (nova) |
Undecided
|
Unassigned | ||
| nova (Ubuntu) |
Medium
|
Unassigned |
Bug Description
The nova base instance directory $instances_
Scott Moser (smoser) wrote : | #1 |
Changed in nova (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
status: | New → Confirmed |
Michael Still (mikal) wrote : | #2 |
I have just send a patch for review which implements the _base cleanup aspects of the blueprint. Its integrated into the nova compute manager, as opposed to being a separate script.
tags: | added: canonistack |
Thierry Carrez (ttx) wrote : | #3 |
Looks like this landed in E4. Please reopen if there is more to it.
Changed in nova: | |
status: | Confirmed → Fix Released |
Bolke de Bruin (bolke-de-bruin) wrote : | #4 |
What happens if I trun on the cleanup and I have instances residing on a glusterfs. Briefly reading the code (Ubuntu essex release) the image does not get marked in use and will be removed. Is that correct?
If so, would this be configurable let's say with a "instances_
Michael Still (mikal) wrote : | #5 |
Bolke -- that's not currently the case. If you want this functionality you should file a separate bug for it. However, with a shared instances directory you're best off disabling the cache manager entirely at the moment.
Dave Walker (davewalker) wrote : | #6 |
Marking Ubuntu task as fix released, as this should be included with Essex-4 milestone and above. If this is not the case, please re-adjust the status as appropriate. Thanks.
Changed in nova (Ubuntu): | |
status: | Confirmed → Fix Released |
This is related to http:// wiki.openstack. org/nova- image-cache- management