This change ensures cache parameters of container-reconciler and
object-expirer are cleared when the cache middleware is not enabled
in these two services.
Change-Id: I062c878a674c9550ea60dce6a4f4123ceb885ac7
This change updates the default pipeline of object-expirer, so that
we follow what is described in the default object-expirer.conf
maintained in swift repo.
Change-Id: I58cf2bc21a0bc4265114b9daf3919a1a38f63649
Moves all spec tests over to using rspec-puppet-facts
and runs the tests for all our supported operating systems.
Change-Id: Ie2d60acac835affaf46a5276c9755640a723bca4
Object expirer does not have log_facility set explicitly
and defaults to LOG_LOCAL0, thus logging to /var/log/messages
All other swift services have been set to LOG_LOCAL2. This
patch changes object expirer to LOG_LOCAL2.
Change-Id: I037090eecc9832e7c7397a5a9e52df4a23f6c16e
Signed-off-by: Thiago da Silva <thiago@redhat.com>
This commit adds support for the memcache_servers option in
object-expirer and container-reconciler. Without this, both
currently default to 127.0.0.1:11211.
Closes-Bug: #1627927
Change-Id: Ie139f018c4a742b014dd4d682970e154d66a8c6d
The 'swiftinit' provider is a custom provider of the service type
that manages swift services using swift-init.
Use of the swiftinit service provider is optional, the default is
to use service providers specified in params file. This provider
also manages swift services starting at boot by adding or removing
a templated init or services file and making systemctl calls.
See README for more detail.
A wrapper defined type 'swift::service' has been created to simplify
use of the swiftinit provider without adding logic to every class.
this wrapper also aids in input validation and testing of the
swiftinit provider.
Two extra runs of apply_manifest have been added to the
basic_swift_spec acceptance test. The service_provider
is set to "swiftinit". The first run catches any errors upgrading
to the swiftinit service provider and the second run tests
idempotency.
This patch is an initial step towards using swift-init to manage
multiple swift services out of different configuration files such
as is needed to run a separate replication network.
Change-Id: I2f71c82c7a6c463f8c76a193409c0a17daa15bda
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