Open Stack

Maybe cinder can emit more notification events, then a dashboard can be
build separately with the appropriate access control and filtering? The
same dash can then be used for many projects - all they need to add are the
events with enough metadata
On 10 Apr 2015 18:53, "Ben Swartzlander" <ben at swartzlander.org> wrote:

>  On 04/10/2015 08:11 AM, John Griffith wrote:
>
>
>
> On Fri, Apr 10, 2015 at 6:16 AM, liuxinguo <liuxinguo at huawei.com> 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
>>
>>  ​The challenge here is that the calls to the driver are async, so we
> don't actually have any direct feedback/messages regarding the result.  One
> thing that's been talked about in the past is adding additional information
> to the status which could be presented so that end users and tools like
> Horizon would have a little more information.
>
>  The trick is however we also do NOT want driver info going back to the
> end user, the whole point of Cinder is to abstract all of that backend
> specific type stuff.  The idea kicked around in the past was to introduce a
> sub-state with a bit more detail, but still wouldn't be anything specific
> from the driver.
>
>  Sounds like a good topic to revisit for the Liberty release.​
>
>
>
> Agreed that driver messages shouldn't reach the end user, but would it be
> helpful at all to the administrator to have driver error messages visible
> on the admin panel?
>
> -Ben
>
>
>
>
> __________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150410/5fd3334c/attachment.html>