* sync charm-helpers to classic charms
* change openstack-origin/source default to quincy
* add mantic to metadata series
* align testing with bobcat
* add new bobcat bundles
* add bobcat bundles to tests.yaml
* add bobcat tests to osci.yaml
* update build-on and run-on bases
* drop kinetic
* add additional unit test https mocks needed since
charm-helpers commit 6064a34627882d1c8acf74644c48d05db67ee3b4
* update charmcraft_channel to 2.x/stable
Change-Id: I2d9c41c294668c3bb7fcba253adb8bc0c939d150
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: Id759ee81cea83fe9b18671ce5bc19a31db319a77
A new relation with primary/secondary nomenclature is added and the
old master/slave relation is marked as *Deprecated*. In future,
master/slave relation would be completely removed.
Change-Id: I9cda48b74a20aaa9a41baedc79332bfaf13951d3
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/926
* 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: Ieb1ef7b7ab76775f5769621a6a7cbcfb18c40b7f
Add a radosgw-user relation to allow charms to request a user. The
requesting charm should supply the 'system-role' key in the app
relation data bag to indicate whether the requested user should
be a system user. This charm creates the user if it does not exist
or looks up the users credentials if it does. The username and
credentials are then passed back to the requestor via the
app relation data bag. The units radosgw url and daemon id
are also passed back this time using the unit relation data
bag.
Change-Id: Ieff1943b02f490559ccd245f60b744fb76a5d832
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: If18475dd9a99c4a286bb2f5913f3ec4f2447c4f4
Implements the swift-proxy interface. This is needed in order for
the glance (or any other) charm to be able to consume RadosGW the
same way they would consume Swift.
Change-Id: Ia59e1286ca25a71bcdf74be38c9dffb07c5be64f
- 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: I156b0cecef76601ccc6f3a6714fc5118f6792b2d
This patch adds the following bundles:
* tests/bundles/bionic-ussuri-namespaced.yaml
* tests/bundles/bionic-ussuri.yaml
* tests/bundles/focal-ussuri-namespaced.yaml
* tests/bundles/focal-ussuri.yaml
The focal tests uses the force_deploy option in the tests.yaml
The depends-on is to fix very recent lint errors in charms.ceph with
E741 (very short variable names).
Change-Id: I46445da361e37716b65bf941f687cbd6468ed212
Depends-On: Id92956e52cefed6d3d792dd95fe7091788fb2d1b
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: Ib6244dc1f5f9c8a0eccbd8f95d5b4f39f7077510
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: Id28834a02b8d540ce23458813a5cf439931f1d59
Add new radosgw-multisite typed master and slave relations to
support configuration of separate ceph-radosgw deployments as
a single realm and zonegroup to support replication of data
between distinct RADOS gateway deployments.
This mandates the use of the realm, zonegroup and zone
configuration options of which realm and zonegroup must match
between instances of the ceph-radosgw application participating
in the master/slave relation.
The radosgw-multisite relation may be deployed as a model local
relation or as a cross-model relation.
Change-Id: I094f89b0f668e012482ca8aace1756c911b79d17
Closes-Bug: 1666880
Add support for the charm to request and receive certificates from
the tls-certificates relation.
Change-Id: I821ad15aa6af7eaf9d22a00e7d3fb79611d4b6b5
Closes-Bug: 1776643
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: I0ebcde2ca99a10a005a6448bca9be7ba40974fd0
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: I5585cb843ddf5d941c618829004bce3cf0bb1a82
- 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 resolving amulet full recheck failures.
Change-Id: I1864ee41be6815f9779669cab8ad8691bd78ffa5
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: I2ed40eefcd2e19cd2c0587129ed4d0b430e805b0
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: I0421eb6a4093793d7bda69b06ba4b976b2573e10
Juju 2.0 provides support for network spaces, allowing
charm authors to support direct binding of relations and
extra-bindings onto underlying network spaces.
Resync charm-helpers to pickup support in API endpoint
resolution code and add API extra-bindings to the charm
metadata.
Change-Id: Iada9f4d29cca9963900d4ec722c7681fa554b16c
Add support for the nrpe subordinate. Check definitions are past from this
charm to the nrpe charm
Change-Id: Icfeddc6ccbec2869a6f0880b4be0f67289d3b745
Closes-Bug: 1557611
Peter Sabaini