cdmi-s3-qos
  • About cdmi-s3-qos
  • Module description
    • RADOSGW, Ceph Object Gateway and QoS
    • Interface to QoS metrics
  • Deployment and Administration guide
    • Installing
    • Starting, stoping and enabling
    • Building sources
    • Running from docker image
    • Configuration
    • Manual integration with cdmi server
  • User guide
Powered by GitBook
On this page
  • Refer to cdmi-qos documentation
  • Limitations

User guide

PreviousManual integration with cdmi server

Last updated 6 years ago

Refer to cdmi-qos documentation

The cdmi-s3-qos module is meant to be part of server, and as such doesn’t introduce any direct interaction with end-users.

The basics of user interaction with cdmi-qos server are presented in cdmi-qos documentation, in chapter .

Limitations

In general cdmi-qos processes four types of queries related to QoS managemnt: ask for all supported QoS profiles, ask for details of specific QoS profile, ask for QoS profile related with specific data object or container and finally change the QoS profile assigned to container or data object.

The cdmi-qos server processes the mentioned queries and requests by delegating them to "QoS Storage Back-End Modules". Such a module can be treated as kind of proxy to underlying storage technology and its QoS related functionality. The cdmi-s3-qos module is a proxy to QoS management facilities of CEPH cluster and to its Object Storage Gateway sub-component.

Due to intrinsic Object Storage Gateway qualities, the QoS properties assigned to a given S3 data object can not be changed on the fly. It means that when cdmi-qos server delegates QoS policy change request to cdmi-s3-qos module, the request cannot be realized. In such a case the module informs the server that the request cannot be fulfilled and server returns proper error status to the caller.

cdmi-qos
API Walkthrough