glance-cache-cleaner not run by default

[Dave Johnston]

On controller nodes the glance image-cache is part of the root partition. Over time this can fill up causing services to break.

This could be prevented by setting the image_cache_max_size in glance-cache.conf.

Also glance-cache-cleaner should be configured to run at regular intervals.

Alternatively the image-cache should be placed on a separate volume to avoid filling up the root partition.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/167204

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/167204
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=ade15f965be55072df5dabc236e1fd21ea79623c
Submitter: Jenkins
Branch: master

commit ade15f965be55072df5dabc236e1fd21ea79623c
Author: Bartłomiej Piotrowski <email address hidden>
Date: Tue Mar 24 10:57:18 2015 +0100

    Enable cronjobs for glance-cache-cleaner and glance-cache-pruner

    Currently we do not run neither, possibly leading to no free
    space on controllers or cinder nodes, taking them down.

    Change-Id: Ic1cb5d41cd1fc003eabc1212abeb6145b12936e5
    Closes-Bug: 1434740
    Closes-Bug: 1435185

[Alexander Nevenchannyy (anevenchannyy)]

Verified on MOS 6.1 ISO #429
Steps to Verify:
root@node-1:/etc# crontab -u glance -l
# HEADER: This file was autogenerated at 2015-05-20 14:31:09 +0000 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: glance-cache-cleaner
PATH=/bin:/usr/bin:/usr/sbin
1 0 * * * glance-cache-cleaner
# Puppet Name: glance-cache-pruner
PATH=/bin:/usr/bin:/usr/sbin
*/30 * * * * glance-cache-pruner