Ah, nice, wasn’t aware. Mateusz is one of the Horizon experts here at CERN I was referring to :)
On 25 Sep 2017, at 10:41, Massimo Sgaravatto <massimo.sgarava...@gmail.com<mailto:massimo.sgarava...@gmail.com>> wrote: Just found that there is already this one: https://bugs.launchpad.net/horizon/+bug/1717342 2017-09-25 10:28 GMT+02:00 Saverio Proto <ziopr...@gmail.com<mailto:ziopr...@gmail.com>>: Yes I am interested. Are you going to push them to gerrit ? Should we open a bug to track this change into Horizon ? massimo do you want to open the bug on Launchpad ? So if Arne pushed the patches on gerrit we can link them to the bug. I pointed robcresswell to this thread, he is reading us. thanks ! Saverio 2017-09-25 10:13 GMT+02:00 Arne Wiebalck <arne.wieba...@cern.ch<mailto:arne.wieba...@cern.ch>>: > Massimo, Saverio, > > We faced the same issue and have created patches for Horizon to display > - the per volume quota in the volume request panel, and also > - additional information about the volume type (like IOPS and throughput > limits, intended usage etc.) > > The patches will need some polishing before being sent upstream (I’ll need > need to cross-check with our Horizon experts), but we use them in prod since > quite a while and are happy to already share patch files if you’re interested. > > Cheers, > Arne > > > >> On 25 Sep 2017, at 09:58, Saverio Proto >> <ziopr...@gmail.com<mailto:ziopr...@gmail.com>> wrote: >> >> I am pinging on IRC robcresswell from the Horizon project. He is still >> PTL I think. >> If you are on IRC please join #openstack-horizon. >> >> We should ask the Horizon PTL how to get this feature request into >> implementation. >> >> With the command line interface, can you already see the two different >> quotas for the two different volume types ? Can you paste an example >> output from the CLI ? >> >> thank you >> >> Saverio >> >> >> 2017-09-25 9:55 GMT+02:00 Massimo Sgaravatto >> <massimo.sgarava...@gmail.com<mailto:massimo.sgarava...@gmail.com>>: >>> We are currently running Mitaka (preparing to update to Ocata). I see the >>> same behavior on an Ocata based testbed >>> >>> Thanks, Massimo >>> >>> 2017-09-25 9:50 GMT+02:00 Saverio Proto >>> <ziopr...@gmail.com<mailto:ziopr...@gmail.com>>: >>>> >>>> Hello Massimo, >>>> >>>> what is your version of Openstack ?? >>>> >>>> thank you >>>> >>>> Saverio >>>> >>>> 2017-09-25 9:13 GMT+02:00 Massimo Sgaravatto >>>> <massimo.sgarava...@gmail.com<mailto:massimo.sgarava...@gmail.com>>: >>>>> Hi >>>>> >>>>> >>>>> In our OpenStack cloud we have two backends for Cinder (exposed using >>>>> two >>>>> volume types), and we set different quotas for these two volume types. >>>>> >>>>> The problem happens when a user, using the dashboard, tries to create a >>>>> volume using a volume type for which the project quota is over: >>>>> >>>>> - the reported error message simply reports "unable to create volume", >>>>> without mentioning that the problem is with quota >>>>> >>>>> - (by default) the dashboard only shows the overall Cinder quota (and >>>>> not >>>>> the quota per volume) >>>>> >>>>> >>>>> Do you know if it possible in some to expose on the dashboard the cinder >>>>> quota per volume type ? >>>>> >>>>> >>>>> Thanks, Massimo >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> OpenStack-operators mailing list >>>>> OpenStack-operators@lists.openstack.org<mailto:OpenStack-operators@lists.openstack.org> >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>>> >>> >>> >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org<mailto:OpenStack-operators@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -- > Arne Wiebalck > CERN IT > -- Arne Wiebalck CERN IT
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators