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

Standard for object-storage #725

Open
3 tasks
anjastrunk opened this issue Sep 2, 2024 · 2 comments
Open
3 tasks

Standard for object-storage #725

anjastrunk opened this issue Sep 2, 2024 · 2 comments
Assignees
Labels
SCS-VP10 Related to tender lot SCS-VP10 standards Issues / ADR / pull requests relevant for standardization & certification

Comments

@anjastrunk
Copy link
Contributor

Object-storage is one mandatory service in SCS infrastructure, see #587. However, requirements for object-store are not yet defined. Similar to block storage, as an IaaS user, I want to know what capabilities a SCS object-store has. These capabilities include (on exhaustive list)

  • API endpoint, as Object storage comes with two different APIs: S3 and Swift.
  • Backup/Fail Safe capabilities
  • Locality, region, availability zone
@anjastrunk anjastrunk added standards Issues / ADR / pull requests relevant for standardization & certification SCS-VP10 Related to tender lot SCS-VP10 labels Sep 2, 2024
@mbuechse
Copy link
Contributor

mbuechse commented Sep 2, 2024

The idea was that #587 standardizes APIs, and in the case of object storage, we decided to make the S3 API mandatory and the Swift API recommended.

@anjastrunk
Copy link
Contributor Author

The idea was that #587 standardizes APIs, and in the case of object storage, we decided to make the S3 API mandatory and the Swift API recommended.

You are right and we have to standardize capabilities of components behind the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SCS-VP10 Related to tender lot SCS-VP10 standards Issues / ADR / pull requests relevant for standardization & certification
Projects
Status: Backlog
Development

No branches or pull requests

3 participants