pie chart doesn't display properly if total = 0

[Cindy Lu]

Example:

If you go to Admin > Project and change the number of volumes to 0 and then go to Project > Overview page, it shows Volumes Used 2 of 0. It shows as an empty pie chart.

Please see attached image.

[Cindy Lu (clu-m)]

It seems like when I try to modify Number of Instances or VCPUs (when I have those resources provisioned) to 0, it doesn't allow me to change the value. Maybe we should have the same behavior for Volumes to prevent the scenario above?

[Julie Pichon (jpichon)]

I suspect it's about matching the API behaviour again. Nova doesn't allow to set quotas under current utilisation (for now - http://lists.openstack.org/pipermail/openstack-dev/2014-June/038014.html ) but when the APIs allow it it's a useful feature for cloud admins. I don't see a problem with the graph (I think it was fixed to look like this as part of bug 1263232?) but if you have an idea for how it should look like in these cases maybe we can apply it. Maybe it should be full and entirely red since the user is at capacity?

[Liz Blanchard (lblanchard)]

It would definitely make sense to me to represent this as "At full capacity" and even perhaps added a message saying over capacity if possible. Is the idea that once the user deletes these volumes that they won't be able to create new ones since their Quota is now 0? Is there a plan to somehow gracefully let the user know that they are currently over capacity due to quota changes and that they should remove the volumes (or whichever item) at their convenience?

[Victoria Martinez de la Cruz (vkmc)]

Maybe we could let the user know about this behavior when the quota is changed to a number lower than the current utilization and change the look of an 'over utilized' resource so it's distinguishable from a 'no utilized' resource.

On the other hand, it would be nice if all the resources behaves accordingly. That's it, allowing the admin to set quotas under current utilization for all resources and reflecting this in ux as mentioned above.

It looks like Nova folks are working on this, so we could fix it for the services that allow over utilization and then submit a follow up patch to make this consistent for Nova resources.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/119427
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=087ccfe740b627ca687b5c8727453dedcf2998cd
Submitter: Jenkins
Branch: master

commit 087ccfe740b627ca687b5c8727453dedcf2998cd
Author: Bradley Jones <email address hidden>
Date: Fri Sep 5 18:43:05 2014 +0100

    Updated overview graph when usage exceeds quota

    Change-Id: Iee24a70c77e7565cb04846f872af4f489165aa05
    Closes-bug: 1333483
    Closes-bug: 1407715