8fb37dc0c1
For principal - subordinate plugin type relations where the principal Python payload imports code from packages managed by a subordinate, upgrades can be problematic. This change will allow a subordinate charm that have opted into the feature to inform its principal about all implemented release - packages combinations ahead of time. With this information in place the principal can do the upgrade in one operation without risk of charm relation RPC type processing at a critical moment. This makes use of https://github.com/juju/charm-helpers/pull/643 This is similar to https://review.opendev.org/c/openstack/charm-keystone/+/781822 Also fixed broken link to charm-guide. Change-Id: Iaf5b44be70ee108cbe88b4a26f0f15f915d507fe Closes-Bug: #1927277
11 lines
490 B
Markdown
11 lines
490 B
Markdown
# Overview
|
|
|
|
This directory provides Zaza test definitions and bundles to verify basic
|
|
deployment functionality from the perspective of this charm, its requirements
|
|
and its features, as exercised in a subset of the full OpenStack deployment
|
|
test bundle topology.
|
|
|
|
For full details on functional testing of OpenStack charms please refer to
|
|
the [functional testing](https://docs.openstack.org/charm-guide/latest/reference/testing.html#functional-testing)
|
|
section of the OpenStack Charm Guide.
|