As per 2025.1 testing runtime[1], we need to test on Ubuntu
Noble (which will be taken care by depends-on tempest and devstack
patches to move base jobs to Noble) and at least single job to run on
Ubuntu Jammy (for smooth upgrade from previous releases).
This commit adds a new job to run on Jammy which can be removed
in the next cycle.
Depends-On: https://review.opendev.org/c/openstack/tempest/+/932156
[1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html
Change-Id: I1d0c87830cc4f58facdeeedba0a376ef2e087945
Add file to the reno documentation build to show release notes for
stable/2024.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.2.
Sem-Ver: feature
Change-Id: Icea8e0ce7e613853cdea75f59d0af9c06a86bcf8
The log message is sent in a normal sequence without any failure, so
it shouldn't be logger in the error level.
Change-Id: Ia99639df19d7ec97c42c3b365b2042a75ff66bb0
This has been unmaintained and its functional tests have been broken
for some time. Because the current upper version is not compatible with
Python 3.12 and we aren't sure if we can bump the cap safely, let's
remove the extension.
Also replace the openstack CLI by the swift CLI to resolve the current
CI failure.
Change-Id: I1a2f908fef4b660686d75ea6e8330287b423cd8b
These are detected as errors since the clean up was done[1] in
the requirements repository.
[1] 314734e938f107cbd5ebcc7af4d9167c11347406
Change-Id: I06ba02c081822aea9dc76bd949ff0ce31deecd44
This has been unused since the SUID binary to restart docker containers
was removed[1].
[1] d60176cc2f7286257ab8d2187329943efec09bb7
Change-Id: If2050e6a8e44217536cd80504934cd4949583b0c
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: I4d87c52977d1569cf3f84a25241fd3ebea2825ca
Using many extra resources may cause high load at proxy server, because
the process needs to get all of the requested objects concurrently.
This change introduces a new option to limit maximum number of extra
resources per request to avoid DoS attack by too many extra resources.
If a request contains extra resources over the limit, then the request
is rejected at an early stage. The default value is -1 which means
unlimited. In case this option is set to 0 then users are not allowed
to use extra resources at all.
This also refactors handling of extra-resources header. One side
benefit of the refactoring is that now users can use additional inputs
when executing storlet over PUT requests.
Change-Id: I0ea7d78614f2b1ef5bf4961d2d5fe773264ef448
* Fix duplicate closure of _input_read_fd
* Delegate closure of _input_write_fd to the dedicated write thread
Change-Id: I74128fe1f55abafea322111cf289fb0a978fc2b4
Each StorletRequest or StorletResponse can contain multiple StorletData
when using multi input/output feature.
Change-Id: I755583116d55588083ec9703de28344f3e20f7ee
This introduces a functional tests which runs on CentOS Stream 9.
Currently we use docker-ce in this job, but the job may be later
updated to use podman, which is part of the distribution packages.
Change-Id: Ic93c1c7faf46f641aa5988c688ebbef4a6e32ab4
