The systool command is necessary for some non-Ceph backends, but Ubuntu
packages do not pull it as a dependency. Make sure sysfsutils is
installed in cinder-volume units by default instead of updating all
backend charms.
lsscsi is a dependency of os-brick for volume related operations
including creating a boot volume with iSCSI/FC backends. However, it
wasn't installed by default until jammy-antelope (lunar) due to a
packaging bug. It hasn't been an obvious issue especially when the
cinder-volume unit and the nova-compute unit are co-located since
nova-compute charm installs the package. Instead of applying a
workaround to all backend charms, let's apply the workaround in the
cinder charm since lsscsi is installed by default for later OpenStack
releases anyway and it's a small package.
Closes-Bug: #1939390
Change-Id: I131e12c53c78957873b6a75a3b1b67b1725b43ed
(cherry picked from commit 9a6ab28af2f5b01bc5ebc54c7cde3248dd65b53e)
This commit adds Keystone audit middleware API logging to the Cinder
charm in versions Yoga and newer to allow users to configure their
environment for CADF compliance. This feature can be enabled/disabled
and is set to 'disabled' by default to avoid bloat in log files.
The logging output is configured to /var/log/apache2/cinder_error.log.
This commit builds on previous discussions: https://github.com/juju/charm-helpers/pull/808.
Bug LP 1863232 introduced a new Apache configuration option called
WSGISocketRotation which allows users to disable wsgi socket
rotation. This patch makes this configurable with a new
wsgi-socket-rotation config option that defaults to the Apache
default and can optionally be set to False.
[yoga] Ensure get_requests_for_local_unit doesn't fail on incomplete relation
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
Change-Id: Ia8830828f363af91b0765ff4f761faefb5f00212
(cherry picked from commit 6f00af3e777ff53cfbe287536977f7ff3eb7f0c3)
Sync from charm-helpers to update [service_user] config to use the
service domain.
The keystone charm currently creates two service users, one for the
service domain (for v3 authentication), and the other for the default
domain (for v2 authentication). The [service_user] config needs to
use the service domain.
Render [service_user] only for identity-service relation
The service token section [service_user] is not required when
cinder-volume is deployed as a separate service. In other words
it is not required for the identity-credentials relation.
The [service_user] section is nearly the same as the
[keystone_authtoken] section, and the keystone_authtoken data
is only produced for the IdentityServiceContext, therefore this
change will not render [service_user] for the
IdentityCredentialsContext.
Closes-Bug: #2024676
Change-Id: Iaecae3c22db1f4f2309f73f8c6836e6c072b848b
(cherry picked from commit ebbedcbf58660ce13823152d6943fee036af7e11)
