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: Ib7947ab8dfd4c4b18c482f4df1a7c6f5b5e3756f
Unpin the versions of tox, setuptools, etc. This removes the issue
with tox 4.x breaking the virtualenv dependencies.
Change-Id: I103e16c70aee394331b37ec0cf323e014011d3ae
* 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: I506c53b4956024066bc769665525cb022438a0ae
- 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: I62d95763a6283d8dc7f54b65b0474d48b20608f0
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: Ic9e267db4934cb95125eebb2ff3b1ca09d64e003
* 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: I79af80dd7a0faa9175c9dca1fac669f8c187e3f5
Update pydev project definition to use python 3.
Drop upper bound on flake8.
Tidy misc lint across codebase with newer flake8.
Change-Id: I9637ac603cb3801c9e3ffa8c2b0897968d42ada5
When the VNC server is set to bind to 0.0.0.0,
unauthenticated console access is possible to any
VM via any of the compute host's interfaces. This
access should be restricted to an internal network.
Change-Id: Ibbc12ae282320f966eec90e9116388233e65eb9a
Closes-Bug: #1843004
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: I58b115a17cf4293db6c8a0c1cd553f20fa4a3894
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: I237b056a9bc0072b956f4c47ebb1363d90c8d0a4
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: I389421cce9c131ea8b9f4b1527a8bccd9f2b8a5a
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Switch nova installation to use Python 3 for OpenStack Rocky.
Purge python- packages on upgrade.
Change-Id: I7839c823d51f6a3d166157be19f2e93b8dd72305
Depends-On: Ic5e96336b6a2ca474fc28d358553c6a05e1a75ce
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: I42387c238e74415ccaf5adb5182ae252bcbf10bf
- 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: Iffd4ed0aecbb966fe493fe0f24bf2422aab55bb6
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.
Change-Id: Ib07bdddd6e79f73785105ba4844c7aca654231b0
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: I3d2a570b86c8889704f84b311abacc3acc316e3b
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: Idac55f55d0827053ca7ec51cd06db6d4fa3317f8
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: I60befab62843fa439a6a1fc897851091e4d47d49
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: I35697797e797ef504ea2f7c86185e98abb935c63
Alex Kavanagh