Manage Block Storage backup quotas per project

You can change or view the limits of the following resource quotas that apply to Block Storage volume backups that users can create for each project (tenant):

About this task
Copy link

  • backups, specify the maximum number of Block Storage volume backups that users of this project can create. By default, this limit is set to 10.
  • backup-gigabytes, specify the total size, in gigabytes, of all the Block Storage volume backups that users of this project can create. By default, this limit is set to 1000.

You can also view the usage of these Block Storage backup resource quotas for each project.

Procedure
Copy link

  1. Access the remote shell for the openstackclient pod from your workstation: 
    $ oc rsh -n openstack openstackclient
$ source ./cloudrc
  2. Optional: List the projects to obtain the ID or name of the required project: 
    $ openstack project list
  3. View the current limits of the backup quotas for a specific project: 
    $ openstack quota show <project>
    • Replace <project> with the ID or name of the required project.

      This provides the limits of all the resource quotas for the specified project. Take note of the Limit column for the backup-gigabytes and backups fields in the table. For example:

      $ openstack quota show c2c1da89ed1648fc8b4f35a045f8d34c
+-----------------------+-------+
| Resource              | Limit |
+-----------------------+-------+
...
| backups               |    10 |
...
| backup-gigabytes      |  1000 |
...
+-----------------------+-------+
  4. Optional: Modify the total size of all the Block Storage volume backups that users can create for a project: 
    $ openstack quota set --backup-gigabytes <totalgb> <project>
    • Replace <totalgb> with the total size, in gigabytes, of the backups that users can create for this project.
  5. Optional: Modify the maximum number of the Block Storage volume backups that users can create for a project: 
    $ openstack quota set --backups <maxnum> <project>
    • Replace <maxnum> with the maximum number of backups that users can create for this project.
  6. Optional: View the usage of these Block Storage volume backup quotas and, if necessary, review any changes to their limits for a specific project: 
    $ cinder quota-usage <project_id>
    • Replace <project_id> with the ID of the project.

      The first two rows in this table specify the backup quotas for the specified project. Examine the following columns in this table:

    • The In_use column indicates how much of each resource has been used.
    • The Limit column indicates whether the quota limits have been adjusted from their default settings, in this example both have been adjusted. 
      $ cinder quota-usage c2c1da89ed1648fc8b4f35a045f8d34c
+-----------------------+--------+----------+-------+-----------+
| Type                  | In_use | Reserved | Limit | Allocated |
+-----------------------+--------+----------+-------+-----------+
| backup_gigabytes      | 235    | 0        | 500   |           |
| backups               | 7      | 0        | 12    |           |
...
  7. Exit the openstackclient pod: 
    $ exit

Grant volume owners access to admin-created backups
Copy link

When you back up a volume on behalf of another project, include the volume owner’s credentials so they can access the backup.

Procedure
Copy link

Provide the following arguments to authenticate a volume owner for access to volume backups: 
$ openstack --os-project-name <projectname> \
--os-username <username> \
--os-password <password> \
volume backup create [--name <backup_name>] <volume>
  • Replace <projectname> with the name of the project (tenant) of the owner of the volume.
  • Replace <username> and <password> with the username and password credentials of the user that is the owner of the volume within this project.
  • [--name <backup_name>] <volume> are the typical arguments when creating a volume backup.