Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-05-04 Thread liuxinguo
· I’m just trying to have a analysisapp:ds:analysis into it, maybe can begin with the “wrapper around the python-cinderclient” as George Peristerakis suggested. 发件人: Erlon Cruz [mailto:sombra...@gmail.com] 发送时间: 2015年4月27日 20:07 收件人: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-05-04 Thread Alex Meade
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:

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-05-04 Thread Erlon Cruz
Thanks Alex! On Mon, May 4, 2015 at 11:38 AM, Alex Meade mr.alex.me...@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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-27 Thread liuxinguo
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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-27 Thread Erlon Cruz
Alex, Any scratch of the solution you plan to propose? On Mon, Apr 27, 2015 at 5:57 AM, liuxinguo liuxin...@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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-15 Thread hao wang
I prefer to the sub-state with a bit more detail. It will be simple for horizon or others to get the more detail error message from cinder. Maybe we can define some template messages(according to kinds of error reason, more general) to avoid specify driver info back to end user. 2015-04-14 0:24

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-13 Thread Alex Meade
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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-13 Thread Erlon Cruz
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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-13 Thread Duncan Thomas
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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-13 Thread George Peristerakis
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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-10 Thread Fox, Kevin M
Events shouldnt help much since the workflow is, user does something. It breaks with error notify admin then admin needs to figure out why... ideally there needs to be a field for why in the db, and the dashboard can show it to admins? Thanks, Kevin From:

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-10 Thread Duncan Thomas
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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-10 Thread Fox, Kevin M
True. I was thinking more of the horizon event thing that show for a few seconds, then vanish. not useful for this case... Maybe something like the way heat keeps track of events, but more globally then? A list of error events in the admin tab that admins should look at and clear?

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

2015-04-10 Thread gordon chung
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