Managing quota

IBM Storage Ceph as a Service supports deployment level quotas for both the Performance and Capacity plans. The block and object level quota allocation depends on the committed capacity along with the user opted max burst capacity usage limit.

Since the provisioned capacity and quota are at deployment level setting, the quota can be set for block storage as well as object storage. The quota is set initially by default when the deployment instance is created that also includes the maximum burst capacity usage limit.

Managing quota from the UI

In the IBM Cloud console , click Deployments > Name link > Settings.
Click Edit preferences.

If you want to manage quota for a different Deployment, then click Deployments drop down to choose the one whose quota you want to manage and click Edit preferences.
Review the capacity limit. Select Include burst capacity if you want to include the burst capacity to expand your total available capacity.

Including burst capacity might incur overage fees for the amount of burst capacity used.
Click Next and review the storage capacity allocations.
Use the plus and minus controls to modify the allocated capacity.

The allocated capacity cannot be reduced or set below the current amount of used or provisioned capacity.
Click Save to set the new storage capacity allocations.

Managing quota using the CLI

Use the following command to modify the block and object storage capacity quota.

ibmcloud resource service-instance-update <Service_Instance_name>  --parameters '{"quota": {"block": <n>, "object": <n>}, "allocate_burst_capacity": <bool>}'

In the --parameters specify the capacity amounts. See the following example where the Service_Instance_ID is cephaas-unified-2 and the quota to be updated are specified as parameters.

ibmcloud resource service-instance-update cephaas-unified-2 --parameters `{"quota": {"block": 60, "object": 40}, "allocate_burst_capacity":"true"}`
...

Updating service instance cephaas-unified-2 with ID crn:vi:staging:public:software-defined-storage:us-south:a/7a30fdf....:: is updated successfully

To verify that the capacity quota was updated, run the following command

ibmcloud resource service-instance <Service_Instance_name> --output json

Managing quota with the API

Make a PATCH request to modify the block and object quota.

curl -X PATCH $rc_endpoint/v2/resource_instances/$guid -H "Authorization: Bearer $IAM_TOKEN" -H 'Content-Type: application/json' -d '{
"parameters": {
       "quota":{"block":60,"object":40},
       "allocate_burst_capacity":true
   }
}'

In the example, $rc_endpoint is the resource controller endpoint. Make sure that crn is included in the url in encoded format.

You can configure and set the default endpoint for resource controller $rc_endpoint to https://resource-controller.cloud.ibm.com/v2/resource_instances. For guidance on how to set the URL, see Config commands.

When allocate burst capacity is set to true then 30% extra quota is set which is the total of block and object quota where the burst capacity is also included in this total quota leading to increase in the overages and pricing fees.

When the allocate burst capacity value is set to false, the burst capacity is disabled and the quota does not exceed the total of the current set value.