standards icon indicating copy to clipboard operation
standards copied to clipboard

Standard for object-storage

Open anjastrunk opened this issue 1 year ago • 5 comments

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.~ S3 is mandatory, as defined in #587
  • [ ] Backup/Fail Safe capabilities
  • [ ] Locality, region, availability zone

anjastrunk avatar Sep 02 '24 09:09 anjastrunk

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.

mbuechse avatar Sep 02 '24 10:09 mbuechse

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.

anjastrunk avatar Sep 03 '24 06:09 anjastrunk

[Moved to https://github.com/SovereignCloudStack/standards/issues/1003 as it was out of scope here]

toothstone avatar Oct 28 '25 10:10 toothstone

I would like to add that it came up during S3 discussions, that cloud users typically expect to have their Swift and S3 data to be in sync, i.e. that all their objects can be accessed from both services if both are provided. This has not been addressed by the SCS standards so far.

toothstone avatar Oct 28 '25 13:10 toothstone

Do we really want to consider Swift? Regarding both the Swift API and the OpenStack Swift Service: neither of them is really widely used, is it?

berendt avatar Oct 28 '25 14:10 berendt