Home OpenStack-Ansible Swift
Configuring the service¶
Procedure 5.2. Updating the Object Storage configuration ``swift.yml`` file
# cp /etc/openstack_deploy/conf.d/swift.yml.example \ /etc/openstack_deploy/conf.d/swift.yml
Update the global override values:
# global_overrides: # swift: # part_power: 8 # weight: 100 # min_part_hours: 1 # repl_number: 3 # storage_network: 'br-storage' # replication_network: 'br-repl' # drives: # - name: sdc # - name: sdd # - name: sde # - name: sdf # mount_point: /srv/node # account: # container: # storage_policies: # - policy: # name: gold # index: 0 # default: True # - policy: # name: silver # index: 1 # repl_number: 3 # deprecated: True # statsd_host: statsd.example.com # statsd_port: 8125 # statsd_metric_prefix: # statsd_default_sample_rate: 1.0 # statsd_sample_rate_factor: 1.0
Set the partition power value based on the total amount of storage the entire ring uses.
Multiply the maximum number of drives ever used with the swift installation by 100 and round that value up to the closest power of two value. For example, a maximum of six drives, times 100, equals 600. The nearest power of two above 600 is two to the power of nine, so the partition power is nine. The partition power cannot be changed after the swift rings are built.
The default weight is 100. If the drives are different sizes, set the weight value to avoid uneven distribution of data. For example, a 1 TB disk would have a weight of 100, while a 2 TB drive would have a weight of 200.
The default value is 1. Set the minimum partition hours to the amount of time to lock a partition’s replicas after moving a partition. Moving multiple replicas at the same time makes data inaccessible. This value can be set separately in the swift, container, account, and policy sections with the value in lower sections superseding the value in the swift section.
The default value is 3. Set the replication number to the number of replicas of each object. This value can be set separately in the swift, container, account, and policy sections with the value in the more granular sections superseding the value in the swift section.
By default, the swift services listen on the default management IP. Optionally, specify the interface of the storage network.
storage_networkis not set, but the
storage_ipsper host are set (or the
storage_ipis not on the
storage_networkinterface) the proxy server is unable to connect to the storage services.
Optionally, specify a dedicated replication network interface, so dedicated replication can be setup. If this value is not specified, no dedicated
Replication does not work properly if the
repl_ipis not able to connect to other hosts
Set the default drives per host. This is useful when all hosts have the same drives. These can be overridden on a per host basis.
mount_pointvalue to the location where the swift drives are mounted. For example, with a mount point of
/srv/nodeand a drive of
sdc, a drive is mounted at
swift_host. This can be overridden on a per-host basis.
Storage policies determine on which hardware data is stored, how the data is stored across that hardware, and in which region the data resides. Each storage policy must have a unique
nameand a unique
index. There must be a storage policy with an index of 0 in the
swift.ymlfile to use any legacy containers created before storage policies were instituted.
Set the default value to
yesfor at least one policy. This is the default storage policy for any non-legacy containers that are created.
Set the deprecated value to
yesto turn off storage policies.
For account and container rings,
repl_numberare the only values that can be set. Setting them in this section overrides the defaults for the specific ring.
Swift supports sending extra metrics to a
statsdhost. This option sets the
statsdhost to receive
statsdmetrics. Specifying this here applies to all hosts in the cluster.
statsd_hostis left blank or omitted, then
statsdsettings can be overridden or you can specify deeper in the structure if you want to only catch
statsdvmetrics on certain hosts.
Optionally, use this to specify the
statsdserver’s port you are sending metrics to. Defaults to 8125 of omitted.
statsdrelated options are more complex and are used to tune how many samples are sent to
statsd. Omit them unless you need to tweak these settings, if so first read: https://docs.openstack.org/swift/latest/admin_guide.html
Update the swift proxy hosts values:
# swift-proxy_hosts: # infra-node1: # ip: 192.0.2.1 # statsd_metric_prefix: proxy01 # infra-node2: # ip: 192.0.2.2 # statsd_metric_prefix: proxy02 # infra-node3: # ip: 192.0.2.3 # statsd_metric_prefix: proxy03
IPaddress of the hosts so Ansible connects to to deploy the
swift-proxy_hostsvalue matches the infra nodes.
This metric is optional, and also only evaluated it you have defined
statsd_hostsomewhere. It allows you define a prefix to add to all
statsdmetrics sent from this hose. If omitted, use the node name.
Update the swift hosts values:
# swift_hosts: # swift-node1: # ip: 192.0.2.4 # container_vars: # swift_vars: # zone: 0 # statsd_metric_prefix: node1 # swift-node2: # ip: 192.0.2.5 # container_vars: # swift_vars: # zone: 1 # statsd_metric_prefix: node2 # swift-node3: # ip: 192.0.2.6 # container_vars: # swift_vars: # zone: 2 # statsd_metric_prefix: node3 # swift-node4: # ip: 192.0.2.7 # container_vars: # swift_vars: # zone: 3 # swift-node5: # ip: 192.0.2.8 # container_vars: # swift_vars: # storage_ip: 198.51.100.8 # repl_ip: 203.0.113.8 # zone: 4 # region: 3 # weight: 200 # groups: # - account # - container # - silver # drives: # - name: sdb # weight: 75 # groups: # - gold # storage_port: 6010 # repl_port: 6110 # - name: sdc # - name: sdd # - name: sde # - name: sdf
Specify the hosts to be used as the storage nodes. The
ipis the address of the host to which Ansible connects. Set the name and IP address of each swift host. The
swift_hostssection is not required.
Contains the swift host specific values.
Base these values on the IP addresses of the host’s
replication_network. For example, if the
br-storageand host1 has an IP address of 184.108.40.206 on
br-storage, then this is the IP address in use for
storage_ip. If only the
storage_ipis specified, then the
repl_ipdefaults to the
storage_ip. If neither are specified, both default to the host IP address.
Used to enable running object servers per disk. The default value for both is
The default is 0. Optionally, set the swift zone for the ring.
Optionally, set the swift region for the ring.
The default weight is 100. If the drives are different sizes, set the weight value to avoid uneven distribution of data. This value can be specified on a host or drive basis (if specified at both, the drive setting takes precedence).
Set the groups to list the rings to which a host’s drive belongs. This can be set on a per drive basis which overrides the host setting.
Set the names of the drives on the swift host. Specify at least one name.
This metric is optional, and only evaluates if
statsd_hostis defined somewhere. This allows you to define a prefix to add to all
statsdmetrics sent from the hose. If omitted, use the node name.
In the following example,
swift-node5shows values in the
swift_hostssection that override the global values. Groups are set, which overrides the global settings for drive
sdb. The weight is overridden for the host and specifically adjusted for drive
sdb.# swift-node5: # ip: 192.0.2.8 # container_vars: # swift_vars: # storage_ip: 198.51.100.8 # repl_ip: 203.0.113.8 # zone: 4 # region: 3 # weight: 200 # groups: # - account # - container # - silver # drives: # - name: sdb # weight: 75 # groups: # - gold # - name: sdc # - name: sdd # - name: sde # - name: sdf
swift.ymlis in the