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: Idd4eb37dd413b49a99b8b81fd15d0b45f75ae97e
Add 23.04 run-on base and add lunar to metadata.yaml.
Drop 22.10 run-on base and drop kinetic from metadata.yaml.
Charm-helper sync to pick up Antelope support.
Change-Id: I8a4f42249a8607c5d0baf3b9f19d8edd663ec1ca
Add 22.10 run-on base and add kinetic to metadata.yaml.
Sync charm-helpers to pick up kinetic support.
Change-Id: I26aaceb01f16ddb31123a37454a9cf0d61ed384c
This reverts commit c0beec6fa2.
Reason for revert: I think this should be reverted as it removes focal support from the rabbitmq-server master, and thus this won't cherry-pick cleanly to the stable/jammy channel for the 3.9 track.
Change-Id: Iebab77fcc0cee31af66980c2d3be334fffe06222
* 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: I93da9ce52bed2b3e8a467491d2a61bfd2ed4ea7d
Enabled rabbitmq_prometheus plugin for prometheus to scrape
the metrics of rabbitmq and alert if rabbitmq splitbrain is
detected.
Integrated rabbitmq dashboards in grafana via dashboards
relations
Added new unit test cases
Closes-Bug: 1899183
Change-Id: I88942dd0b246c498d0ab40b00d586d4349b0f100
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: If003131e8a1bde58d90b1a3b1e47801bbb044335
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Ibc3597cd9aadb9662b56cacf40c5ac6ee0650b42
- 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
Change-Id: I02bdac24d05ae34ef3519963ef95bb53bdbbc2fc
The patchset adds ussuri to bionic and focal-ussuri tests. This depends
on the linked patch below that adds initial focal support to the charm.
Depends-On: Ia239b7c2f0ed2383e220cf0fa4ade443149a3b32
Change-Id: Ib65896cd433a2108a154e18cae6f0089b5e3f44a
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: I3d88b0642d98d786a15a0ac5c8d5ec898c74d9fd
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: I71eb7e91d0cbdd66acc6551499e41c9d1065f06d
Add support for rabbitmq using the certificates relation
to secure traffic with clients. Support for users supplying
their own certs and for rabbit acting as its own Certificate
Authority should be unchanged. The follwoing additional changes
were needed:
* Charm helper sync
* Update rabbit to use get_relation_ip from charm helpers which
is the standard helper for calculating endpoint ip addresses.
* Create network helpers file to avoid circular dependancies.
Change-Id: Ie60893e660efe1f8b0a0d42aaaecfbd9aae6f97c
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: I6f24a3122c42149348c73661288fb0aba2b939dd
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: If2923103254a4816e188407379307425020a931d
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
- Tweak functional tests for ocata changes.
Change-Id: I87e1759deba6877373c48a49e676e5b1766611d2
The charm store does not yet recognize this series, and errors
when it exists, thereby preventing push/release of dev charms
into the charm store.
Revisit after the following is resolved:
- https://github.com/juju/charmstore/issues/695
Change-Id: I9b6bfbdfe7f91141e46094e1b1875eefa7be4863
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: I168a0dfac64e9e21fd95e753a152310923353d8b