I think #3 and #4 specified above should be reorganized as follows. From example it will give an idea about how user can get the tenant id.
---------------
3. To update Block Storage service quotas
cinder quota-update --quotaName newValue tenantID
For example:
$tenant=$(openstack project show -f value -c id tenant01)
$ cinder quota-update --volumes 15 $tenant
$ cinder quota-show tenant01
+-----------+-------+
| Property | Value |
+-----------+-------+
| gigabytes | 1000 |
| snapshots | 10 |
| volumes | 15 |
+-----------+-------+
--------------------------
Other thing I would change is use consistent naming - like tenant_NAME rather than TENANT_NAME or tenant_name, same for tenantID.
Also, in the section on 'remove a service', it encloses the parameters in '<>'
I think #3 and #4 specified above should be reorganized as follows. From example it will give an idea about how user can get the tenant id.
---------------
3. To update Block Storage service quotas
cinder quota-update --quotaName newValue tenantID
For example: $(openstack project show -f value -c id tenant01) ------- --+---- ---+ ------- --+---- ---+ ------- -+----- --+
$tenant=
$ cinder quota-update --volumes 15 $tenant
$ cinder quota-show tenant01
+--
| Property | Value |
+--
| gigabytes | 1000 |
| snapshots | 10 |
| volumes | 15 |
+---
------- ------- ------- -----
Other thing I would change is use consistent naming - like tenant_NAME rather than TENANT_NAME or tenant_name, same for tenantID.
Also, in the section on 'remove a service', it encloses the parameters in '<>'
Disable the service.
$ cinder service-disable <host> <binary>
I propose we change that to :
Disable the service.
$ cinder service-disable host binary
Please let me know if that will be acceptable