1. Outline the proposed title of this feature request. Quota improvements for NooBaa OBCs
2. What is the nature and problem description of the request?{}OBC quotas are reactive instead of proactive. For example, you can successfully upload a 4Gb file to an OBC with a 1Gb quota, and it's only when the quota is met or surpassed that the quota is then enforced.

Noobaa OBCs should not allow an object to be uploaded if said object is surpasses the OBCs quota limit.

1. Why does the customer need this? (List the business requirements here)
   To make sure that individual users of OCP and ODF to not fill up OBCs past their quota limits.

1. Are there any Documentation Requirements for this request?
   No

1. Is the request coming from a specific customer or subset of customers (on prem only, cloud only, etc). Please don't mention any customer related sensitive information.
   Customer Name: BANK OF AMERICA

1. What is the urgency of the request?
   Major as it's effecting the customer's go-live date

1. Please provide contact information, in case of follow up questions.
   Email: bmcmurra@redhat.com

[Update March 12th]

After a meeting with the customer, we agreed to update the RFE and have the ask for the following
1. MCG is a distributed system, hence the computation must be asynchronous. With that said, we accept the need to have a smaller update cycle, hence we will accept the request to make it configuration without a change in the default value of 2 min. 
2.  New quota variable - number of buckets