Keeping up a Competitive Ceph/RadosGW S3 API
summary
Practical account of contributing features and bugfixes to RadosGW S3 across releases, showing what lands upstream and what actually changes product behavior: compatibility improvements from Jewel to Nautilus, added API parity and bug fixes that reduce client incompatibilities, unit and integration tests plus proofs of concept and reference implementations, and glue in python libraries and drivers to validate deployments. Describes which patches get accepted, which are rejected, measurable interoperability wins and the operational work needed to make the RadosGW S3 API viable for service providers.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:21Users and companies investing in RGW/S3
- 7:36Base storage consumers
- 9:12Cheap and massive storage consumers
- 10:38On-line storage providers (laas providers)
- 12:31Libcloud Storage Drivers
- 14:54Going upstream with new features
related talks
43mWriting better APIs
19mVersioning strategy for a complex internal API
35mEvolving your APIs, a step-by-step approach
19mBeing the gentle giant: Supporting API users for the long haul
44mEvolving Your APIs, A Step-By-Step Approach
41mEvolving your APIs, a Step by Step Approach
14mHow to build better and consistent APIs at scale
37mAdvanced API Management & Operations, A Developer & Customer-Focused Approach