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
Summary of changes:
- Drop 'source' override in mysql-innodb-cluster and rabbitmq-server
- Fix 'openstack-origin'
Change-Id: I19faecbcfebdaf5dcf0d0346c5d0b0eed02866aa
This unpinning is meant to solve the issues with tox 4.x breaking
all the virtualenv dependencies.
Change-Id: Idd02728e33be4931c7729c218629b7a8430d0f41
- 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>
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.
Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I33cd69aca44f48af2766c92ede46ff12367160c5
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I191a4ac0c66f2e5d36cc941d5eb2809408a89320
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Sync charm-helpers
Change-Id: I01125ce328091db86c757d5ee14e3f3eaa913d73
The 'hirsute' key in c-h/core/host_factory/ubuntu.py:
UBUNTU_RELEASES had been missed out, and is needed for
hirsute support in many of the charms. This sync is to
add just that key. See also [1]
Note that this sync is only for classic charms.
[1] https://github.com/juju/charm-helpers/pull/598
Change-Id: I75107c4fd927f95eb3778b65a2172b0268390feb
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: I493cb80145fe91163d011bc78f30e84f317142de
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
The network-get --primary-address juju-info fails on pre-2.8.?
versions of juju. This results in a NoNetworkBinding error.
Fallback to unit_get() if that occurs for local_address().
Change-Id: I309ef298fecfe8d5cb2fd4c3322c3d734094f5d4
Includes updates to charmhelpers/charms.openstack for cert_utils
and unit-get for the install hook error on Juju 2.9
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I40621954e3108f73b79257755aa518646e52c88f
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I73cdbc4f9a444cb3bc5e9daa4d1cc038b5ed26c5
Process requests for radosgw per unit keys. Ideally the charm
would move to using charms.ceph.utils for the get_radosgw_key
method but this does not work atm. I have raised bug #1899643
to cover deduplicating hooks.ceph v charms.ceph.*
Change-Id: I00f5a58f127baa1f7878b0ddb31b4fa009d9651e
Closes-Bug: #1899634
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I512ef8bbb52c08e782c66450b435a40a76b8a532
Changing an existing EC profile can have some nasty side effects
including crashing OSD's (which is why its guarded with a --force).
Update the ceph helper to log a warning and return if an EC profile
already exists, effectively making them immutable and avoiding
any related issues.
Reconfiguration of a pool would be undertaking using actions:
- create new EC profile
- create new pool using new EC profile
- copy data from old pool to new pool
- rename old pool
- rename new pool to original pool name
this obviously requires an outage in the consuming application.
Change-Id: I630f6b6c5e3c6dd252a85cd373d7e204b9e77245
Closes-Bug: 1897517
Drop use of local copy of ceph_broker.py in preference to the
centrally maintained copy in charms.ceph.
Change-Id: I89aa0f9fc7d5d2d480ebabc1cb17a86dcbef21bf