Mitaka Series Release Notes¶
13.3.1¶
New Features¶
The
os_swift
role has 3 new variables that will allow a deployer to change the hard, soft and fs.file-max limits. the hard and soft limits are being added to the limits.conf file for the swift system user. The fs.file-max settings are added to storage hosts via kernel tuning. The new options areswift_hard_open_file_limits
with a default of 10240swift_soft_open_file_limits
with a default of 4096swift_max_file_limits
with a default of 24 times the value ofswift_hard_open_file_limits
.
13.2.0¶
Bug Fixes¶
Previously, the
ansible_managed
var was being used to insert a header into theswift.conf
that contained date/time information. This meant that swift.conf across different nodes did not have the same MD5SUM, causingswift-recon --md5
to break. We now insert a piece of static text instead to resolve this issue.
13.1.3¶
New Features¶
Allow the fallocate_reserve option to be set (in bytes) for Swift, to help prevent disks from filling up and prevent a situation where Swift is unable to remove objects due to a lack of disk space. The fallocate_reserve value to is set to a default of 10GB.
Enable rsync module per object server drive by setting the
swift_rsync_module_per_drive
setting toTrue
. Set this to configure rsync and swift to utilise individual configuration per drive. This is required when disabling rsyncs to individual disks. For example, in a disk full scenario.
Upgrade Notes¶
The
swift_max_rsync_connections
default value has changed from 2 to 4 in order to match the OpenStack swift documented value.