- Set default branch for git review/gerrit.
- Switch tests to stable.
- Switch to using stable charm-helpers branch.
- Switch to using stable charm.openstack branch.
- Switch to using stable zaza, zaza-openstack-tests
  branch
- (reactive charms) Add build.lock file

Change-Id: I40da506eeb9304b28a013299b380204e1cffcc3f

The bundles for the yoga channel currently point to "latest/edge"
channel for all the charms.  This update points the charms to the
appropriate channel for the charm being used, either from ceph,
openstack, ovn or the misc tracks.

Change-Id: If5e7f24744ba793a92958ddc4cec9bbb5bd2fc1b

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.

Related-Bug: #2002788
Change-Id: I499d3020fdfe449a2e5bb34a38146545020bf7e0

Add the 'docs' key and point it at the 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: I8105c5e90d0e8054f26f21fbd29cb80bebe7aa39
(cherry picked from commit fe0cfb0)

…relation

This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation.  Fix in charmhelpers is in [1].

[1] juju/charm-helpers#827
Closes-Bug: #2028683

Change-Id: I76e0c796b142ff1b0472f4c22986a10e0000622d

Added configuration for injecting default image properties using the
interoperable image import process. This change adds 1 configuration
option to the charm:
- 'custom-import-properties' to specify the desired custom properties

Note: current glance docs example shows incorrect quoting, the
implemented format in this change (no quotes) is correct. Docs fix
in: https://review.opendev.org/c/openstack/glance/+/890423

Release note: https://review.opendev.org/c/openstack/charm-guide/+/891010

Closes-Bug: 1994053
Related-Bug: 2028895
Change-Id: I9548c90e663285c6e7a70eebc8c135a5568974bc
(cherry picked from commit 0a1d645)

re-installation does not restore them.

Implemented a unit test function for the above
scenario.

Call apt_update from upgrade_charm().

Closes-Bug: #2042792
Change-Id: I57c5fa293b421483b0879f24ddac260e47c7cbef
(cherry picked from commit 59efce8)

Add configuration parameters cinder_store_user_name,
cinder_store_password, cinder_store_project_name and
cinder_store_auth_address to cinder volume type backend configuration.
This avoids a glance_store bug that prevents glance-api from starting.

Closes-Bug: #2052726
Change-Id: I4b6ca32ed426f77a326711c2457046dbda594e77
(cherry picked from commit 07da644)

For cinder volume backend sections, ensure that enabling internal
endpoint usage for service access does not completely clear the
existing content of the section.

Change-Id: I383a0794e924db3c7f4ce47d1e3b88355c2475e4
Closes-Bug: 2052726
(cherry picked from commit cfb228f)

…does not restore them." into stable/yoga

Change-Id: I1da63d318de21e266f8331a2c7a2d0fca0ecea73

This commit adds Keystone audit middleware API logging to
the Glance charm in versions Yoga and newer to allow users to
configure their environment for CADF compliance. This feature can
be enabled/disabled and is set to 'disabled' by default to avoid
bloat in log files. The logging output writes to
/var/log/glance/glance-api.log.
This commit builds on previous discussions:
juju/charm-helpers#808.

func-test-pr: openstack-charmers/zaza-openstack-tests#1236
Closes-Bug: 1856555
Change-Id: Ied08b56cf3c4fa30827d43a50ca7b552db0fa82b
(cherry picked from commit 66a167e)

* update:
  - charmcraft.yaml for v3
  - tox.ini to use py3.10 by default
  - test-requirements.in to use zaza for juju3
  - update test bundles to work with charmcraft v3
* generate:
  - merged-requirements-py310.txt
  - merged-requirements-py38.txt
  - test-requirements-py310.txt
* add:
   - update-requirements env to tox.ini
   - update-requirements-focal env to tox.ini
* .zuul.yaml:
   - switch to charm jobs to get py310 support

Change-Id: Ic847b5344e23976927dc8037fb410740fed46515
Signed-off-by: Munir Siddiqui <munir.siddiqui@canonical.com>

tox.ini needs to have env for specific Python versions as this
is needed by the CI Zuul jobs, e.g., py310, py312 etc. Since we
are using the same CI cleanup procedure as with other charms,
this may also modify requirements files, so we re-generate
them to be sure they are in sync.

Change-Id: Iab1e7082bf92e2e741eb09bcd51a6b374ae61bec
Signed-off-by: Munir Siddiqui <munir.siddiqui@canonical.com>