org
<mailto:openstack-dev@lists.openstack.org> >
Date: Friday, 6 April 2018 at 12:07
To: "'OpenStack Development Mailing List (not for usage questions)'"
<openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org> >
Subject: Re: [openstack-
[mailto:delightw...@ssu.ac.kr]
Sent: Thursday, April 5, 2018 10:53 AM
To: 'OpenStack Development Mailing List (not for usage questions)'
Subject: RE: [openstack-dev] [Vitrage] New proposal for analysis.
Hello Ifat,
Thanks for the good comments.
It was very helpful.
As you said, I tested
, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
Sent: Wednesday, April 4, 2018 4:21 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hi Minwook,
I discussed this issue with a Mistral contributor
e questions)"
<openstack-dev@lists.openstack.org>
Date: Tuesday, 3 April 2018 at 5:36
To: "'OpenStack Development Mailing List (not for usage questions)'"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hello Ifat,
I also th
: [openstack-dev] [Vitrage] New proposal for analysis.
Hi Minwook,
Thinking about it again, writing a new service for these checks might be an
unnecessary overhead. Have you considered using an existing tool, like
Zabbix, for running such checks? If you use Zabbix, you can define new
triggers
enStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hi Minwook,
I understand your concern about the security issue.
But how would that be different if the API call is passed through Vitrage API?
The authentication
velopment Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hi Minwook,
I understand your concern about the security issue.
But how would that be different if the API call is passed through Vitrage
API? The authentication from vitrage-
<openstack-dev@lists.openstack.org>
Date: Thursday, 29 March 2018 at 14:51
To: "'OpenStack Development Mailing List (not for usage questions)'"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hello Ifat,
Thanks for your r
(not for usage questions)
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hi Minwook,
Why do you think the request should pass through the Vitrage API? Why can’t
vitrage-dashboard call the check component directly?
And another question: what should happen if the user closes
Mailing List (not for usage questions)'"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hello Ifat and Vitrage team.
I would like to explain more about the implementation part of the mail I sent
last time.
The flow is as follows.
stions)'
Subject: Re: [openstack-dev] [Vitrage] New proposal for analysis.
Hello Ifat,
Thanks for your reply. : )
This proposal is a proposal that we expect to be useful from a user
perspective.
>From a manager's point of view, we need an implementation that minimizes
the overhead
Date: Tuesday, 27 March 2018 at 14:45
To: "openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org> "
<openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org> >
Subject: [openstack-dev] [Vitrage] New proposal for analysis.
Hello Vitrage t
: MinWookKim <delightw...@ssu.ac.kr>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: Tuesday, 27 March 2018 at 14:45
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
13 matches
Mail list logo
