aboutsummaryrefslogtreecommitdiffstats
path: root/swift-deploy.yaml
AgeCommit message (Collapse)AuthorFilesLines
2015-01-27Swift: set default replicas to 3Dan Prince1-1/+1
Our existing default (replicas == 1) means that no data (or copies) is being replicated in a multi-node Swift environment. This seems like a bad production default setting and could easily slip by if not set. Setting it to 3 shouldn't hurt anything and seems to follow suit with what several production installers (based around Puppet) actually use. If using an installation with less than 3 swift nodes I believe swift will do its best, and still work fine. FWIW I noticed this when testing a multi-node Puppet swift installation and was surprised when I didn't see any *data files getting replicated across the storage cluster. Change-Id: I44bdfff7aae6bdf845b79ca1f8f450c22113caed
2014-11-12Add swift.mount-check metadataEamonn O'Toole1-0/+5
We've submitted a patch (https://review.openstack.org/#/c/130172/) to set the value of mount_check to swift.mount-check if it exists, and otherwise to set mount_check to false. By default TripleO deployments set mount_check to false since they do not use mounted disks to store data. However we (HP) and others are now using TripleO to deploy Swift servers with mounted drives for data, in which case mount_check should be set to True. This change adds swift.mount-check data and sets it to the value of the SwiftMountCheck parameter, which has a default value of False. Change-Id: I36fece56bafa9fe9c4883b572687b3fc819eeae1
2014-10-08Sort inputs and parametersAlexis Lee1-8/+8
They're mostly rather higgledy-piggledy at the moment which makes it quite difficult to compare against files where these are sorted. EG compute.yaml from I687a00c7dc164ba044f9f2dfca96a02401427855. Change-Id: I508a3d0f6a79810d2100fdd1ad143bcd37bf8c00
2014-10-07Merge "Add SwiftMinPartHours parameter"Jenkins1-0/+5
2014-09-29Add SwiftMinPartHours parameterLorcan1-0/+5
This parameter adds the facility for an operator to set the length of time in hours that a partition in a swift ring can be altered following a rebalance of that ring. The default value is set to one. The corresponding element change is here: Ie6438386a54794e1ae2f31ad925db01c2c10ed6d Change-Id: Icc5e431a7e2884b3ca3a255b6fd901619bc98460
2014-09-05Parametrize Swift partition powerEamonn O'Toole1-0/+5
The Swift partition power is currently hard-coded to 10. While this is fine for small Swift clusters there are some users who will want to configure rings with higher partition powers. We have parametrized the value of the partition power, and the default is set to 10. Change-Id: If115cf5cf2f4c2ff7d28b0f5ae3d2ca3f4b4be5a
2014-08-26Merge "Make Swift replica count configurable."Jenkins1-0/+5
2014-08-13Make Swift replica count configurable.Robert Collins1-0/+5
Using 1 is thoroughly non-HA :) This is the HOT version of this patch. Change-Id: Ic96bcdc03dacb9650520bd9ac1ce3805c6dac2fa implements: blueprint tripleo-icehouse-ha-production-configuration
2014-08-13Switch to heat_template_version: 2013-05-23Steve Baker1-6/+6
To support underclouds and seeds running older than the very latest heat. 2013-05-23 lacks function list_join, so this change reverts to using the equivalent function Fn::Join. Change-Id: I039f57ab39c1fcfc319a7a34265ba4fabf4ccd08 Closes-Bug: #1354305
2014-08-04Convert Fn::Select to extended get_attrSteve Baker1-9/+3
Overcloud bootstrap_nodeid is now specified by parameter BootStrapNodeResource with default value controller0. This avoids the need to use Fn::Select on the mergy.py built list of controllers to specify the first controller. Change-Id: Id9cfeab50b90ceeeae51ea0e35997b7495b28cc4 Partial-Blueprint: tripleo-juno-remove-mergepy
2014-08-04Port all templates to HOTSteve Baker1-26/+26
This change was generated and validated by running the following: make hot clean all validate-all This converts all templates to be valid HOT. Fn::Select is not converted in this change but this will actually work with heat_template_version 2013-05-23. Fn::Select is converted manually in the next change in this series. This change also sets the heat_template_version to 2014-10-16 which includes the list_join intrinsic functions used throughout these templates. Partial-Blueprint: tripleo-juno-remove-mergepy Change-Id: Ib3cbb83f6ae94adb7b793ab1b662bd5c55cbb5b3
2014-07-30Fix swift memcache and device propertiesJan Provaznik1-40/+28
All controller nodes are added into the list of swift devices and into the list of memcache servers. This patch also removes swift storage nodes from the list of memcache servers - I don't think that each storage node should run proxy server (also swift-storage element doesn't depend on swift-proxy). Change-Id: Idb2ce2e2050fb84d8f8b564626b20e7b059fd685
2014-04-17Adding Swift proxy-server memcache metadataEamonn O'Toole1-0/+22
Swift proxy-servers use memcache to store and share metadata. This change adds swift.proxy-memcache metadata to the swift-source and swift-storage-source yaml templates modelled on the existing swift.devices metadata. This metadata will be consumed by the swift-proxy/os-config-applier/etc/swift/proxy-server.conf element if the metadata exists. Change-Id: If0b5724f69e7ec1c98e4dbdbeb9f08c4a18151b6
2014-04-16Switch overcloud to software-configClint Byrum1-0/+45
This migrates the overcloud to using OS::Heat::StructuredConfig and OS::Heat::StructuredDeployment. With those tools, we can decouple servers from software configuration and begin to deprecate features in tripleo_heat_merge. Change-Id: Ice85f0711e90d0fabf1d1bc4698201c4d6758508