Open Stack

Hello Ifat.

 

Thanks for your comments.

 

The Performance Test action is completely independent of the Vitrage flow
and is simply an action that triggers an external Performance Test project.

 

Users can simply see the results on the Vitrage-Dashboard.

 

We can also exclude Performance Test from the action list if they are not
needed.

 

'set monitoring configure' is an example of an action that can be added. We
can discuss the addition of required actions in the vitrage-dashboard at the
development level.

 

In addition, my experience is to manually register entities in the
/etc/vitrage/zabbix_conf.yaml file to use the monitoring configuration using
zabbix and vitrage. Then restart the Entity-Graph service.

 

I think we can let this process automatically modify the zabbix_conf.yaml
file by right-clicking on the desired entity in the Vitrage-Dashboard. (I
think we can modify zabbix_conf.yaml automatically via SSH if we perform
that action. we can enter the required parameters for this. )

 

As such, we can discuss the list to be included in the right mouse button
action.

 

what do you think?

 

Best Regards,

Minwook.

 

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.afek at nokia.com] 
Sent: Thursday, December 14, 2017 11:18 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack][Vitrage] Vitrage Entity Graph
supports various actions according to mouse events for entities.

 

Hi MinWookKim,

 

I think that the right click is a good idea. 

 

Some questions:

 

*         Just to make sure I understood correctly – after the “performance
and load test”, do you expect to see the result on the selected resource, or
somewhere else?

*         What do you mean by “set monitoring configure”?

 

Best Regards,

Ifat.

 

 

From: 김민욱 <delightwook at ssu.ac.kr <mailto:delightwook at ssu.ac.kr> >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at lists.openstack.org
<mailto:openstack-dev at lists.openstack.org> >
Date: Thursday, 14 December 2017 at 8:29
To: "openstack-dev at lists.openstack.org
<mailto:openstack-dev at lists.openstack.org> "
<openstack-dev at lists.openstack.org
<mailto:openstack-dev at lists.openstack.org> >
Subject: [openstack-dev] [OpenStack][Vitrage] Vitrage Entity Graph supports
various actions according to mouse events for entities.

 

Hello.

 

I'm MinWookKim.

 

I have been discussing my proposal with the Vitrage PTL a while ago,

 

I want to get feedback from Vitrage contributors.

 

In conclusion, my suggestion is that when I right-click on the Entity Graph
provided by Vitrage, I want the user to perform various actions through the
UI.

 

These actions include many things, and they do not go through the Vitrage
interior.

 

Ask other projects directly.

 

This is similar to what appears when you right-click on an icon in Windows.

 

You can set various parameters for a specific action and pass it directly
to the project.

 

The actions I thought so far are:

1. Execution of Mistral workflow

2. Performance & Load Test using external project for Entity

3. Set monitorig configure?

 

# Workflow

 

Entity click & select action

      |

Vitrage-Dashboard -----> Mistral API -----> Execute Workflow

                               |

                               ------> Test Project API ----> Execute Test

 

I want to check the results of these actions on the UI. 

 

For example, if the Performance & Load Test action is triggered on an
Entity, the UI will display the following result.

 

Availability: 99.75%

Elapsed time: 59.66 secs

Data transferred: 10340918 bytes

Response time: 2.36 secs

 

The focus of this proposal is to provide a click action for the Entity to
provide convenience to the user.

 

What do you think?

 

Best Regards,

 

Minwook.

 

 

 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 15526 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171215/7714c67d/attachment.bin>