Open Stack

I think there is a lot to discuss here and I would love to push for a
solution implemented in Liberty. I have a proposed summit session on this
topic (Asynchrounous Error Reporting). I also discussed this briefly at the
Kilo summit. I will work on formalizing some of these ideas and hopefully
we can pick a path forward at the summit.

Keep the discussion going :) I will try to organize everyones thoughts.

-Alex

On Mon, Apr 13, 2015 at 10:00 AM, Erlon Cruz <sombrafam at gmail.com> wrote:

> I like Duncan's idea. To have a dash in horizon where admin can see error
> events. It can hide backend details from tenants and  would save the time
> of browsing through logs seeking for the operations that  caused errors
> (the request id also should be logged in the metadata to allow further
> investigation). We have notice this problem while ago, and at the time we
> found this bug[1] about the same problem.
>
> [1] https://bugs.launchpad.net/horizon/+bug/1352516
>
>
> On Fri, Apr 10, 2015 at 5:26 PM, gordon chung <gord at live.ca> wrote:
>
>> > I'd say events are *more* useful in that workflow, not less, as long as
>> > they contain enough context. For example, the user creates a volume,
>> > tries to attach it which fails for some config error, so the user
>> > deletes it. With an event based model, the admin now has an error event
>> > in their queue. If we used a db field then the error status is
>> > potentially revived by the successful delete.
>>
>> +1
>>
>> Nova currently emits a good set of events and errors and we've found it
>> especially useful to debug / do postmortem analysis by collecting these
>> notifications and being able to view the entire workflow. we've found quite
>> a few occasions where the error popups presented in Horizon are not the
>> real error but just the last/wrapped error.
>>
>> there are various consumers that already collate these error
>> notifications from Nova and i don't think it's much of a change if any to
>> collect error notifications from Cinder. i don't think there's any change
>> from Ceilometer POV -- just publish to error topic.
>>
>> cheers,
>>
>> gord
>>
>> __________________________________________________________________________
>> 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/20150413/b7d932d0/attachment.html>