Managing a 500 MB share results in 500 GB share in HDS HNAS Driver

[Rodrigo Barbieri]

Whenever a user wants to manage an existing share that has a registered quota of less than 1GB using HDS HNAS Driver, the driver recognizes the quota number as GB, but it may be KB or MB. This causes the Manila quota to be drastically reduced, exhausted or even prevent share from being managed. As an example, managing a 500 MB share results in 500 GB share in HDS HNAS Driver.

[Erlon R. Cruz (sombrafam)]

Quota/share can be in 'TB' as well.

[Alyson (alyson-rodrigues-rosa)]

When its in 'TB' we transform to 'GB' using something like "quota * units.Ki"

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/224830
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=dd77cf98c1018531d0e539e915b3421bd14fc3e8
Submitter: Jenkins
Branch: master

commit dd77cf98c1018531d0e539e915b3421bd14fc3e8
Author: Alyson Rosa <email address hidden>
Date: Thu Sep 17 13:14:08 2015 -0300

    Fix HDS HNAS manage incorrect share size

    Method get_quota does not handle quotas smaller than 1 GB.
    When the share quota is KB or MB, get_quota transforms everything to GB.
    It is impacting directly on managing shares.
    As an example, managing a 500 MB share results in 500 GB share in HDS HNAS
    Driver.
    The unit TB was already being transformed in GB.

    This patch implements a condition to deny share with quota smaller than
    1GB.

    Closes-bug: #1496917
    Change-Id: I73edc1f413bd307a856702f8a024a8b50886207b