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: Iffc97e7963469742439da25040e204fd27000976
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
[1] https://github.com/juju/charm-helpers/pull/824
Closes-Bug: #2028683
Change-Id: Icb53c57de58571635ff575d9c23e7f9858be236e
* 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: I83b97c35b6e64050feaa94a2eee2b80fa49c2555
This patch adds kinetic to the metadata.yaml and ensures
that a run-on base for 22.10 is added in the
charmcraft.yaml
Change-Id: I3f2ed3df8cc5f076402f68b18e9f2de66ae23007
* 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: I2cb698f719106e54b06009f24ea47259419e9cad
- 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
- Remove overlay as no longer needed in charmhub with explicit .charm
- Pin setuptools < 50.0 in src/wheelhouse.txt
Change-Id: Ie15e3e0530345f488565454e673e40981f606bdd
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
Depends-On: https://review.opendev.org/c/openstack/charm-nova-cell-controller/+/830520
Change-Id: I47fd77c67776817f7b8d8918f0ec29d420f1763a
nova-manage uses the [database]/connection to determine the
database connection. This change updates the nova.conf
template to use the parts/section-database template,
switching away from using [DEFAULT]/sql_connection to use
[database]/connection instead.
[DEFAULT/sql_connection has been deprecated since at least
mitaka:
https://docs.openstack.org/nova/mitaka/sample_config.html
This change also re-enables the gate tests for Xena.
Closes-Bug: #1951874
Change-Id: I9d77b44ad3c40f3ee60fedc3f211f3ac085fcbb2
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: I821bf39f976be059f6e7e03b337d6f323787dcb0
* 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
Change-Id: I6d7d32dd016e436d8463f88331682f53c4741e8d
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: I259256fedb52f424535cba3c5e78ac53516989f2
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I233ad706c70123a2613ba5ec6463f60ef82123cc
* 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: I0b89619963f796132356b174f7bd9f3a85a681f4
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I306cd021e4038a50dc2763e65da93253edd87e9e
* Update requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
doesn't get 'builds' appended. The tox change puts it
back so that stable & master both build to the same
directory. This may be reviewed in the future.
Change-Id: Ieae91b9ffda65f21741f742e03662cdaf73b3177
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: Idabe1d11d7410622aeb4455c0fe24503f8e502a9
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: Id9d36ae950300b1c3f461928908e56bd2d49b37a
* 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
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/440
Change-Id: I10a6a748b8fee04a0395da37d599e0c50d28f01c
- 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: I02183a592035b37bad6fa568bfcf9fdf20322b50
Fix regression in layer-basic which failed to unpack new dependencies
properly during the upgrade-charm hook.
Github Issue: #166
Closes Bug: #1875496
Change-Id: I5df34b0439cb92db558db0cc9b1bcf620318aae4
Use default_update_peers which will publish admin, internal and public
addresses to peers.
Change-Id: Ibb9d67095c85f0486d24bec01c356c7e7bfb008a
Closes-Bug: #1858132