* 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: Ida68ffdab34c3136f3acf98629e4be6fda3bcea2
- 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
- charmhelpers sync
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/747
Change-Id: I8bd5e6f5d002fbd1118f2c7fa54e50f1b31fc722
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: Iee7fb24e06d23b3fbf35f05e7931dbdc25b37d64
* 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: Id4a36b0f41d2644a94d266ca1990a270e4e7452f
* 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: Ib702ce2d31f41cf779c2372b69c4d53f82e9e1eb
This patch also updates the smoke test to run train.
Change-Id: Ic7ed2a3c12df08dac2a056bb08c5ef87768f8e47
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
Also clean up pre-existing pep8 violations in the
files/* dir which was previously not covered by lint testing.
Change-Id: I443a084681d5788c89cdadf2ff999030f4b4d735
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: I268df41f6f775560580b49fa60f717ba8da88def
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note that python35-charm-jobs is retained since this charm is supported
on Xenial.
Change-Id: I72638af28accb42482caf43e78d0418f1b722e89
Story: #2005924
Task: #34228
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: Ibb6306a45f35c1a22794e1a019bb357831442df4
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: I2f4357b4168a1142950f12304932d8f559f380fb
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Switch to using python3-{nova,neutron} at OpenStack Rocky; purge
previously installed Python 2 modules on upgrade.
Switch default test target to bionic-rocky.
Change-Id: I0a2b48bfc8c950efea3e83c74ec3eb6dd43796c4
Inline with neutron-openvswitch add support for use of existing
linuxbridge's when wiring openvswitch bridges to underlying
network devices.
Change-Id: I24281e8c31d9a140dfdaff308e6e99d3ce162fef
Closes-Bug: 1635067
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: I91129b9f1667116a20f14ae76994d90447e95317
Refactor codebase and unit tests to default to execution
under Python 3.
Drop install shim as Python 3 is always present >= trusty.
Drop legacy dhcp and network reassignment code from charm as
a) this relies on a py3 neutronclient (not supported on older
releases) and b) this function was superceeded by the ha-legacy-mode
and then neutron router and network HA built in functionality.
Use charmhelper provided get_host_ip as this superceeds the in
charm version of this function.
Change-Id: I0b28bf0851d44e85b1e856cbd97b71099faa76ae
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
- fix tests which assumed mocks would just work on os_release()
Change-Id: I9c0dae8a37ded6536dc2b0c53e06647f380c48b0
Related-Bug: #1659575
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
- Update tests for ocata changes.
Change-Id: Iea2ee8a6a482c2eb12d695123a908ee4402722df
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: I95470bdd2d544e657ceccb240235e734a70987ee
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.
Change-Id: I02bb4fa2978c548d8d8df00ce3add2b98bb65593
Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.
Rename amulet tests inline with gate-* and dfs-* naming standards.
Update README to refer to functional testing section of the charm
guide.
Change-Id: I9b36f8a6375da5cf5807d51e1d009c47d74dc1dd
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: Id04a1238b4460ba4c4de6549c6fe937cb90d9d9d
Alex Kavanagh