Openstack Glance: user_total_quota size unit bytes

[Tzach Shefi]

Description of problem:

When you setting user_total_quota size is in bytes, unit should be in KB\MB\GB

Version-Release number of selected component (if applicable):
RHEL 6.5

python-glanceclient-0.12.0-1.el6ost.noarch
openstack-glance-2013.2-5.el6ost.noarch
python-glance-2013.2-5.el6ost.noarch

[Flavio Percoco (flaper87)]

I'm sorry but I don't understand why this should be represented in something else but bytes.

Image size is represented in bytes, so are quotas in other services throughout OpenStack. In order to keep consistency through the various resources we have, I think this bug should be closed as WONTFIX.

Could you please provide more info?

[Tzach Shefi (tshefi)]

From a user/admin point's of view who thinks in bytes any more, more so with large images in mind ?
Forcing users to convert MB/GB to bytes isn't smart as it would probably lead to user frustration / errors, in my opinion.

Using bytes throughout openstack doesn't necessarily mean it's good practice.
Example RHEL's Natulis and Window's file Explorer both show small files in byets/kb while larger files automatically show in MB/GB suffix.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/79582

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/80466

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/79582
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=cff35c1999997b6af62f4ef285d66f38b19433af
Submitter: Jenkins
Branch: master

commit cff35c1999997b6af62f4ef285d66f38b19433af
Author: Vaibhav Bhatkar <email address hidden>
Date: Tue Mar 11 09:53:20 2014 +0000

    user_storage_quota now accepts units with value

    user_storage_quota now accept value in B, KB, MB, GB
    or TB. The unit is optional. If no unit is specified
    Bytes is used as default.

    DocImpact

    Change-Id: Icc3f672869a5947cbcae38de92993c88ce0ef4e1
    Closes-Bug: #1261747