Converting the charm to binary builds provides two benefits:
- build time issues are moved to testing rather than (failing) at the
install time, which can often happen after the charm is pushed to the
charmhub.
- the install time is much, much faster. This means upgrades take < 1m
rather 3-4m.
Change-Id: Ib4f4a8acf807de0406b9588d32750e3a48ff2841
Rebuild the charm to pick up charms.reactive-1.5.2 which includes a fix
for application is single unit.
Adding libpython3-dev to be able to build Cython
Related-Pr: https://github.com/juju-solutions/charms.reactive/pull/243
Change-Id: Ief281586efde5303c66bd7b0432589c9735c7f86
* 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: I577fff942606ded9885e9ba6f29040ba3fc7fb27
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: Icb73919f247c60a9e18cc2e563f0fda9c620cb14
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: I3447ba421e4d73b12cd633bb4b3c4a60b5dd371f
* 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: I531088a70f1281ba7f2f066c383e234fb7a8164f
* 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: If226d1e14a213f0c04cf63a56058682f13d32dc2
* 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: I82c35d13e7cbb4586a29c70ebccb4f687a17a496
The idea of an application cert is that it is identical on all
units. To generate one the interface collects all the published
sans and cns from the clients and generates one certificate
which is valid for all of them.
This change relies on an interface change *1
*1 https://github.com/juju-solutions/interface-tls-certificates/pull/22
Change-Id: I24362d23e2445970a7d1b078380f22dc672487ee
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: Ibad815c50a15aa8df7349262109fcdb2e4a3e341
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: I35a710ef22d2b1185179f0679a1e18c530da49b9
Story: #2005924
Task: #34228
This change adds in zaza.openstack, as well as changing the
branch target of zaza to a branch with zaza.openstack
removed, allowing us to validate the new library
Change-Id: If2db3d8d992cd24fcf0cefb5409cb6cb17658eea
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: I42a5f115cce800e08afa68a43467fc323ce9c853
Ensure KV backend is created as a v2 backend by using
explicit provision of options when enabling the secret
backend.
Change-Id: Ief0a26c8a1adb9f6be39fa497222f809994c11d0
Set the vault app version in juju status using the version
returned from the Vault health data (rather than the installed
snap).
This review also puts in place the atexit handling needed for
general status assessment.
Change-Id: I1f8f0991534f4e130e924ffac733fa13141f0970
The OpenStack reactive charms use a src directory to store the
'source' charm. Convert the vault charm to comply with this
structure.
Change-Id: I7dd36b9aa7419459238f989dfe6c0553f7641cdf
Add .gitreview file to point at openStack gerrit
Bring tox.ini and requirements mostly inline with other
reactive charms. tox.ini has to deviate slightly as
charm currently has no src dir.
Change-Id: I9184847409a884699d3b51641e19cbd9d30634fa
Add a tox.ini for creating virtualenvs and then executing builds,
flake8, unit tests and charm proof in those venvs. Example:
tox -e pep8
tox -e build
tox -e charm-proof
tox -e unit-tests
Partial-Bug: #1745966
Alex Kavanagh