Since puppet 3.x, Puppet Labs Forge accept only the metadata.json file
for module description (Modulefile is now deprecated).
This patch :
- convert the Modulefile to metadata.json.
- bump major version to 5 (for juno), and deps.
- switch to stackforge namespace.
- relax pe version_requirement to 3.x.
Change-Id: Id33056d659454b3dbc1921e37978993ca46c5217
This patch allows us to customize log_name for:
- proxy-server
- container-server
- object-server
- account-server
Which may be usefull for log collecting/parsing. Defaults remain
as they were before the patch.
Change-Id: I173652ec5bbe8d4382e10db4510d91aebceacab5
puppetlabs/stdlib 4.x is backwards compatible with 3.x and still tested
on Puppet 2.7. Updating stdlib to 4.x allows modules to use newer
functions without breaking older functionality.
Change-Id: I74e4d3a7bc11cd194fc33a1bbb70f07836ea5d32
Pin to rspec < 2.99 until rspec-puppet officially supports rspec 3.x.
This is to avoid warnings due to deprecated matchers in the
rspec-puppet gem.
This change is also intended to normalize the Gemfile for all stackforge
puppet modules. This should facilitate pinning gem versions when
releasing new stable branches, since the same diff can be used for all
repos.
Change-Id: Ibc857d800943bc256f54bbe9faef0bce080a4fc0
Partial-Bug: #1326034
On RHEL6 restorecon is in /sbin and on newer RHEL based systems it is in /usr/sbin
Closes-Bug: rhbz#1109079
Change-Id: I5662c4337ff23310c12a86834c51c6a3ec151a1f
Facter returns 'false' if selinux is not enabled.
Puppet evaluates it as true as it is not empty.
Change-Id: I2f1d9a348fd981292aeef177b57f08e1b7ef2732
Closes-bug: #1328547
This commit aims to avoid duplication error when the ringserver and the storage node
are on the same machine. For example when using loopback devices.
Change-Id: Ic09af5d3a706d1a59c3fee7689b373d0a4de4e80
Otherwise swift::client can't fetch the name of the package by itself
if swift::params doesn't happen to be in the catalog.
Change-Id: I3d15d0ce68ca084eb4573764b05e8723befbd7e7
Align account_quotas and container_quotas filter names to prevent
swift-proxy from tracing back when quotas are enabled.
Change-Id: I835b05fa5d9eb1fb00cc8309d78bafcd4969d0d3
Closes-Bug: #1323761
Introduce dependencies so swift config files are not created until
the swift packages are installed to avoid failures due to missing
directories, users, and groups supplied by the swift packages.
Change-Id: Ifbd7e9c4f0ecdef03c5afe8459216ddaeb849bb7
Closes-Bug: #1314772
Mounting devices without specifying or restoring context ends up with
default context file_t assigned for swift paths. On selinux systems it
is nice to at least try to preserve predefined contexts on paths.
Change-Id: I9b68c04cb0d4ee72c074e514db7141c3c077c978
Closes-Bug: rhbz#1095503
Closes-Bug: #1320853
On some puppet modules, a it_raises helper is provided. This commit
implements it for puppet-swift.
Change-Id: Id8724823b912f201cc137e23f991d8e05acdcbcc
Since Swift 1.8.0, there is the region layer of topology above zones.
swift-ring-builder supports this natively and this commit allows a user to
specify a region when creating devices.
We maintain backwards compatibility by defaulting to region '1'.
The coverage of the ring builder spec tests were also improved as part of
this commit.
Change-Id: I67cbe6b87c84778f71df59cf00f2c5175342bc1b
The endpoint prefix for keystone endpoints is now configurable (defaults
to AUTH). This will allow for easier integration with SwiftStack
which requires that the endpoint prefix not be AUTH.
Change-Id: I102008aad86c0e35e3020961119a56c81da973f3
The latest Rake update requires Ruby >= 1.9. Bundler in the
current gate uses 1.8.x. This update fixes the gate by pinning
Rake to the last known working version.
Change-Id: I8f798a71246c39deb91610bad1d0261aaa485a75
Before this update the Modulefile was not following semver in
relation to stable/havana, and the README files were not in sync.
This update introduces proper semver and consistency.
Change-Id: I65fda078f20eb8d41b260c4550ac3c262cca8267
The storage::server class includes a bit of logic that checks
the pipeline and warns if ${type}-server isn't included.
However, the check has a logic flaw such that if $pipeline is an
array and contains ${type}-server, the warning is triggered
anyway. This patch corrects the bad logic so that the warning
isn't triggered spuriously.
Change-Id: I7f81598f2f7910a2175fe772c9d82b2a1067826c
Closes-Bug: #1289187
In the actual state of the manifest we can only setup package_ensure to
absent|present|latest. This commit allow end users to pin swift* and
swift-client to a specific version. (note that swift* and
python-swiftclient version are not the same).
A new class (swift::client) manage now client packages, and we keep the
retro-compatibility of commit 020b7723cbbe75fbcae89514a1e1882ae807fb27.
Change-Id: I9bcc5a0f9d0a93a812fb574c4571fb9584077e4a
Some of the swift classes use parameterized settings defined in
swift::params but do not include the swift::params class.
Change-Id: I7704bf42db4554566d27b510bbbedb8afe0fe7b3
Closes-Bug: #1288252
The puppet-swift modules emit deprecation warnings of the form:
Warning: Variable access via 'pipeline' is deprecated. Use
'@pipeline' instead. template[inline]:2
(at (erb):2:in `result')
These are due to missing @ signs in inline ERB templates in
storage/server.pp and proxy.pp. This patch fixes them.
Change-Id: I3745cfd86c4332f00bc10a0999088691b3833147
Closes-Bug: #1282717
It is possible to disable endpoint configuration by setting
the value of the configure_endpoint and configure_s3_endpoint
parameters to false.
The default value is true, preserving default behavior.
Change-Id: I0f9afb78c181573a30f93dc4f862f86baa3efe31
Closes-bug: #1279071