tripleo-heat-templates/deployment/swift
Takashi Kajinami 190420f1bb Fix inconsistent <service>Workers
Currently the <service>Workers parameters are implemented in different
ways according to services. Because of this, these parameters enforce
different type(number vs string) and behave differently for a specific
value such as 0. These are quite confusing for users.

This change introduces the standard implementation for all Workers
parameters so that the parameters behave consistently in all services.

This also introduces the following changes as side-effects.

- Outdated description of some workers parameter is removed. Currently
  workers are limited to a certain number(such as 12) even in a system
  with many CPU cores

- Default value of BarbicanWorkers is effectively lowered down to
  $::os_workers from $::processorcount, to use the consistent default
  workers for all services.

Change-Id: Ie7a12a297e00efebca017d51afb9bf9e8c56ee50
2022-09-27 12:28:44 +09:00
..
external-swift-proxy-baremetal-puppet.yaml Merge "Honor the ExternalSwiftUserTenant parameter" 2021-10-30 00:27:42 +00:00
swift-base.yaml Use server side env merging for ServiceNetMap/VipSubnetMap 2021-05-19 10:16:58 +05:30
swift-dispersion-baremetal-puppet.yaml Use server side env merging for ServiceNetMap/VipSubnetMap 2021-05-19 10:16:58 +05:30
swift-proxy-container-puppet.yaml Fix inconsistent <service>Workers 2022-09-27 12:28:44 +09:00
swift-ringbuilder-container-puppet.yaml Role specific container support 2022-01-21 14:18:02 -07:00
swift-storage-container-puppet.yaml Fix inconsistent <service>Workers 2022-09-27 12:28:44 +09:00