Ask Your Question

Why is quota charged for shutdown instances?

asked 2013-08-26 11:32:02 -0600

sigrist gravatar image

updated 2013-08-26 13:20:22 -0600

Hi OpenStack folks!

I have a brand new private cloud setup for development using Ubuntu 12.04 and OpenStack grizzly.

I just noticed behavior that is quite undesirable for my purposes: shutdown machines still cause tenant quotas to be charged for VCPUs and RAM, even though they are actually utilizing neither.

Since I intend to keep around some shutdown machines in case I need them, this is quite undesirable as I will run out of quota while still having spare compute capacity to use.

Can anyone tell me if this is an OpenStack bug or if there is a way to configure quotas so that shutdown machines won't charge VCPUs and RAM?

Please let me know.


-- thiago

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-08-27 04:35:28 -0600

updated 2013-08-27 04:36:01 -0600

I think this is just to restrict the overallocation of resources, shutdown instances may not be using the VCPUs and RAM as you mentioned but they will consume anytime they are started & being shutdown, starting it is at users wish. If you want to tweak it specifically for your requirement, you can tweak it with updating the quotas explicitly, but it will be users resposibility to manage the number of running hosts.

edit flag offensive delete link more


Thanks for your answer! That's what I imagined, unfortunately. It would be cool if there was a way to tweak how quotas are charged. For example, for my requirements I would not charge VCPU or RAM for shutdown instances, but other users might have other requirements. :)

sigrist gravatar imagesigrist ( 2013-08-27 06:03:44 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-08-26 11:32:02 -0600

Seen: 216 times

Last updated: Aug 27 '13