aboutsummaryrefslogtreecommitdiffstats
path: root/manifests/profile/base/swift/proxy.pp
AgeCommit message (Collapse)AuthorFilesLines
2017-02-03Merge "add cache to object-expirer pipeline"Jenkins1-0/+1
2017-02-01Use transport_url for swift-proxy instead of rabbitmq paramsJuan Antonio Osorio Robles1-25/+52
These parameters are being deprecated, so we should be using the transport_url format instead. Change-Id: I8b7457b6233c4f88af2d7bc1b9304fcccb6edf61
2017-01-17add cache to object-expirer pipelineMarcus Furlong1-0/+1
Without 'cache' in the object-expirer pipeline, adding $memcache_servers will have no effect. This commit adds 'cache' to the pipeline. Change-Id: I8ddb71e8e6a5844446dd2478b6b9389ed0ade075
2017-01-16Merge "Set memcache_servers in /etc/swift/object-expirer.conf"Jenkins1-1/+3
2017-01-16Merge "Enable object-expirer on Swift proxy profile"Jenkins1-0/+2
2016-12-11Decouple swift-proxy from ceilometer packagesDan Prince1-8/+15
This patch updates the swift proxy so that it only depends on ceilometer if the ceilometer_api_enabled all-nodes-data hiera setting has been set. Also removes a parameter dependency where the tripleo::profile::base::swift::proxy class was referencing a puppet-ceilometer value from hiera (which can also cause ceilometer dependencies). Depends-On: Ief5399d7ea4d26e96ce54903a69d660fa4fe3ce9 Change-Id: I8d9f69f5e9160543b372bd9886800f16f625fdc6 Closes-bug: #1648736
2016-11-30Set memcache_servers in /etc/swift/object-expirer.confChristian Schwede1-1/+3
This defaults to 127.0.0.1:11211 without setting these explicitly. The object-expirer is working without a correct memcache server, however it is slower and warnings will be logged. Related-Bug: 1627927 Depends-On: Ie139f018c4a742b014dd4d682970e154d66a8c6d Change-Id: I89a879592a264d541cf42f007584e2e78058c867
2016-11-29Enable object-expirer on Swift proxy profileChristian Schwede1-0/+2
This service is required to delete expired automatically. It is often run on the proxy nodes, therefore adding it to the Swift proxy profile. Change-Id: I3250c205ffc166ae628bc427de2e3492d086c3bb Closes-Bug: 1645657
2016-11-28Use FQDNs for the services' RabbitMQ configurationJuan Antonio Osorio Robles1-4/+4
This replaces the services' IP-based RabbitMQ configuration and uses FQDNs instead. Change-Id: I2be81aecacf50839a029533247981f5edf59cb7f
2016-11-09adding new swift middleware that is typically enabled by defaultThiago da Silva1-0/+5
These are features that are typically enabled by default in any swift cluster. Change-Id: Ie323f68255a73d46e774cbf49d9353c3bf90c35e Signed-off-by: Thiago da Silva <thiago@redhat.com>
2016-11-04swift/proxy: configure rabbitmq properlyEmilien Macchi1-3/+16
Use rabbitmq_node_ips to find out where rabbitmq nodes are, and have correct ipv6 syntax if required. Closes-Bug: 1637443 Change-Id: Ibc0ed642931dd3ada7ee594bb8c70a1c3462206d
2016-10-19Merge "Include ::swift::config in Swift API and Storage roles"Jenkins1-0/+1
2016-10-11Add versioned_writes to Swift proxy configChristian Schwede1-0/+1
Tempest expects object versioning to be enabled by default in Swift; if not it has to be disabled explicitly in the Tempest config. This is a commonly used middleware, therefore it should be enabled in the overcloud proxy nodes as well. Closes-Bug: 1632215 Change-Id: I07a206473ff7939749e3eba1dfe3ea8c4526eb5c
2016-10-07Include ::swift::config in Swift API and Storage rolesGiulio Fidente1-0/+1
This changes makes the Swift API and Storage roles to include the ::swift::config class, as we do for the other OpenStack services, which is useful to push arbitrary config settings into Swift. Change-Id: Iaf2c2f0f0103fe9264ce875099a1578b353a5558
2016-09-23Add swift proxy for ceilometer middlewarePradeep Kilambi1-0/+1
swift proxy has already been updated to use updated ceilometermiddleware as indicated here [1]. Include it in the proxy class. [1] https://github.com/openstack/puppet-swift/commit/e8ad981eff0f97c24a53197c42caf350627d3c9f Change-Id: Ie49f4a750368ff174b23b8d6baa743d0956d727e
2016-09-20swift: normalize memcache servers IP addressesEmilien Macchi1-1/+1
In the case of memcache servers are IPv6, make sure brackets set in the way we construct the list of memcache server + memcache port parameter. Also add unit-tests to test that the output is what we want in the configuration. Depends-On: I8d361ce9cfcfe6a3f8592b2b7991971a3c748c75 Closes-Bug: 1625335 Change-Id: I9fb8168d8fb56c9d8465d58a45fd8c6edfee6fdd
2016-09-01Create memcache_servers list in swift proxy profileSteven Hardy1-1/+14
Instead of mangling this list in t-h-t, generate the list derived from memcached_node_ips, which is now always set when memcached is deployed, regardless of the role. Note the port default is hard-coded as this is already hard-coded (in two places) in t-h-t, but we can override it if this changes in future. We need this to remove the swift specific stuff out of overcloud.yaml to enable custom-roles. Change-Id: Ic8872e5e51732874ca5b93bff5efd3e7ed75bc31 Partially-Implements: blueprint custom-roles
2016-08-08Fix parameters and headers inconsistency in the puppet manifests.Carlos Camacho1-2/+0
As we are staring to manually check overcloud services the first step is to check that the puppet profiles are all aligned. Changes applied: No logic added or removed in this submission. Removed unused parameters. Align header comments structure. All profiles parameters sorted following: "Mandatory params first sorted alphabetically then optional params sorted alphabetically." Note: Following submissions will check pacemaker, cinder, mistral and redis services in the base profiles as some of them has the $pacemaker_master parameter defaulted to true. Change-Id: I2f91c3f6baa33f74b5625789eec83233179a9655
2016-06-08Enable bulk delete in swift for gnocchiPradeep Kilambi1-0/+1
Closes-bug: #1590495 Change-Id: I912c09584d9b4cae530a247c91b6fd331943a8c5
2016-05-31Add puppet profile for swift proxySteven Hardy1-0/+44
Breaks out the swift proxy configuration from t-h-t to a composable profile Change-Id: I6bd72284911f3f449157a6fc00b76682dd53bd8c Partially-Implements: blueprint refactor-puppet-manifests