Open Stack

Nectar would absolutely love for this to get off the ground. We have just the one region with many AZ’s and to be able to quota on an AZ would be great.

I can help in terms of use cases but we are pretty light on the developer front at the moment. We can throw money at someone else for this though I think.

Cheers,
Sam



> On 20 Nov 2018, at 11:33 pm, Lance Bragstad <lbragstad at gmail.com> wrote:
> 
> Unified limits cropped up in a few discussions last week. After describing the current implementation of limits, namely the attributes that make up a limit, someone asked if availability zones were on the roadmap.
> 
> Ideally, it sounded like they had multiple AZs in a single region, and they wanted to be able to limit usage within the AZ. With the current implementation, regions would be the smallest unit of a deployment they could limit (e.g., limit project Foo to only using 64 compute cores within RegionOne). Instead, the idea would be to limit the number of resources for that project on an AZ within a region.
> 
> What do people think about adding availability zones to limits? Should it be an official attribute in keystone? What other services would need this outside of nova?
> 
> There were a few other interesting cases that popped up, but I figured we could start here. I can start another thread if needed and we can keep this specific to discussing limits + AZs.
> 
> Thoughts?
> 
>