From: "Yujun Zhang (ZTE)"
Date: Thursday, 1 June 2017 at 18:10
On Thu, Jun 1, 2017 at 10:49 PM Afek, Ifat (Nokia - IL/Kfar Sava)
mailto:ifat.a...@nokia.com>> wrote:
So for now we agree that we need to add a UI for configuration information and
datasources status.
Sounds good. In order to i
On Thu, Jun 1, 2017 at 10:49 PM Afek, Ifat (Nokia - IL/Kfar Sava) <
ifat.a...@nokia.com> wrote:
So for now we agree that we need to add a UI for configuration information
> and datasources status.
>
>
Sounds good. In order to implement in UI, we shall also need api to expose
them right?
--
Yujun
11:50
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [vitrage] error handling
On Tue, May 30, 2017 at 3:59 PM Afek, Ifat (Nokia - IL/Kfar Sava)
mailto:ifat.a...@nokia.com>> wrote:
Hi Yujun,
You started an interesting discussion. I t
iles are more for
the engineers to analyse the root cause.
> Best Regards,
>
> Ifat.
>
>
>
>
>
> *From: *"Yujun Zhang (ZTE)"
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)"
> *Date: *Monday, 29 May 2017 at 16
usage questions)"
Date: Monday, 29 May 2017 at 16:13
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [openstack-dev] [vitrage] error handling
Brought up by a recent code review, I think it worth a thorough discussion
about the error handling rule.
Brought up by a recent code review, I think it worth a thorough discussion
about the error handling rule.
I once read an article[1] from Joyent and it impressed me on the
distinguish between *Operational* errors vs. *programmer* errors. The
article is written for nodejs, but the principle also app
