6496cfc0ba
In a deployment that has both Ceph or Swift deployed it can be useful to seperate the network traffic. This change adds support for dedicated storage networks for both Ceph and Swift. By default, the storage hosts are attached to the following networks: * Overcloud admin network * Internal network * Storage network * Storage management network This adds four additional networks, which can be used to seperate the storage network traffic as follows: * Ceph storage network (ceph_storage_net_name) is used to carry Ceph storage data traffic. Defaults to the storage network (storage_net_name). * Ceph storage management network (ceph_storage_mgmt_net_name) is used to carry storage management traffic. Defaults to the storage management network (storage_mgmt_net_name). * Swift storage network (swift_storage_net_name) is used to carry Swift storage data traffic. Defaults to the storage network (storage_net_name). * Swift storage replication network (swift_storage_replication_net_name) is used to carry storage management traffic. Defaults to the storage management network (storage_mgmt_net_name). This change also includes several improvements to Swift device management and ring generation. The device management and ring generation are now separate, with device management occurring during 'kayobe overcloud host configure', and ring generation during a new command, 'kayobe overcloud swift rings generate'. For the device management, we now use standard Ansible modules rather than commands for device preparation. File system labels can be configured for each device individually. For ring generation, all commands are run on a single host, by default a host in the Swift storage group. A python script runs in one of the kolla Swift containers, which consumes an autogenerated YAML config file that defines the layout of the rings. Change-Id: Iedc7535532d706f02d710de69b422abf2f6fe54c
50 lines
1.7 KiB
YAML
50 lines
1.7 KiB
YAML
---
|
|
# Host on which to build Swift rings.
|
|
swift_ring_build_host:
|
|
|
|
# Path to Kayobe cnnfigutation for Swift.
|
|
swift_config_path:
|
|
|
|
# Path in the container in which to build rings.
|
|
swift_container_build_path: /tmp/swift-rings
|
|
|
|
# Path on the build host in which to store ring files temporarily.
|
|
swift_ring_build_path: /tmp/swift-rings
|
|
|
|
# Docker image to use to build rings.
|
|
swift_ring_build_image:
|
|
|
|
# Base-2 logarithm of the number of partitions.
|
|
# i.e. num_partitions=2^<swift_part_power>.
|
|
swift_part_power:
|
|
|
|
# Object replication count.
|
|
swift_replication_count:
|
|
|
|
# Minimum time in hours between moving a given partition.
|
|
swift_min_part_hours:
|
|
|
|
# List of configuration items for each host. Each item is a dict containing the
|
|
# following fields:
|
|
# - host: hostname
|
|
# - region: Swift region
|
|
# - zone: Swift zone
|
|
# - ip: storage network IP address
|
|
# - ports: dict of ports for the storage network
|
|
# - replication_ip: replication network IP address
|
|
# - replication_ports: dict of ports for the replication network
|
|
# - block_devices: list of block devices to use for Swift. Each item is a dict with the
|
|
# following items:
|
|
# - 'device': Block device path. Required.
|
|
# - 'fs_label': Name of the label used to create the file system on the device.
|
|
# Optional. Default is to use the basename of the device.
|
|
# - 'services': List of services that will use this block device. Optional.
|
|
# Default is 'block_device_default_services' for this host.
|
|
# - 'weight': Weight of the block device. Optional. Default is
|
|
# 'block_device_default_weight' for this host.
|
|
# - 'block_device_default_services': default list of services to assign block
|
|
# devices on this host to.
|
|
# - 'block_device_default_weight': default weight to assign to block devices on
|
|
# this host.
|
|
swift_host_config: []
|