63688a14e5
This change implements storage policies as defined by swift: http://docs.openstack.org/developer/swift/overview_policies.html There are two primary areas of change in this review - Add storage policy support to the ringbuilder and ring devices, along with associated spec tests. - Adding storage policy support and enforcing rules in swift.conf using the swift_storage_policy type and provider. Also: updated spec tests and an update to swift acceptance test to use storage policies to configure an additional 3 replica based ring. See release notes and the README update for more details/instructions. Change-Id: I2b8db751790704df3f1027a14f61e231591537f3
65 lines
2.4 KiB
Puppet
65 lines
2.4 KiB
Puppet
# == Class: swift::deps
|
|
#
|
|
# swift anchors and dependency management
|
|
#
|
|
class swift::deps {
|
|
# Setup anchors for install, config and service phases of the module. These
|
|
# anchors allow external modules to hook the begin and end of any of these
|
|
# phases. Package or service management can also be replaced by ensuring the
|
|
# package is absent or turning off service management and having the
|
|
# replacement depend on the appropriate anchors. When applicable, end tags
|
|
# should be notified so that subscribers can determine if installation,
|
|
# config or service state changed and act on that if needed.
|
|
anchor { 'swift::install::begin': }
|
|
-> Package<| tag == 'swift-package'|>
|
|
~> anchor { 'swift::install::end': }
|
|
-> anchor { 'swift::config::begin': }
|
|
-> Swift_config<||>
|
|
~> anchor { 'swift::config::end': }
|
|
~> anchor { 'swift::service::begin': }
|
|
~> Service<| tag == 'swift-service' |>
|
|
~> anchor { 'swift::service::end': }
|
|
~> Swift_dispersion_config<||>
|
|
|
|
Anchor['swift::config::begin']
|
|
-> Swift_proxy_config<||>
|
|
~> Anchor['swift::config::end']
|
|
|
|
Anchor['swift::config::begin']
|
|
-> Swift_storage_policy<||>
|
|
~> Anchor['swift::config::end']
|
|
|
|
Anchor['swift::config::begin']
|
|
-> Swift_object_config<||>
|
|
~> Anchor['swift::config::end']
|
|
|
|
Anchor['swift::config::begin']
|
|
-> Swift_container_config<||>
|
|
~> Anchor['swift::config::end']
|
|
|
|
Anchor['swift::config::begin']
|
|
-> Swift_account_config<||>
|
|
~> Anchor['swift::config::end']
|
|
|
|
Anchor['swift::config::begin']
|
|
-> File<| tag == 'swift-file' |>
|
|
-> Concat<| tag == 'swift-concat' |>
|
|
~> Anchor['swift::config::end']
|
|
|
|
# Support packages need to be installed in the install phase, but we don't
|
|
# put them in the chain above because we don't want any false dependencies
|
|
# between packages with the swift-package tag and the swift-support-package
|
|
# tag. Note: the package resources here will have a 'before' relationshop on
|
|
# the swift::install::end anchor. The line between swift-support-package and
|
|
# swift-package should be whether or not swift services would need to be
|
|
# restarted if the package state was changed.
|
|
Anchor['swift::install::begin']
|
|
-> Package<| tag == 'swift-support-package'|>
|
|
-> Anchor['swift::install::end']
|
|
|
|
# Installation or config changes will always restart services.
|
|
Anchor['swift::install::end'] ~> Anchor['swift::service::begin']
|
|
Anchor['swift::config::end'] ~> Anchor['swift::service::begin']
|
|
|
|
}
|