* Update charm-layer-openstack from branch 'master'
to 7c671b0696977f455616565d956895b2f890464b
- Add calver abd hatchling dependencies for dnspython>=2.5.0
dnspython, as of 2.5.0, has switched to hatchling (from poetry) for
module installation. For source based reactive charms, this means that
the calver and hatchling dependencies need to be present in the
wheelhouse of the built charm for it to install.
Change-Id: Ie9fb6ff19753cfb9c61f8027c9dee47dfb9739fd
* Update charm-layer-openstack from branch 'master'
to 1c9e662d78b328c6d4587171ccba08572e8dcf25
- Add support for HAProxy L7 checks
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
* Update charm-layer-openstack from branch 'master'
to 8b31ef19e40b1cff2960434ef940867d85ea56be
- Add poetry-core to build dnspython
The commit f9a11fd unpinned dnspython, the newer version of it requires
poetry-core to be built and 'pip download' doesn't capture that
requirement. Some charms have been migrated to binary charms, but not
all of them have been migrated, this change gives those more time to
transition.
Change-Id: I0656d8a902eeede56fe0315a9db782b1c707c26c
* Update charm-layer-openstack from branch 'master'
to f9a11fde2e136fc45ee619f3e94eb93fcffb117d
- Unpin dnspython
Commit 1a2962cd699dcbd5fcfc277bc4843905ae7982a3 pinned dnspython
in order to retain Python 3.5 (Trusty/Xenial) support.
Since then, the aforementioned releases has gone EOL and our
charms no longer support them.
This pin is now prohibiting foreward movement into Python 3.10
on Jammy and as such we should remove it.
Closes-Bug: #1989066
Signed-off-by: Frode Nordahl <frode.nordahl@canonical.com>
Change-Id: Ifb2c807e6522a314f667b8b29094888132d4e4bb
* Update charm-layer-openstack from branch 'master'
to 79dbe21f571fcea8b9d254ed85e796453e442977
- Remove Tempita as it is unsupoorted
Tempita should be removed as much as possible and having it in a
low level layer like this causes it to be installed in charms
which do not require it.
Change-Id: I7d06601ff4c316cf4325196116b10e108dc17eed
* Update charm-layer-openstack from branch 'master'
to 93bc9e1837b71cd80536c67ed8c1a64d9ee43872
- Do not execute certificate handlers in update-status hook
The certificate handler code does a bit of work and should not
run during the update-status hook.
As documented in the charms.reactive dispatch [0] function
handlers registered with the @hook decorator will execute before
other handlers. So we can rely on the 'is-update-status-hook'
flag being consistently set when in update-status hook before
other handlers are evaluated for dispatch.
0: 3d27f3d24a/charms/reactive/bus.py (L325)
Closes-Bug: #1954748
Change-Id: I4a3aa544f98049c83db576f95de826038e8e1afc
* Update charm-layer-openstack from branch 'master'
to 5999eeaa5d007b6ae8dc12753976ef11f76684ee
- Align haproxy logging config with charm-helpers
The previous config didn't actually log anything, and it has been fixed
for classic OpenStack API charms through charm-helpers. We need to
update layer-openstack as well to reflect those changes to reactive
OpenStack API charms.
Closes-Bug: #1697002
Related-Bug: #1940037
Change-Id: I523369673471f63346428f7f739a2429aa5084b3
* Update charm-layer-openstack from branch 'master'
to 1ff51a9bf3bc6dd00d5110708600f51ff3b1ead3
- Ease KeepAliveTimeout in line with keystoneauth1.session.Session
Apache2's default value for KeepAliveTimeout is 5 seconds, which is okay
for general web-page serving use cases. However, sessions and connection
pools created by keystoneauth1.session.Session can be terminated
unnecessarily during multiple API calls in a session due to the short
KeepAliveTimeout.
Let's ease KeepAliveTimeout to 75 seconds, which is fairly standard for
API services behind a reverse proxy since it's the default value of
nginx.
Closes-Bug: #1947010
Change-Id: I752a836676d895ef783362810ed6764980e8574b
* Update charm-layer-openstack from branch 'master'
to 4793ceba5faeac659d9db9b5fc4edde325155710
- Wrap pip to force pip<20.3 and setuptools<50.0.0
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>
* Update charm-layer-openstack from branch 'master'
to 207bac8bec837edc6a4d6003f51d5b59d2d75adb
- Ensure endpoints are populated within actions
When actions are run the reactive run_at{start,exit} methods are not
implicit run. This means that some data associated with endpoints
is missing. For example reactive.Endpoint.all_joined_units is always
None.
Change-Id: I565fb534612a06d76e6688ed4f06ad64bc42e512
* Update charm-layer-openstack from branch 'master'
to ba152d41b4a1109073d335415f43c4248109e7c7
- Publish releases packages map to opt-in endpoints
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
* Update charm-layer-openstack from branch 'master'
to 91e6caf3be764d117d07be5dbf5927b847284e49
- Use the project_name from the identity_service
Currently the template hardcodes the `project_name` to `services`
which is not necessarily correct. Instead the template should use the
`identity_service.service_tenant`.
Closes-Bug: #1908945
Signed-off-by: Nicolas Bock <nicolas.bock@canonical.com>
Change-Id: Idd2a7c436f5448505bdfe5a53738a8e2071ed272
* Update charm-layer-openstack from branch 'master'
- Refresh cipher suites and protocols
The last update was 2016, and it's time to drop TLSv1 and TLSv1.1 as the
base configuration recommended by Mozilla.
https://wiki.mozilla.org/Security/Server_Side_TLS
This is equivalent to a charm-helper's change:
27d6ceb385
Change-Id: Ic7c3751d5cfce33517072bfca865e03f6f84f423
Closes-Bug: #1886630
* Update charm-layer-openstack from branch 'master'
- Merge "Add a 'is-update-status-hook' flag to the layer"
- Add a 'is-update-status-hook' flag to the layer
This flag is to enable charms.openstack / layer-openstack charms to have
a way to determine if the current hook is update-status from a flag. By
being a flag, it means that charm reactive handler code doesn't have to
check for the the hook in every handlers, but can declare "don't run
this if it's an update-status hook". The flag is guaranteed to not be
set during a not update-status hook (in that, if it is set, then it gets
cleared and the handlers can therefore run), or to be set during an
update-status hook. To speed things up, the code also removes the flag
at the end of the update-status handler.
The intended use of this flag is to guard 'expensive' handlers from
being run during update-status.
Change-Id: I7ca97db646ada95d7f5541ca4e2cf14013c0d7a6
* Update charm-layer-openstack from branch 'master'
- Do not run config.rendered handlers when paused
Change-Id: Ie55422148e2824a30af51ffc121f88380bade06f
Closes-Bug: #1885121
* Update charm-layer-openstack from branch 'master'
- Ensure that concrete charm class is found for default handlers
When debugging a charm uprade issue with ovn_chassis, it was noticed
that the upgrade hook failed as the concrete charm class wasn't
found and instantiated. This patchset ensures that the concrete charm
class is found and thus can be instantiated.
Change-Id: Ic9cdc2f470e4c7e1f6fc17a4d6246ca79fc48bd7
* Update charm-layer-openstack from branch 'master'
- Merge "Add list of files to exclude on layer consumption"
- Add list of files to exclude on layer consumption
Change-Id: I4791f29f850e809a35c40b562e018a2f743e22d1
Closes-Bug: #1852424
* Update charm-layer-openstack from branch 'master'
- Add section-placement
The placement config may be useful among more than one charm as
more services start to use the placement service. This patch adds
a single source of placement sectional config.
Change-Id: Id99e750f7b43dd0c893790eaa6fb79f7ce064f12
Related-Bug: 1850691
* Update charm-layer-openstack from branch 'master'
- Merge "Add default certificates relation handlers"
- Add default certificates relation handlers
These where moved up to this layer from ``layer-openstack-api``,
removal counterpart: I007275c041ca5465664a6b5d441e56c0316c405d
Guard the default handlers behind check for
'charms.openstack.do-default-certificates.available' flag. This
flag is activated when the consumer charm makes a call to
charm.use_defaults('certificates.available') from its reactive
handler. Previously it was always activated for all consumers of
the ``openstack-api`` layer, it should be up to the charm
implementation to choose.
We do not add back ``layer-tls-client``, the reason being that
the reactive bits in ``layer-openstack`` in conjunction with
helpers in ``charms.openstack`` is managing both the server and CA
certificates and rely on the same flags to detect changes.
If we one day offload those tasks to the ``layer-tls-client``
we should add it back in conjunction with removing our code for
this. At the time of this writing it would not be possible as
``layer-tls-client`` is not spaces aware.
With the above mentioned change we can stop relying on the now
deprecated ``certificates.batch.cert.available`` flag.
We also do not add back the Keystone certificates handling code
as this has been removed from the Keystone charm reference:
openstack/charm-keystone/commit/17b24e7fde8e4c8c276a4f392cbae0d1d0ed2615
Needed-By: I007275c041ca5465664a6b5d441e56c0316c405d
Needed-By: I8a72acd451dd21e1b042b7f71f6d98e164737ac1
Closes-Bug: #1840899
Change-Id: I12f45236632b608e07fdd35d31b90b84ca92eb1f
* Update charm-layer-openstack from branch 'master'
- Avoid pollution and false positives with tox.ini
- 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
* Update charm-layer-openstack from branch 'master'
- Update layer wheelhouse with common dependencies
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
- OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.htmlhttp://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
* Update charm-layer-openstack from branch 'master'
- Use ``uri`` property
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
* Update charm-layer-openstack from branch 'master'
- Add default handler for storage-backend
Add a default handler for storage-backend relation. This is part
of the work to push cinder plugin bolierplate code into supporting
layers.
Change-Id: Icad5f72939b1e33d15adf2638f8e344235a9318b
Alex Kavanagh