Cinder

How can I change quota of total volume size?

Asked by Koji

Hi,

I'm trying to figure out how to change the quota of total volume size. I have one cinder volume which should be able to have about 2.5T total. It seems 1TB is defalt and I found out "osapi_max_limit = 1000" by "cinder-manage config list". I changed it to 2000, but no luck.

I would really appriciate if some of you can help me to figure this out.

Thanks in advance.
Koji

Question information

Language:
English Edit question
Status:
Solved
For:
Cinder Edit question
Assignee:
No assignee Edit question
Solved by:
Koji
Solved:
Last query:
Last reply:

This question was reopened

  • by Koji
Revision history for this message
Koji (kj-tanaka) said : 		#1

I found out the command. Thanks.

cinder quota-update [--volumes <volumes>] [--gigabytes <gigabytes>] <tenant_id>

Revision history for this message
Koji (kj-tanaka) said : 		#2

Ah... The command doesn't seem working. cinder quota-defaults keep showing 1000. Is it because I have keystone?

+-----------+-------+
| Property | Value |
 +-----------+-------+
| gigabytes | 1000 |
| volumes | 10 |
 +-----------+-------+

Also, here's absolute-limits.
cinder absolute-limits
+-------------------------+-------+
| Name | Value |
 +-------------------------+-------+
| maxTotalVolumeGigabytes | 1000 |
| maxTotalVolumes | 10 |
 +-------------------------+-------+

I would really appreciate any help. Thanks.

Revision history for this message
Jason (zzs) said : 		#3

Can you try to modify the quota_gigabytes instead of osapi_max_limit.

Revision history for this message
Koji (kj-tanaka) said : 		#4

Thank you Jason. I could change it to 2400.
+-----------+-------+
| Property | Value |
 +-----------+-------+
| gigabytes | 2400 |
| volumes | 10 |
 +-----------+-------+

But, I still get an "ERROR: VolumeSizeExceedsAvailableQuota". Do you know if there is another limitation, like a limit per user or something?

I already have a 900G volume, so I should be able to add a 1500G volume, but when I execute "cinder create 1400" or "nova volume-create 1400" I get this error.
ERROR: VolumeSizeExceedsAvailableQuota: Requested volume exceeds allowed volume size quota (HTTP 413) (Request-ID: req-XXXXXXXXXXXXXXXXXXXXXXXXXXX)

Revision history for this message
Jason (zzs) said : 		#5

Can you sure you restart all the related services and the database data is updated?

Revision history for this message
Koji (kj-tanaka) said : 		#6

Yes, I restarted cinder-api, cinder-scheduler and cinder-volume several times. I tried to restart them and tried stop-start them, but no luck...

And, I see these outputs in --debug.

reply: 'HTTP/1.1 413 Request Entity Too Large\r\n'
header: Retry-After: 0
header: Content-Length: 143
header: Content-Type: application/json
header: X-Compute-Request-Id: req-2a3d4c6f-8b4d-4f36-949f-133436e630a2
header: Date: Thu, 04 Apr 2013 19:50:24 GMT
DEBUG (shell:473) VolumeSizeExceedsAvailableQuota: Requested volume exceeds allowed volume size quota (HTTP 413) (Request-ID: req-2a3d4c6f-8b4d-4f36-949f-133436e630a2)

So, I'll look into database and see if I can find something...

Thanks

Revision history for this message
Jason (zzs) said : 		#7

How did you install the OpenStack and which version are you using?

Revision history for this message
Koji (kj-tanaka) said : 		#8

Jason, I could figure this out. My big mistake is this.

cinder quota-update --gigabytes 2500
cinder quota-show demo
+-----------+-------+
| Property | Value |
 +-----------+-------+
| gigabytes | 2500 |
| volumes | 10 |
 +-----------+-------+

Correct procedure is this.

cinder quota-update --gigabytes 2500 04b61dc833c3450eb15e95df3a9d0276
cinder quota-show demo
+-----------+-------+
| Property | Value |
 +-----------+-------+
| gigabytes | 2500 |
| volumes | 10 |
 +-----------+-------+

I think it would be great if cinder shows some error when user try to update some inexistent tenant-id, because on nova client, id and name work fine. At least, it should show some error... I hope.

Revision history for this message
Koji (kj-tanaka) said : 		#9

Well, I wrote wrong the previous comment.

Correct procedure is this. Tenant-id, not tenant name.

cinder quota-update --gigabytes 2500 04b61dc833c3450eb15e95df3a9d0276
cinder quota-show 04b61dc833c3450eb15e95df3a9d0276
+-----------+-------+
| Property | Value |
 +-----------+-------+
| gigabytes | 2500 |
| volumes | 10 |
 +-----------+-------+

Revision history for this message
Lucas Ribeiro (lucasribeiro1990) said : 		#10

Hi.
I really thanks for this. I was suffering in it trying to find out the way to change these quotas.

But, I just didn't understand something, shouldn't it be a bug/improvement?

Because even if you inform an incorrect information (in this case the tenant name) cinder returns some information related.
I tested it changing the quotas by "cinder quota-update" using admin and demo, and I have checked if you inform the tenant name it makes changes.

Revision history for this message
Bart Wensley (bartwensley) said : 		#11

This is a bug and is captured at: https://bugs.launchpad.net/cinder/+bug/1307487

Revision history for this message
Dan Bode (bodepd) said : 		#12

I have a related question here, I'm trying to update quota information from /etc/cinder/cinder.conf. For example:

quota_snapshots=250

I noticed that these values take effect during the initialization of cinder, but that they are not updated when I make modifications to the config files. Is updating these values are supported use case?