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.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1108
Change-Id: I782890f44628a634c7adcf9cdace753c62d6c262
Extend ceph-proxy to implement ceph-mds interface, this allows the
ceph-fs to be related. The testing is made reusing the CephFSTests
testing class.
Usage example:
juju add-relation ceph-proxy:mds ceph-fs:ceph-mds
Co-Authored-By: Felipe Reyes <felipe.reyes@canonical.com>
Closes-Bug: #1922195
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/558
Change-Id: I437dbac9fe018eb2d0ffb87052d61a08aa014473
- update bundles to include UCA pocket tests
- update test configuration
- update metadata to include kinetic and lunar
- update snapcraft to allow run-on for kinetic and lunar
Change-Id: I583679055cd8add80321282edd7ec12eaa5826fc
* 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: I78b0720e75891a41364ba0ddb82add89c3b77ca1
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: I17cb0cfe88be075d79d94edcdd2cea845bf78b8f
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I744188799db42ea9960ea35c1e83e773c6a2ee36
- 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: I1b49dc4f3e24483d7a64c6d9c2c55634e3b526e0
This patch adds a focal-ussuri and bionic-ussuri bundles to the tests
for the charm.
Also removes 'admin-token' from the tests, as the keystone charm no
longer accepts the option.
Also, for focal, btrfs-tools has been removed and replaced by
btrfs-progs; thus these are installed on focal instead. See linked Bug.
Closes-Bug: #1871712
Change-Id: Ifc79beebb981571cebc38be6cb6c2748d22816c9
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: Ie306d2caaafb16eff0ee4481a691c1f5a2f31cf4
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: I30800945c7799727f19731f04b61972148df830c
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: If892cf5e5b045300433dc2737f3b8b479d12527e
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: Ia0ea3d0ce22856c9a705417f258b6d0484bb0882
- 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.
Change-Id: Ia63b663255f5dc52a2a755e8c309b05ba8662a6a
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: Ibbb4cfe533b607f394fbffab6310a18bc667886d
Juju 2.0 provides support for network spaces, allowing
charm authors to support direct binding of relations and
extra-bindings onto underlying network spaces.
Add public and cluster extra bindings to this charm to
support separation of client facing and cluster network
traffic using Juju network spaces.
Existing network configuration options will still be
preferred over any Juju provided network bindings, ensuring
that upgrades to existing deployments don't break.
Change-Id: If4ce1ef545638130cb7e5f0d77b949d9b2e28090
Add the "osd-devices" block-type storage, with
minimum of 0 and no maximum. Volumes assigned to
a unit will be added as OSDs.
Also, add the "osd-journal" block-type storage,
with minimum of 0 and maximum of 1. The osd-journal
storage, if supplied, will be used in favour of
osd-journal configuration if supplied.
For now, handling of osd-journal is static, just
as the configuration method was before. Removing
or adding the journal after deployment is not
currently supported. This is possible with further
changes, but requires stopping Ceph and migrating
the existing journal, and so out of scope here.
Zuul