What kind of workload are you using Ceph for? (Part-3)
In part3 let’s look at RADOS Gateway (radosgw) the top 3 interfaces being used with Ceph. Basically, radosgw is a RESTful gateway to access to Ceph object store and it supports both S3 and Swift API for Amazon and OpenStack. Since it is using RESTful, all the web related technology could be useful to help enhance the radosgw e.g. using nginx as CDN, etc. Therefore having workload related to S3 and OpenStack should be automatic. However, the scope of these two API could mean any kind of IO patterns is possible. And the use case for radosgw is most flexible and dynamic. Meanwhile, the application that uses RESTful is also likely to be custom made and would require more control over the storage need. This also means in a longer term perspective in order to really provide an appliance template architecture for Ceph should all 3rd party create their own plugins and interface. But this feature may push to at least a version or two later for Aquarium to gain enough users to do so. Let’s look at some typical use cases and prepare the default workload that makes sense for now.
- OpenStack
- Metadata Search
- Message Queue
- Media Backup
OpenStack in the previous two article already show the use cases of doing block image and file service. Radosgw is compatible with the Swift API so, it could be use directly. So what we can also do for the user is to sync the OpenStack KeyStone identity management. That way the user management could…
