* 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: Ie133bc41bf789e07d4d777e128617b21d822de30
- 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
- sync charmhelpers
Change-Id: I359df29fb7c86caf0c29c7f35c3e4b68392ba5ad
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: Ic7cf54d7669219f4a42e08c8a1e2adb786a16af6
* 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: If7019d54b67c10407c0db5fac098aa9cee993f1c
* 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
Change-Id: I6027b4bb12dce36a7b10df2e14cafd5dc6ee963b
Unit tests generally will all be executed, and measuring them will
skew the overall coverage numbers. Thus, I'm excluding the unit_tests
folder.
Change-Id: I71c133b14eb21986875a52dcd2e883b0db306540
This technique was borrowed from the tox "cover" environment in
openstack/nova's tox.ini. This leverages the fact that stestr lets
you override the python executable via the PYTHON environment
variable. Doing this allows us to easily generate coverage for our
unit tests.
An important caveat is that this does not provide any coverage for
tests via zaza, amulet, etc. It is purely focused on the unit tests.
Note that this replaces the previous .coveragerc; coverage
configuration is instead pulled from tox.ini.
Change-Id: Iaa61e7b2dd9f5ce6cebbd43af9c59c9b04a3547c
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I2c180a54b4105c4167273671e5063db61a1cb419
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Switch package install to Python 3 for OpenStack Rocky or later.
When upgrading, remove any python-* packages that where explicitly
installated and then autoremove --purge any dependencies that are
no longer required.
This change also switches to using the cinder-manage binary in
preference to using the internal API of Cinder to query and manage
services in cinder, avoiding the need to continue to have python-cinder
installed for charm usage.
Change-Id: Ie8f7d2d7e1ef7b3065d6d9ed244e5fd05e2f613b
As of pip 10.0, --allow-unverified is not permitted.
Use of the flag in this repo was previously used to force
installation of python-apt to accommodate certain unit tests.
The unverified package, python-apt, is no longer necessary
for test execution.
Related-Bug: #1760720
Change-Id: Ia2e678723fd7769d037df336b992bdcc67be4948
Includes charmhelper sync and amulet test update to switch
to api version2 on Pike+ as v1 has been dropped
Change-Id: Ib7fac99f6987947dec9a09ef8354003520688b6d
- Turn on Zesty-Ocata Amulet test definitions.
- Standardize test-requirements.txt
- Sync charm helpers for various fixes
Change-Id: I931fe3cf63b5bdf1ecb62c6f41a7d83bd1560350
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
Change-Id: Ic227ce03c1acf6de9b5f83953d6390d66cda190c
Related-Bug: #1659575
All OpenStack Charms now contain identical tox.ini files,
not to be modified or made unique within each charm repo.
This is to ensure consistency across charm repos in tox
target naming, approach and purpose, also giving the
charm dev and test experience additional consistency.
Also create empty dirs with .keep files where necessary.
Some classic charms have actions and/or lib dirs, and some
do not. In all classic charms, flake will now check those
dirs to ensure lint coverage of existing or future content.
Change-Id: Ibc97c71eba9a64969fc3cfe5fc6ddd2c867cc0b8
Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.
Rename amulet tests inline with gate-*, dev-* and dfs-*
naming standards.
Update README to refer to functional testing section of the charm
guide.
Change-Id: I6d9582386b77cae8a00726760dc7cead85af7527
The new release of charm-tools no longer ships the charm
command; update minimum version requirement and switch
to using charm-proof instead, unblocking current pep8
failures across all charms.
Also pin the version of requests to 2.6.0 until theblues
(indirect dependency of charm-tools) sort out its
requirements versioning.
Change-Id: Ib0f6c7400b443413bbf857ad087d16f7ac4c81b1
Alex Kavanagh