Summary of changes:
- Update the charmcraft.yaml file to use base and platforms, only
allowing noble support.
- Update config to default to caracal.
- Update osci.yaml to use the charmcraft 3.x/beta
- Drop non-noble tests
- Update constraints file from -2024.1.txt to -noble.txt
- Add charmbuild to .zuul.yaml
- Add rename.sh to build process
Change-Id: Ia22e04e6da00eb176558d43f09c967d37f2366f4
- Removed pins to old version of setuptools
- Added py312 section to tox.ini [testenv]
- Updated flake8 to 7.1.1 instead of 3.9.2
Change-Id: Ib73053351a8a3daddfd989251999e1e5873357de
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: I4f5df7cd306e69210b53e2c800de609337e8c84f
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: I83fe6b1d397299c716bf67b11d1d30167a87ea84
* 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
Change-Id: Ic07c734001c56f26d6980934005ea8cad8588c4f
Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10. Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.
Switch to using a binary build which allows pip's dependency
resolution to work.
Change-Id: I6ab47c1c94249c194bf55650e26737fefe5838b3
* 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: I054650d578c30b5c865cbd7a567eb5d7c8032d01
Prior to this change, big bang upgrades were not being run
when openstack-origin was updated to a new release.
Closes-Bug: #1979553
Change-Id: I3a9d0211bede8db43cd5ae8e0db51736155282f6
- 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: Ib993e07f73d694d9d0189dc55d6ab1e3c9d31938
Currently, this charm sets the host_href config option with the
admin endpoint. This patch adds a config option to allow it to be
configured to use the public endpoint, so that the secrets could
be accessible through this endpoint.
Closes-bug: #1642769
Change-Id: Ice7131459753f15e1184c687a24301689df338e2
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: I826947b1b358c4b04ba18135035292e135cce985
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: I2f54eb8f1fae913603f8692986361b88a32cc221
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: I9e922e77175fb117a2d98a3c42f2cddfae0dc326
Upstream Barbican has bumped up its default for the configuration keys
max_allowed_request_size_in_bytes and max_allowed_secret_in_bytes to
25kB and 20kB respectively (c59f2a6b). This change adopts those values
to be used in all the supported releases and exposes them via juju
config.
Closes-Bug: #1946018
Change-Id: I3dcb30f5de6367de2aa5c26bb59a79893fb8e578
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: I65a7403ec68d8be880e418bc4fca1b1fdffe6eb9
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Ic2d80c0c1eb8e22408ce363fd05b5d66d1d93e4b
* 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: I0f28e1e28ee9cb5712ef5b7b007903d317a5f61a
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Ied3c4d70fb5a7cf2556a4ca7d9c0aec551b63939
* 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: Ie41022bf94c69019799d87abf138228ff27dddb8
Without db_auto_create = False each barbican-worker attempts to run
alembic upgrades on the database whenever they start. This leads to
race conditions that can leave the sate of the database broken
(multiple alembic version that "overlap").
This change runs the barbican-manage db upgrade by the leader only
avoiding the race condition. charms.openstack also handles the
openstack upgrade process with a call to instance.db_sync.
Change-Id: I6b9498059c7057b73b1c3db0e355456c38b0510e
Closes-Bug: #1827690
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I69fab5d73305dfe1eb0563d5e570ef76b64e5d64
Also updates for testing period for 20.01 release.
All these changes are needed together in order to have passing
functional tests.
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: Ieff90482f0acfac735c1ed69fc0593bd44913bac
Closes-Bug: #1903725
