Yuxin Wang
2018-05-10 12:07:03 UTC
Dear all,
How to keep containers unique among a swift cluster?
I'm working on a swift project. Our customer cares about S3 compatibility very much. I tested our swift cluster with ceph/s3-tests and analyzed the failed cases. It turns out that lots of the failed cases are related to unique container/bucket. But as we know, containers are just unique in a tenant/project.
After googling, I can't find much info about that. I wonder if there are approaches to accomplish such a unique container constraint in a swift cluster? I thought about adding a proxy app in front of the proxy-server, the proxy app would maintain a mapping from unique containers to its account and check the uniqueness of every container PUT request, but it seems unpractical.
Do you have any ideas on how to do or maybe why not to do? I'd highly appreciate any suggestions.
Best regards,
Yuxin
How to keep containers unique among a swift cluster?
I'm working on a swift project. Our customer cares about S3 compatibility very much. I tested our swift cluster with ceph/s3-tests and analyzed the failed cases. It turns out that lots of the failed cases are related to unique container/bucket. But as we know, containers are just unique in a tenant/project.
After googling, I can't find much info about that. I wonder if there are approaches to accomplish such a unique container constraint in a swift cluster? I thought about adding a proxy app in front of the proxy-server, the proxy app would maintain a mapping from unique containers to its account and check the uniqueness of every container PUT request, but it seems unpractical.
Do you have any ideas on how to do or maybe why not to do? I'd highly appreciate any suggestions.
Best regards,
Yuxin