Fix key errors for rbd-pool-name and ec-rbd-metadata-pool
The existing code assumes event.params['rbd-pool-name'] and
event.params['ec-rbd-metadata-pool'] have a key. Set an empty string by
default to be filled by other part of the code.
Follow-up of Iec275190854edcc85915d93db233f444c92fbb17
"iscsi" is the name of the metadata pool by default in the charm and not
to be used for tenant data. The charm can fill out the data pool name
automatically with `def data_pool_name` or can accept a user specified
value. After fixing the issue, the "iscsi" pool will be used only for
hosting gateway.conf as a rados object so reflect the purpose into the
application name for the pool too.
Also, update the command syntax not to print the deprecation warning:
"rbd: --user is deprecated, use --id"
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
Change-Id: Ia414ab7d30db9443cf0d9d26071ca48b772f8d1e
(cherry picked from commit 41e3db8134c944fef0c83e5c26880157bcb8f453)
- update bundles to include UCA pocket tests
- update test configuration
- update metadata to include kinetic and lunar
- update snapcraft to allow run-on for kinetic and lunar
Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.
Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.
