One of the problems with managing a large private cloud is integrating quota management into the existing financial process. When one of our Projects on our internal cloud wants to increase their quota they’ll need to file a request. That request will be compared against projected cluster capacity as well as certain financial models. If the request falls within certain parameters it’ll need larger finance approval before the quota can be allocated. There are a number of capacity folks who would be handling these requests, so there could be a race condition when multiple Projects request capacity at the same time. So not only do we need a way to grant and track quota increases, but also to have a concept of state management within a given quota request. The advantage of state management is an enterprise can track why and when a given quota increase was requested and granted. Especially if there’s a field to track an external reference ID (like a bug/ticket number). The big change is that we will no longer have one item in the DB per-Project-per-resource, but instead it’d be per-Project-per-resource-per-request. This means we’d also need to extend nova to support the concept of ‘Soft’ and ‘hard’ quota. Hard quota being what you can actually allocate against, and ‘soft’ quota would let you see what you have + what’s in the pipe for approval.
