2ce5b11b1a
This patch changes the name of the Admin-Guide from the Cloud
Admin Guide to the Administrator guide. This affects the
filename in the repository, and references to cloud administrators
within the document texts.
1.) Changing instances of 'cloud administrator'
to 'administrator'.
2.) Change links from '/admin-guide-cloud/' to
'/admin-guide/' within the Admin Guide.
3.) Adjust .htaccess file.
Change-Id: I7f21a710e922981aa295afc0616de36fd819b523
Implements: blueprint user-guides-reorganised
118 lines
5.2 KiB
ReStructuredText
118 lines
5.2 KiB
ReStructuredText
.. _dashboard-set-quotas:
|
|
|
|
======================
|
|
View and manage quotas
|
|
======================
|
|
|
|
.. |nbsp| unicode:: 0xA0 .. nbsp
|
|
:trim:
|
|
|
|
To prevent system capacities from being exhausted without notification,
|
|
you can set up quotas. Quotas are operational limits. For example, the
|
|
number of gigabytes allowed for each tenant can be controlled so that
|
|
cloud resources are optimized. Quotas can be enforced at both the tenant
|
|
(or project) and the tenant-user level.
|
|
|
|
Typically, you change quotas when a project needs more than ten
|
|
volumes or 1 |nbsp| TB on a compute node.
|
|
|
|
Using the Dashboard, you can view default Compute and Block Storage
|
|
quotas for new tenants, as well as update quotas for existing tenants.
|
|
|
|
.. note::
|
|
|
|
Using the command-line interface, you can manage quotas for the
|
|
OpenStack Compute service, the OpenStack Block Storage service, and
|
|
the OpenStack Networking service (see `OpenStack Admin User Guide
|
|
<http://docs.openstack.org/user-guide-admin/cli_set_quotas.html>`_).
|
|
Additionally, you can update Compute service quotas for
|
|
tenant users.
|
|
|
|
The following table describes the Compute and Block Storage service quotas:
|
|
|
|
.. _compute_quotas:
|
|
|
|
**Quota Descriptions**
|
|
|
|
+--------------------+------------------------------------+---------------+
|
|
| Quota Name | Defines the number of | Service |
|
|
+====================+====================================+===============+
|
|
| Gigabytes | Volume gigabytes allowed for | Block Storage |
|
|
| | each project. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Instances | Instances allowed for each | Compute |
|
|
| | project. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Injected Files | Injected files allowed for each | Compute |
|
|
| | project. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Injected File | Content bytes allowed for each | Compute |
|
|
| Content Bytes | injected file. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Keypairs | Number of keypairs. | Compute |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Metadata Items | Metadata items allowed for each | Compute |
|
|
| | instance. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| RAM (MB) | RAM megabytes allowed for | Compute |
|
|
| | each instance. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Security Groups | Security groups allowed for each | Compute |
|
|
| | project. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Security Group | Rules allowed for each security | Compute |
|
|
| Rules | group. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Snapshots | Volume snapshots allowed for | Block Storage |
|
|
| | each project. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| VCPUs | Instance cores allowed for each | Compute |
|
|
| | project. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
| Volumes | Volumes allowed for each | Block Storage |
|
|
| | project. | |
|
|
+--------------------+------------------------------------+---------------+
|
|
|
|
.. _dashboard_view_quotas_procedure:
|
|
|
|
View default project quotas
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
#. Log in to the dashboard and select the :guilabel:`admin` project
|
|
from the drop-down list.
|
|
|
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
|
and click the :guilabel:`Defaults` category.
|
|
|
|
#. The default quota values are displayed.
|
|
|
|
.. note::
|
|
|
|
You can sort the table by clicking on either the
|
|
:guilabel:`Quota Name` or :guilabel:`Limit` column headers.
|
|
|
|
.. _dashboard_update_project_quotas:
|
|
|
|
Update project quotas
|
|
~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
#. Log in to the dashboard and select the :guilabel:`admin` project
|
|
from the drop-down list.
|
|
|
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
|
and click the :guilabel:`Defaults` category.
|
|
|
|
#. Click the :guilabel:`Update Defaults` button.
|
|
|
|
#. In the :guilabel:`Update Default Quotas` window,
|
|
you can edit the default quota values.
|
|
|
|
#. Click the :guilabel:`Update Defaults` button.
|
|
|
|
.. note::
|
|
|
|
The dashboard does not show all possible project quotas.
|
|
To view and update the quotas for a service, use its
|
|
command-line client. See `OpenStack Admin User Guide
|
|
<http://docs.openstack.org/user-guide-admin/cli_set_quotas.html>`_.
|