Comment 2 for bug 1827065

In this case, tests resource might cross the allowed quote on tested cloud. Quota set on your env either it is default or override is what you want to restrict due to HW resource etc. I am not sure how it will help to customize quota on tempest side ?

But in case quota is default/updated due to some other policy then yes you can customize quota on tests side to fully run the tests.

I would like to know the exact use case for that.