openstack-manuals/doc/admin-guide-cloud/source/cli_cinder_quotas.rst
Gudrun Wolfgram 08f0c4aa46 Cloud Admin Guide CLI chapter
Moving (copying) Admin User Guide CLI content to
the Cloud Admin Guide as a part of the reorganization
goal. This patch does not include any new or original
content.

This patch is Part 1 to create a new command-
line client section for Admin Users in the Cloud Admin
Guide, as disucssed in the User Guide Specialty team
meetings.

1) Creating a new CLI section with cli.rst

2) Moving the non common files from user-guide-admin to
admin-guide-cloud, along with their sub files. (Rename
user-guide-admin files to user cli_ prefix in admin-
guide-cloud.)
manage_projects_users_and_roles.rst
nova_cli_manage_projects_security.rst
cli_manage_services.rst
cli_manage_shares.rst
cli_manage_flavors.rst
cli_admin_manage_environment.rst
cli_set_quotas.rst
analyzing-log-files-with-swift-cli.rst
cli_cinder_scheduling.rst

3) Attempt updates to several links.

Change-Id: I97f4ced4f5033c7e0f3bf00c410288a75699d110
Implements: blueprint user-guides-reorganised
2016-03-07 15:51:49 -06:00

4.7 KiB

Manage Block Storage service quotas

As an administrative user, you can update the OpenStack Block Storage service quotas for a project. You can also update the quota defaults for a new project.

Block Storage quotas

Property name Defines the number of

gigabytes

Volume gigabytes allowed for each project.

snapshots

Volume snapshots allowed for each project.

volumes

Volumes allowed for each project.

View Block Storage quotas

Administrative users can view Block Storage service quotas.

  1. Obtain the project ID.

    For example:

    $ project_id=$(openstack project show -f value -c id PROJECT_NAME)
  2. List the default quotas for a project (tenant):

    $ cinder quota-defaults PROJECT_ID

    For example:

    $ cinder quota-defaults $project_id
    +-----------+-------+
    |  Property | Value |
    +-----------+-------+
    | gigabytes |  1000 |
    | snapshots |   10  |
    |  volumes  |   10  |
    +-----------+-------+
  3. View Block Storage service quotas for a project (tenant):

    $ cinder quota-show PROJECT_ID

    For example:

    $ cinder quota-show $project_id
    +-----------+-------+
    |  Property | Value |
    +-----------+-------+
    | gigabytes |  1000 |
    | snapshots |   10  |
    |  volumes  |   10  |
    +-----------+-------+
  4. Show the current usage of a per-project quota:

    $ cinder quota-usage PROJECT_ID

    For example:

    $ cinder quota-usage $project_id
    +-----------+--------+----------+-------+
    |    Type   | In_use | Reserved | Limit |
    +-----------+--------+----------+-------+
    | gigabytes |   0    |    0     |  1000 |
    | snapshots |   0    |    0     |   10  |
    |  volumes  |   0    |    0     |   15  |
    +-----------+--------+----------+-------+

Edit and update Block Storage service quotas

Administrative users can edit and update Block Storage service quotas.

  1. Clear per-project quota limits.

    $ cinder quota-delete PROJECT_ID
  2. To update a default value for a new project, update the property in the cinder.quota section of the /etc/cinder/cinder.conf file. For more information, see the Block Storage Configuration Reference.

  3. To update Block Storage service quotas for an existing project (tenant)

    $ cinder quota-update --QUOTA_NAME QUOTA_VALUE PROJECT_ID

    Replace QUOTA_NAME with the quota that is to be updated, NEW_VALUE with the required new value, and PROJECT_ID with required project ID.

    For example:

    $ cinder quota-update --volumes 15 $project_id
    $ cinder quota-show $project_id
    +-----------+-------+
    |  Property | Value |
    +-----------+-------+
    | gigabytes |  1000 |
    | snapshots |   10  |
    |  volumes  |   15  |
    +-----------+-------+
  4. Clear per-project quota limits.

    $ cinder quota-delete PROJECT_ID

Remove a service

  1. Determine the binary and host of the service you want to remove.

    $ cinder service-list
    +------------------+----------------------+------+---------+-------+----------------------------+-----------------+
    |      Binary      |         Host         | Zone |  Status | State |         Updated_at         | Disabled Reason |
    +------------------+----------------------+------+---------+-------+----------------------------+-----------------+
    | cinder-scheduler |       devstack       | nova | enabled |   up  | 2015-10-13T15:21:48.000000 |        -        |
    |  cinder-volume   | devstack@lvmdriver-1 | nova | enabled |   up  | 2015-10-13T15:21:52.000000 |        -        |
    +------------------+----------------------+------+---------+-------+----------------------------+-----------------+
  2. Disable the service.

    $ cinder service-disable HOST_NAME BINARY_NAME
  3. Remove the service from the database.

    $ cinder-manage service remove BINARY_NAME HOST_NAME