Red Hat Bugzilla – Bug 1474744
[paid][online-stg] The user can use non-integer GiB to request more storages than it is limited in the storage quota.
Last modified: 2017-09-14 16:26:20 EDT
Pushing this out as the user can at most shoot over by 1Gi.
Some options I can think of on top of my head:
1. we could prevent users from specifying non-integer values
2. we could switch to using status values for quota
3. we could round up to the next integer to determine "request" for quota purposes
Did intend to reassign. Changing back.
From storage point of view, different backends have different rules. AWS, GCE and Cinder can allocate only whole GB (and Kubernetes rounds non-integer GBs up), while e.g. Gluster can allocate in MB. We could force all of them to round to GB, at least in quota calculations.
It would be nice if we could account also pvc.status.capacity which always holds the size of bound PV. Until a PVC is bound its spec.capacity would be used for quota and after binding its status.capacity would be used instead, as it reflects real size of allocated storage to the user.
Assigning to brad. This is a storage 'problem' not online specific. Jan has an idea. This might be an RFE. I'll let Brad and storage team decide how to run with this.