tripleo-heat-templates/releasenotes/notes/configure-multipathd-with-ansible-f32f3ea627815191.yaml
Alan Bishop 80fcd33248 Deploy multipathd using tripleo_multipathd ansible role
The puppet and ansible tasks for deploying the Multipathd service have
been moved to a new tripleo_multipathd ansible role. THT uses that role
passing in parameter values via ansible variables.

Two new THT parameters are supported:
- MultipathdCustomConfigFile provides a way for the user to specify a
  custom multipath.conf file. This makes it easier for the user to
  manage custom settings that are unique to their deployment, such as
  vendor specific hardware tuning.
- MultipathdSkipKpartx provides a means for overriding multipathd's
  default behavior whereby it automatically creates disk partitions on
  multipath devices. Partitions should be managed by VM servers accessing
  the device, not by the overcloud host itself.

Depends-On: Icf9faff31d83f0ea77d00a59a53d6ad36b06da4f
Depends-On: I3478312b5117da5c2e819e47c99f574246e84838
Change-Id: I934a1ae5bc0d77fd39b25f5039635e5df6e9004f
2020-10-22 06:07:15 -07:00

21 lines
810 B
YAML

---
features:
- |
A new multipathd-container-ansible.yaml heat template replaces the
multipathd-container.yaml template. The new template adds support for
the following new parameters.
* MultipathdSkipKpartx
* MultipathdCustomConfigFile
upgrade:
- |
When upgrading from the multipathd-container.yaml template to the new
multipathd-container-ansible.yaml template, bear in mind the new
MultipathdSkipKpartx parameter will configure the corresponding skip_kpartx
setting in /etc/multipath.conf.
deprecations:
- |
The multipathd-container.yaml template is deprecated in favor of a new
multipathd-container-ansible.yaml template. The new template is backward
compatible with the old template, but see the features and upgrade notes
for additional details.