These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal. They do NOT lock the charms
down, and don't change the testing branches to stable branches.
Change-Id: Iab51a774517ee8bd397eb900bd76a0620aa3dd6d
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: I1fe8dfc4744e71700a4546f80a83e0ab1ddca2aa
There is an improperly formatted comment in a Jinja2 template.
This causes Juju hooks to fail with a template syntax error.
Closes-Bug: 2025507
Change-Id: I8d3758e52252d8f1d171de83f614aa4a611d98e8
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
* Add libpython3-dev to allow the charm to be built. This
fixes a missing dependency with Cython
Change-Id: I102ee0648ffbbed87df5b3de6cb964ee6fb90744
* 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: I3cc0af8443ecf62589c88d4e924cb633c419e87f
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
Change-Id: I055353bc78607119b0647bed87ca806f0ceffc62
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
Change-Id: I05dbf9cbfd3132b1970ca9cd9de111d6879f1582
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
* add nrpe to bundles
Change-Id: I184e4696336378f8e2b02ff6ce8800c224249e47
Closes-Bug: #1925977
Changes project_domain_id and user_domain_id to *_name in manila.conf
Add defensive mechanism to fallback to `_id` if `_name` is not set
Closes-Bug: #1911424
Change-Id: I6240b7b7e4590a21f034b9c70247e87ec18d867d
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].
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I70c579bc425746b30be12cb30e660542da842c48
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I809f8b581a7e86d43acb8115c3d0e609285d9bd8
* 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: Ied9b83ce5c57f370bd4d673964dcc433519ea8b3
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: If0b6b73e75e51230f6b3330754c12b9ad10540f8
* 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: I1024115390e26e4c71d97d8ba37204c530b7b28a
Also switch the smoke bundle to focal-ussuri as that will be the LTS on
focal.
Change-Id: I91ae66a5903c23c663243dfd10270d04325e5e39
Closes-Bug: #1879684
- 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: Ic72f5a398b738ee909d07d48a416fcf18d50f218
Due to the ha change in charm-manila [0] xenial-mitaka and xenial-ocata
are no longer supported by manila. Hence remove them from the gate.
[0]: I1f501283db3db1338d47a89a7688cf5035d08a7a
Change-Id: Ifcd489d1c58abba7776dcd1c2b56777e552539a2
This patch also updates the smoke test to run train.
Change-Id: I82729f83e846976908fb7446c150c57a9eb3fdad
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
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:
- 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.
LP Related-Bug: #1823718
Change-Id: Ibc953a7da04fb6f8851c1698054542d7b1f1bdb0
Also explicitly set ``include_system_packages`` to False.
While that setting is now the a default we consume from
``layer-basic`` it is more clear for the causual reader
of the charm source code.
Remove redundant entries from ``wheelhouse.txt``.
Change-Id: Ib1c2f5b7f8051c9dc9f1da9f320810741d0cf637
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: I2d83b5a98e82f3120952178494884f3f1e3ca2b9
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: I2d728072bfca20e612c2d4c9178095a22f83631c
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: Ic9170de585360251f6bca8b033c53d668c0c13ce