Nobuto Murata 12193d2bc2 Allow specifying default_volume_type ... It's useful when multiple storage backends to be connected to Cinder. The corresponding volume type must be created after a deployment via API to take effect, e.g., `openstack volume type create VOLUME_TYPE --property volume_backend_name=BACKEND_NAME` Please note that there is a regression in upstream as LP: #1879578, so it doesn't work for Train or later releases until the issue gets fixed. The other way to have the similar effect is to edit the definition of __DEFAULT__ volume type via API (available for Train or later releases). Howevers it's not as flexible as the option in cinder.conf since it doesn't allow any modification unless all of the volumes with the __DEFAULT__ type get deleted. Change-Id: I031a6bf2a066bb9d3157e545bb9df782a76551f3 Closes-Bug: #1884548		2020-08-19 17:51:35 +00:00
..
icehouse	Support using internal network for clients	2016-04-01 12:10:59 +01:00
kilo	Modify the spelling mistakes	2017-08-17 22:51:58 -07:00
liberty	Modify the spelling mistakes	2017-08-17 22:51:58 -07:00
mitaka	Migrate to python3 only charm	2019-01-30 12:36:21 +00:00
ocata	Sync charm-helpers and use "rabbit_use_ssl" for ocata	2019-08-01 23:00:16 -04:00
parts	Allow specifying default_volume_type	2020-08-19 17:51:35 +00:00
queens	Add policy to allow owner to force delete volumes	2019-02-08 07:32:20 -08:00
ports.conf	Disable Apache port 80	2020-01-27 17:33:51 +00:00