Ask Your Question

project quota could overlap?

asked 2013-09-27 05:30:50 -0600

ArKam gravatar image

updated 2014-01-22 15:13:07 -0600

Evgeny gravatar image

From what I see and understand of Quotas, they are not detected or provisioned by the differents services of OS.

So, for exemple, if I have 1 node for Cloud Controller, which exclusively aim to control and manage Compute/Volume nodes, hosting Glance/Quantum/keystone and Horizon services only, and let say, 1 node hosting Compute/Network Agent and Volume services only.

This last host is a Dell M610 Lame Server with 32Gb Ram, 2xIntel Xeon E5520, 500GB HDD (iSCSI Provided) and a root filesytem of 67GB which is not see by OS component.

If I go to the dashboard, default Quotas for my installation will be: RAM: 64GB HDD: 1TB vCPU: 20

Which seems to be hardcoded compared to the available hardware. So, let say once again that I create four projets as follow:


Those four projects come with the exact same default Quotas, but differents users, which are not aware of others. If every user create maximum ressources available instances at the same time I'll probably have errors throwing up because of the overcapaciting isn't it?

I mean don't would have been more logical to have a default Quotas detected and dependant of the actual ressources and then projects allowed Quotas dependant of the ressources allocated on the earlier projects?

I don't know if I'm crystal clear here and can reformulate my question if it's not enough.

PS: This question is not indeed a technical one but rather an opened one based on what I experiment on OS.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-05-03 05:33:06 -0600

Yes, openstack projects has a default quota limit and it is not based on the available hardware capacity. I believe this is the perfect way to handle this, because nova-compute nodes are scalable and you may include any number of compute servers with different configurations overtime, and you can also create aggregates and map flavors to specific nova nodes (Example: you can create SSD based flavors for compute nodes with SSD disks) . Also there is a over commitment parameter in effect, which you can change at anytime based on your capacity needs. With this complications, it is not logical for a dashboard to display the quota based on available resources.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-09-27 05:30:50 -0600

Seen: 107 times

Last updated: May 03 '16