openstack/puppet-swift
Code Issues Proposed changes

Add support for swift-object-expirer service

Browse Source 
The swift-object-expirer service was not supported by
puppet-swift. Adding support by creating a new class
(swift::objectexpirer), and its associated custom type/provider.

Change-Id: I498ffe525a7316c0091e4c9d8b7d9658234231f6
This commit is contained in:
Javier Pena
2015-09-10 15:51:52 +02:00
parent 79b596b817
commit d8a8b70547
9 changed files with 422 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@@ -236,6 +236,15 @@ The byte size that dd uses when it creates the file system.
####`seek`
The size of the file system that will be created. Defaults to 25000.
### Class: swift::objectexpirer
Class that will set Swift object expirer, for scheduled deletion of objects.
```puppet
class { 'swift::objectexpirer': }
```
It is assumed that the object expirer service will usually be installed in a proxy node. On Red Hat-based distributions, if the class is included in a non-proxy node, the openstack-swift-proxy package will need to be installed.
### Verifying installation
This modules ships with a simple Ruby script that validates whether or not your swift cluster is functional.