Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I9a0eb82d1b495490e6af65a52397105d061ca4a2
This is follow-up of 76d414e58d and fixes
the incomplete construction of an exception message. This also removes
the translation according to the other messages.
Change-Id: Ie2ed619b06d9d6340eb81fc1fac4dbd21702de19
This adds functional tests with redis and redis sentinel, to ensure
the current implementation can initialize clients properly.
Change-Id: I6318f6ad00d5b0ee3db1be5e8671a4c346b9daff
This introduces support for Redis Sentinel backend. Users can now
use Redis Sentinel backend instead of Redis backend by configurations
like the example below.
[cache]
enabled = True
backend = dogpile.cache.redis_sentinel
redis_password = <password>
redis_sentinels = 192.0.2.1:26379,192.0.2.2:26379,192.0.2.3:26379
If tls_enabled option is set to True then all the tls settings are
applied for connections to Redis as well as connections to Redis
Sentinel.
Change-Id: Ic3b84fe6810e08337a884c68625ccfed11665269
This introduces a few new redis_* options to simplify the settings
required to use the redis backend. The main aim of this change is to
replace the requirement to inject url by backend_argument.
[cache]
backend=dogpile.cache.redis
redis_server=127.0.0.1:6379
redis_username=default
redis_password=a_big_secret
redis_socket_timeout=1.0
Closes-Bug: #2052351
Change-Id: Id72878f9cddaa99146eab5fb4ee76c8e6a633809
Because these are not intentional default. This also adds a validation
logic to catch the case where SASL is requested but username or
password is not given.
Change-Id: Ia98bfc5f9a42c13acfdb2192bb1fa11773f6ccf8
This adds support for configuring certificate/key files used for TLS
connection with Redis using the existing tls_* options.
example)
[cache]
backend=dogpile.cache.backend.redis
backend_arguments=url:rediss://:a_big_secret@localhost:2679
tls_enabled=True
tls_cafile = /etc/pki/tls/certs/ca-bundle.crt
Change-Id: I2ab38b8c88274cb4908791eea8212a79e3d524a2
The tls_enabled option works properly only for the following backends.
- oslo_cache.memcache_pool
- dogpile.cache.bmemcache
- dogpile.cache.pymemcache
Currently the tls options are all ignored in case a different backend
is used, but this does not allow users to notice that TLS is not
enabled contrary to their expectations.
This introduces the validation to ensure an appropriate backend is used
when tls is enabled.
NOTE:
The oslo_cache.memcache_pool bakcend supports tls_enabled only when
sasl_enabled is true, which can be fixed separately.
Change-Id: Ib967bf8cb21fb97fff94a6d6cb5983374e4798eb
We also remove these unnecessary linter dependencies from
test-requirements.txt.
Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
Change-Id: I2955b4a99c6963977272e6946058fe8134dfc45a
The previous attempt did not update the version in pre commit config
so the old version is still used by pep8 target.
Change-Id: Ib86e124697031f63d1f7ba1ec961d9d8adffa95e
As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: I28b8d0bdc06a9bd12290180f5e5cdc9e9c82be74
The ConnectionPool currently opens sockets, but never closes them. As a
result, any client using oslo.cache memcache pool leaves sockets in a
CLOSE_WAIT state, with the source port not being re-usable.
In our production system, were we have A LOT of activity, this creates
a storm of non-reusable ports: all source ports are in use, making the
node unuseable for other things.
This patch adds a __del__ destructor closing inactive connections,
fixing the issue.
Closes-Bug: #2043121
Change-Id: I09d632346c76d1aff7c534f0d040162d1985f548
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: I8adbe911c4bfd277c1229ba2c4351eb5a3fa879a