Open Stack

Thanks Alex!

On Mon, May 4, 2015 at 11:38 AM, Alex Meade <mr.alex.meade at gmail.com> wrote:

> Hey Erlon,
>
> The summit etherpad is here:
> https://etherpad.openstack.org/p/liberty-cinder-async-reporting
>
> It links to what we discussed in Paris. I will be filling it out this
> week. Also note, I have submitted this topic for a cross-project session:
> https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit#gid=827503418
>
> -Alex
>
> On Mon, May 4, 2015 at 3:30 AM, liuxinguo <liuxinguo at huawei.com> wrote:
>
>>   ·         I’m just trying to have a  analysis into it, maybe can begin
>> with the “wrapper around the python-cinderclient” as George Peristerakis
>> suggested.
>>
>>
>>
>>
>>
>> *发件人:* Erlon Cruz [mailto:sombrafam at gmail.com]
>> *发送时间:* 2015年4月27日 20:07
>> *收件人:* OpenStack Development Mailing List (not for usage questions)
>> *抄送:* Luozhen; Fanyaohong
>> *主题:* Re: [openstack-dev] [cinder] Is there any way to put the driver
>> backend error message to the horizon
>>
>>
>>
>> Alex,
>>
>>
>>
>> Any scratch of the solution you plan to propose?
>>
>>
>>
>> On Mon, Apr 27, 2015 at 5:57 AM, liuxinguo <liuxinguo at huawei.com> wrote:
>>
>> Thanks for your suggestion, George. But when I looked into
>> python-cinderclient (not very deep), I can not find the “wrapper around the
>> python-cinderclient” you have mentioned.
>>
>> Could you please give me a little more hint to find the “wrapper”?
>>
>>
>>
>> Thanks,
>>
>> Liu
>>
>>
>>
>>
>>
>> *发件人:* George Peristerakis [mailto:gperiste at redhat.com]
>> *发送时间:* 2015年4月13日 23:22
>> *收件人:* OpenStack Development Mailing List (not for usage questions)
>> *主题:* Re: [openstack-dev] [cinder] Is there any way to put the driver
>> backend error message to the horizon
>>
>>
>>
>> Hi Lui,
>>
>> I'm not familiar with the error you are trying to show, but Here's how
>> Horizon typically works. In the case of cinder, we have a wrapper around
>> the python-cinderclient which if the client sends a exception with a valid
>> message, by default Horizon will display the exception message. The message
>> can also be overridden in the translation file. So a good start is to look
>> in python-cinderclient and see if you could produce a more meaningful
>> message.
>>
>>
>> Cheers.
>> George
>>
>> On 10/04/15 06:16 AM, liuxinguo wrote:
>>
>> Hi,
>>
>>
>>
>> When we create a volume in the horizon, there may occurrs some errors at the driver
>>
>> backend, and the in horizon we just see a "error" in the volume status.
>>
>>
>>
>> So is there any way to put the error information to the horizon so users can know what happened exactly just from the horizon?
>>
>> Thanks,
>>
>> Liu
>>
>>
>>
>>
>>
>>  __________________________________________________________________________
>>
>> OpenStack Development Mailing List (not for usage questions)
>>
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150504/5fd37f4c/attachment.html>