This change adds the haproxy options if defined by the
charm class to enable HTTP checks to the HAProxy
configuration, instead of the default TCP connection
checks.
options.ssl check if the environment is using http or
https mode. We disable certificate verification because
we are only interested in the health of the service.
Fix for tox4 compability
Closes-Bug: #1880610
Change-Id: Ie091fdfe560b6a060f0c29c6b92a99f5e564eddf
Osci runs the CI jobs on Bionic, this version of tox (2.5) will
automatically upgrade the packages at virtualenv creation and any
pinning won't have effect since the virtualenv created is upgraded to
the latest versions of pip and setuptools. This behavior was changed in
tox 3.10 with the addition of the 'download' directive[0]
Setuptools 58.0 dropped the support for use_2to3=true which is needed to
install blessings (an indirect dependency of charm-tools) since then
the gate got broken.
This is similar to:
https://github.com/openstack-charmers/release-tools/pull/156https://github.com/openstack-charmers/release-tools/pull/157
Change-Id: I7f22cd744a7aa5747cca49f094a5efd041481a80
Co-authored-by: Felipe Reyes <felipe.reyes@canonical.com>
For principal - subordinate plugin type relations where the
principal Python payload imports code from packages managed by a
subordinate, upgrades can be problematic.
This change will allow a subordinate charm that have opted into the
feature to inform its principal about all implemented release -
packages combinations ahead of time. With this information in place
the principal can do the upgrade in one operation without risk of
charm relation RPC type processing at a critical moment.
Related-Bug: #1806111
Change-Id: I2df0abed25825448569581273aee4e79a6003dad
- 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.
Change-Id: I370fbffa06544c66fcae7a24b15f37b01cbd7d7a
Add empty series list to metadata.yaml to get around charm-tools
now mandating a series list to be present.
This list will always be overridden by charms but building the
layer is part of our gate and we need to unblock it.
Update tox basepython, the build will no longer succeed in the gate
with py27.
Change-Id: If81441d5fb0ed3b8819c4a2814dc20c5e47a8eff
Move workdir to avoid charm build error in gate test. Move built
artifact back so CI can inspect it. (The layer build-only job in
CI should get an update to cope with this itself)
Change-Id: Icee40b83e6924a6adc9ee1f97eff04522121d5fa
Closes-Bug: #1823729
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: I360fc2d49b9e737fd36442ac291a1f532f98b3e7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add generic action code that utilises charms_openstack.bus.discover()
so that the top level charm does not need to make any changes to
inherit generic actions.
Change-Id: I8b3422b915e2477d936e5cdd2d883c6815487577
Remove old template for apache pre-2.4 and update
openstack_https_frontend.conf to match adapter parameters
Add tox targets to placate CI
Change-Id: I03acf7e3e524b2a15756a07e0a2d13ed88eaefac
The code has shifted to the charm.openstack (at the time of writing)
module that will be included in the built charm, rather than being in
the layer. The idea is to make it easier to test/stub out openstack
charms.
Add unit tests to the adapters, charm and ip parts of the lib to ensure
that the API to the classes remains stable with no unplanned regessions
over time.