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
- 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>
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
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
This is to resolve the associated bug where cinder-ceph has grown the
capability to block if it doesn't have an appropriate relation to
nova-compute.
Also remove the trusty-icehouse bundle as it is not longer supported.
Note, on trusty-mitaka, the nova-cloud-controller is needed as otherwise
nova-compute complains and then dies, leaving a nova-compute service is
not running in the status message.
Also, change the detection of the status messages for the radosgw charm
as it has changed during the dev cycle.
Change-Id: I072b79705a6a7dfb0d5cbd16095e6ececb432ec3
Closes-Bug: #1881246
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
Also clean up pre-existing pep8 violations in the
files/* dir which was previously not covered by lint testing.
Also clean-up mocking issues around apt-pkg replacements in the
unit tests.
Also fix py35 issue with enabled_manager_modules() function in the
charmhelpers library (see
https://github.com/juju/charm-helpers/pull/387).
Also fix the functional tests bundles so they actually test the
version of OpenStack that the bundle indicates.
Change-Id: I2c8d84fadc11311c622dd308c4694496872dc157
Tests.yaml was missing a parameter, causing
zaza to pull latest ceph-proxy from charm
store instead of using the changes of
patches proposed in gerrit.
This change fixes it, now zaza deploys
ceph-proxy from local repo created
during tests that contains the patch
proposed in gerrit.
Change-Id: I3681e72f032780b864d02a95cf983f26a0b1c91e
The bundle disco-stein was in the dev bundles because
a bug with the Python 3.7 syntax prevented the success of
the deployment of HA clusters. This bug is fixed, we can
reintegrate disco-stein in the gate bundles.
Other small additions:
- Passing OS env vars instead of AMULET
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
- adding bionic-stein bundle to gate_bundles instead of dev
LP Related-Bug: #1823718
Change-Id: Ia7093a5654a763670be05635f7f6fce292eb9c96
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
Drop explicit install of python-ceph; ceph-common has an
appropriate dependency on the required python{3}-ceph package
so this is not required, and breaks on Stein where Python 2
packages are no longer provided.
Closes-Bug: 1824154
Change-Id: Ia219258f73f038170bc5a070d562e499459fe246
Add a tactical change which is already merged into charm-helpers.
This needs to go into all charms to solve the chicken:egg issue
where cosmic is untestable until this change exists.
Reference:
4835c6c167
Change-Id: I91df2da7be9521689372a2be5f6b7220fee449dd
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
Due to changes to the ceph-osd charm, it is
suggested to use Juju storage for testing.
Change-Id: Icd1b53d8672271a5350b630f14f20bbd3b6c8740
Related-Bug: #1698154
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
Corey Bryant