To make tests faster and more robust, avoid creating an additional LTS
image. Also remove obsolete test bundle options
Change-Id: Icea61ae71980a7fcc18b3898c2913d47339e05f6
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: Ia36919df21c55bfc40497f7c174ba5919f44a394
- 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: Ic9c1aef2b8c81bf53be3a18ca2806c69ce618f90
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1074
Change-Id: Ie39cef6965c30f2adb78b4be568ced17a140115b
* 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
* fix poetry-core addition in wheelhouse
Change-Id: Ia2ad44152cf620e9812bfbd58276735a7491949c
After Octopus, the reporting about image states fails because of a
permission issue in Ceph. This change disables that status reporting
to allow a deployment to be healthy even when some tools cannot query
status.
Also modernize build and func testing: remove python 3.9 and xena from
tests
Related-Bug: #1879749
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1063
Change-Id: Id86fc043495b89609cf6873ec58aee1e2e388578
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
This change also switches away from directory backed OSD devices
in the test bundles, as they are not supported anymore.
Change-Id: I57d1b47afbbeef211bb777fdbd0b4a091a021c19
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.
Change-Id: I53d0b42b43731ac06d96932f3dcf72c116f360f3
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: If26550f2a6aca4f2e7b8a532e924f640d967950f
* 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: I388df195df1294f0fc92bcf06e49e1a207fc6510
* Add optional parameter `pools` to the Juju actions: `resync-pools`,
`status`, `demote`, and `promote`.
* Add `bionic-train-image-mirroring` to the `gate_bundles`.
Change-Id: I9df77be628718bb60a1bdc65078c94d0b7bda9d4
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/486
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I7fce00f968b540d0a5824a2df262f0195bae8739
* 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: If51c83b121eb90308d2e87ca06c73f826a5ce359
cinder-ceph/ceph-mon could now refer to:
- ceph/client
- ceph-replication-device/client
- juju-info/juju-info
Change-Id: Id39640c0084992284a976c3cb02233e3ae6e20fb
Change-Id: I423eb38f5197879c5f8f7999acb11ece3d26a6a4
Co-authored-by: Marius Oprin <morpin@cloudbasesolutions.com>
Signed-off-by: Marius Oprin <moprin@cloudbasesolutions.com>
Drop support for forwarding requests for manually created Erasure
Coded pools. The initial implementation was based on a incomplete
implementation of EC support in the supporting libraries.
Make use of the forwarding of broker requests to support both
BlueStore Compression and Erasure Coded pools created through
the broker request protocol by charms in the source model.
There is currently no support for forwarding or influencing these
properties for manually created pools.
Depends-On: I0d4ed457e1d59eabed3340f5dc7d8353d5d66f04
Depends-On: I16196053bee93bdc4e5c62f5467d9e786b047b30
Change-Id: I19f66f8594b9bdada5365582ce98365039235f9d
* 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
Add master branch charm-helpers to wheelhouse.txt to support bluestore
changes in charms.openstack.
Change-Id: I1cb0d616a3d3033d6948677326062e0eb785c2a0
This patch updates the bundles to include up to focal-ussuri.
The focal-ussuri bundle is in the dev bundles as it can't pass at the
moment due to LP: #1865754.
The bionic-ussuri bundle is in the dev bundles (i.e. not gate) as it
fails due to LP: #1892201
Also deal with the related bug where cinder-ceph requires the relation
with a nova-compute unit.
Related-Bug: #1881246
Related-Bug: #1865754
Related-Bug: #1892201
Change-Id: I0a6f1de82ecc601509822277d657485e08dc893d
A side effect of adding a config keyword in layer.yaml is that
any deletes done by upstream layers are overridden, so we
add the complete set of configuration options inherited that
should not be included in the built charm.
Change-Id: I91e4e52600e7d632bbcf62402e57ebf69b6a3ea5
Closes-Bug: #1879088
- 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: I6772e104b883b79cf85b5c19dc401b431c087878
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.
Change-Id: I7c47c5d8db06ce2a206eed9f617a2eff86088a9f
Closes-Bug: #1881246
This project already had the disco-stein gate test, but since this
change is part of a batch change, I had keeping the same title.
Changes:
- 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.
Change-Id: I477d789cca10e9b714771c1419fe355bf44e4b6a
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: Ie196f329f2f5b98960c895e2bfcf0ea8082ee2b4
Do not rely on system installed Python packages but distribute the
direct charm dependencies as part of the charms wheelhouse.
As the span of distributions we need to support with reactive
charms widens we will run into compability problems with the
current model.
For further reference see juju/charm-helpers#341 and
juju-solutions/layer-basic#135
Change-Id: I129ca4506e44abc1e062d5545ff52f992f86a3b9
Peter Sabaini