Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the use cases for which the testbed is there #1041

Open
Tracked by #193
berendt opened this issue Oct 12, 2022 · 2 comments
Open
Tracked by #193

Add the use cases for which the testbed is there #1041

berendt opened this issue Oct 12, 2022 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation SCS Sovereign Cloud Stack

Comments

@berendt
Copy link
Member

berendt commented Oct 12, 2022

  • developer
  • operators
  • new users
  • CI
@garloff
Copy link

garloff commented Oct 27, 2022

  • SCS Developers: Have their own SCS deployment for inspection, development, testing
  • SCS Operators: Validate changes, reproduce customer issues, keep track of upstream
  • New users: Get a first impression how SCS is deployed, developed, operated (under the hood)
  • CI for itself: Validate that the IaaS layer can be deployed and works
  • CI for code on top: Infrastructure that allows software above the IaaS layer to be validated against latest IaaS layer

@berendt berendt added the SCS Sovereign Cloud Stack label Oct 27, 2022
@berendt
Copy link
Member Author

berendt commented Nov 4, 2022

We are following up within the framework of the SIG Documentation. The first thing to be revised is the openstack-image-manager repository. This repository will then follow.

@berendt berendt self-assigned this Nov 8, 2022
@berendt berendt transferred this issue from osism/testbed May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation SCS Sovereign Cloud Stack
Projects
None yet
Development

No branches or pull requests

2 participants