See https://review.opendev.org/c/openstack/charm-guide/+/796639
Its functional tests are written with the deprecated
Amulet framework (replaced by Zaza). Our CI system
zOSCI can't run Amulet tests.
Change-Id: Iae83b12199468c18c76a5571eeae9c6a94e83af6
Related-Bug: #1828424
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I0f5b28437fda22b09fb0d9346fa5581f6a995f72
* 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: I8b159e2fd0eadecb23c580804ec9b3609b14fdb1
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Iac0486c6d978a34b9e7873bd00627d5c55d32e25
* 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: If175d58b7b663927d7e7be1c44550a9b8aaa5d79
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: I7d36e5607d2f57af31a98051ccb3f35d903f26c9
* 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: I87d7373ec6407dbfd30a93e04146fb122978634d
* 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: I59137f0bc2a0c5ee15f52bd03afefa275e9a011b
- 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: I9e6d0b4e0041f11e6a6417a73177b0fc4cfabfe3
This patch also updates the smoke test to run train.
Change-Id: Ib1e3d8b1b8298131237b02692380eade21e31ce8
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
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: I432a562efb84e486034f97f433186a31a80d4b2d
Also explicitly set ``include_system_packages`` to False.
While that setting is now the a default we consume from
``layer-basic`` it is more clear for the causual reader
of the charm source code.
Remove redundant entries from ``wheelhouse.txt``.
Change-Id: I242795da17bed0c78a7c7808d6b80d11528c65c7
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I681f54a71eb5d1c0605f18e0781f024b8966bf47
Do not rely on system installed Python packages but distribute the
direct charm dependencies as part of the charms wheelhouse.
As the span of distributions we need to support with reactive
charms widens we will run into compability problems with the
current model.
For further reference see juju/charm-helpers#341 and
juju-solutions/layer-basic#135
Change-Id: Ic4e33d59039421593c8ca22f08834ba6f6561b26
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: I8a8bbce4e79a7959f1735902c87d9d1ab02b9957
Story: #2005924
Task: #34228
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: Iccb39e338643d987309c61afe22713053536fb05
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: I6c57c238e19a3e7e500f81135075cdcb11ac3127
Ghanshyam Mann