Previously, we didn't have a control over volume_backend_name other than
the default app name in the Juju model. A common backend name to
multiple backends with the same character is useful because those can be
treated as a single virtual backend associated with a single volume
type.
Reviewed: https:/ /review. opendev. org/c/openstack /charm- cinder- ceph/+/ 737506 /opendev. org/openstack/ charm-cinder- ceph/commit/ d9873fd22cf1d50 81344bde58b324c fb84a5c693
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit d9873fd22cf1d50 81344bde58b324c fb84a5c693
Author: Nobuto Murata <email address hidden>
Date: Tue Mar 30 15:08:59 2021 +0900
Add support of a common volume_backend_name
Previously, we didn't have a control over volume_backend_name other than
the default app name in the Juju model. A common backend name to
multiple backends with the same character is useful because those can be
treated as a single virtual backend associated with a single volume
type.
Change-Id: I4b57f7979837d2 1a1b116007f3da7 07ee154792b
Closes-Bug: #1884511