Open Stack

George

What has been said is that:
1) With an async API, there is no error from the client in the request.
e.g. for a create, the request returns success well before the backend has
been contacted about the request. There is no path back to the client with
which to send an error.

2) Quite often there is a desire for the admin to see error messages, but
not the tenant - this is especially true for managed / public clouds.

On 13 April 2015 at 18:21, George Peristerakis <gperiste at redhat.com> wrote:

>  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:unsubscribehttp://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
>
>


-- 
Duncan Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150413/eb48ffb5/attachment.html>