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: Icf59d65f7938a9a72a0dca87dfbcf13118fabea1
This reverts commit 527261db5c.
Reason for revert: I'm not sure that this should have been merged; it removes support for focal, and that's needed on the 2.4 branch; thus this couldn't be a clean cherry-pick to the stable/jammy branch.
Change-Id: I5b53d552961d39bda91ef97f425123c1bab7e349
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Change-Id: I1a250a0591c15971840bbd6130c7cff3822eed4f
* drop trusty/xenial metadata and function tests
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: I51ed5c7fdb98dcbea72298da956a66b411fed03f
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I6a2826378462a0742a9db638cf3b4c7438f42e13
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/306
Change-Id: Iaa22ef4359203e3b5f8de51f66e3340dbd8ae544
Note that this is NOT the focal testing enablement for the charm. This
is a sync of charm-helpers and a add of 'focal' to the metadata to
enable testing, and landing, of other charms' focal functional testing
enablement. focal testing will be added soon.
Change-Id: I4c9d53588620bf6080cd9f6c405ee222d2cb3561
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I97d1a1381314ce6dc0952ef75f7936ccc9fcf212
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I8ce82a8a620a33314fc2bc612fbfd3f09acd576f
This change adds support for pacmaker-remots joining the cluster
via the pacemaher-remote relation. The pacemaker-remotes can
advertise whether they should host resources. If the
pacemaker-remotes are only being used for failure detection
(as is the case with masakari host monitors) then they
will not host resources.
Pacemaker remotes are managed in the cluster as resources
which nominally run on a member in the main cluster. The
resource that corresponds to the pacemaker-remote is managed
via configure_pacemaker_remotes and configure_pacemaker_remote
functions.
If the pacemaker-remotes should not run resources then the
cluster needs to be switched to an opt-in cluster. In an
opt-in cluster location rules are needed to explicitly
allow a resource to run on a specific node. This behaviour
is controlled via the global cluster parameter 'symmetric-cluster'
this is set via the new method set_cluster_symmetry. The method
add_location_rules_for_local_nodes is used for creating these
explicit rules.
Change-Id: I0a66cfb1ecad02c2b185c5e6402e77f713d25f8b
Add support for the hacluster charm to be related to a principle
using the juju-info interface using the peer-availability relation.
This is useful in the situation where a cluster without any resources
is needed.
Change-Id: Ibd03ba7923cfd2c412d5f772cf385a21c423e5af
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I88b4620bbef4ceee44af48a78e91a0f90578c449
Bionic, being the next LTS, is important to enable for dev
and test as early as possible ahead of 18.02.
Zesty goes EOL in Jan 2018. The next stable charms release (18.02)
will not provide Zesty series support, as it was an interim
(non-LTS) release.
Change-Id: I71a05a94d98f92b38744988e0a77702c554ef936
- Turn on Zesty-Ocata Amulet test definitions.
- Standardize test-requirements.txt
- Sync charm helpers for various fixes
Change-Id: Ibe6fffd7f615e43342b73258bde870dee9dcc5ad
This optimizes the publication process to the charm store, and
ensures that the charm code and version is consistent across all
supported Ubuntu series.
Change-Id: Ic47a12be9544de2cdff8e0ef2adf6bdbde0305ed
Peter Matulis