Repository navigation
Update tests Dockerfile and add tempest for SCS-0128 - #1281
Open
toothstone wants to merge 2 commits into
Open
toothstone wants to merge 2 commits into
toothstone wants to merge 2 commits into
Conversation
toothstone
force-pushed
the
fzahn/tempest-dockerfile
branch
3 times, most recently
from
September 24, 2026 17:37
0b3c07e to
1b0116c
Compare
toothstone
force-pushed
the
fzahn/tempest-dockerfile
branch
from
October 29, 2026 13:41
1b0116c to
7478b0d
Compare
toothstone
marked this pull request as ready for review
October 29, 2026 13:41
toothstone
requested review from
depressiveRobot,
fkr,
garloff and
mbuechse
as code owners
October 29, 2026 13:41
Contributor
Author
|
I've been using this image to run the IaaS compliance checks and tempest for some time now, no problems. Sonobuoy is still available and the executable runs, didn't do a full run but |
mbuechse
reviewed
Oct 29, 2026
| -c ../requirements.txt | ||
| boto3 | ||
| openstacksdk | ||
| tempest |
Contributor
There was a problem hiding this comment.
Tempest pulls in half the internet. Can we put that into a dedicated file (with -c requirements.txt)?
| COPY iaas/requirements.txt iaas-requirements.txt | ||
| COPY kaas/requirements.txt kaas-requirements.txt | ||
| RUN pip3 install -r requirements.txt -r iaas-requirements.txt -r kaas-requirements.txt | ||
| RUN --mount=type=cache,target=/root/.cache \ |
Contributor
There was a problem hiding this comment.
Then we could add -r tempest-requirements.txt here.
| # by the following command: | ||
| # | ||
| # pip-compile requirements.in | ||
| # pip-compile --no-index iaas/requirements.in |
Contributor
There was a problem hiding this comment.
What does --no-index do? Can you add this to Tests/README.md (at the bottom somewhere, there is some section on pip-compile)
Contributor
Author
There was a problem hiding this comment.
This is the auto-generated output from running pip-compile requirements.in on my machine :/
Signed-off-by: Friedrich Zahn <friedrich.zahn@alasca.cloud>
Signed-off-by: Friedrich Zahn <friedrich.zahn@alasca.cloud>
toothstone
force-pushed
the
fzahn/tempest-dockerfile
branch
from
October 30, 2026 09:30
7478b0d to
2342ea1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switching to a slim image base & removing cached packages saves over 800 MB.
Adding tempest and a tempest workspace so we can run it for SCS-0128 - the list of testcases is already copied in.
Image is available for testing at https://gitlab.com/alasca.cloud/focis/experiments/scs-verify/container_registry/12429177 (
registry.gitlab.com/alasca.cloud/focis/experiments/scs-verify:latest)