[openstack-dev] [Vitrage] New proposal for analysis.
Afek, Ifat (Nokia - IL/Kfar Sava)
ifat.afek at nokia.com
Tue Mar 27 17:22:59 UTC 2018
I think that from a user’s perspective, these are very good ideas.
I have some questions regarding the UX and the implementation, since I’m trying to think what could be the best way to execute such actions from Vitrage.
· I assume that these checks will not be implemented in Vitrage, and the results will not be stored in Vitrage, right? Vitrage role is to be a place where it is easy and intuitive for the user to execute external actions/checks.
· Do you expect the user to click an entity, select an action to run (e.g. ‘P2P check’), and wait by the open panel for the results? What if the user switches to another menu before the check is done? What if the user asks to run an additional check in parallel? What if the user wants to see again a previous result?
· Any thoughts of what component will implement those checks? Or maybe these will be just scripts?
· It could be nice if, as a result of an action check, a new alarm will be raised in Vitrage. A specific alarm with the additional details that were found. However, it might not be trivial to implement it. We could think about it as phase #2.
From: MinWookKim <delightwook at ssu.ac.kr>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Tuesday, 27 March 2018 at 14:45
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [Vitrage] New proposal for analysis.
Hello Vitrage team.
I am currently working on the Vitrage-Dashboard proposal for the ‘Add action list panel for entity click action’.
I would like to make a new proposal based on the action list panel mentioned above.
The new proposal is to provide multidimensional analysis capabilities in several entities that make up the infrastructure in the entity graph.
Vitrage's entity-graph allows us to efficiently monitor alarms from various monitoring tools.
In the current state, when there is a problem with the VM and Host, or when we want to check the status, we need to access the console individually for each VM and Host.
This situation causes unnecessary behavior when the number of VMs and hosts increases.
My new suggestion is that if we have a large number of vm and host, we do not need to directly connect to each VM, host console to enter the system command.
Instead, we can send a system command to VM and hosts in the cloud through this proposal. It is only checking results.
I have written some use-cases for an efficient explanation of the function.
From an implementation perspective, the goals of the proposal are:
1. To execute commands without installing any Agent / Client that can cause load on VM, Host.
2. I want to provide a simple UI so that users or administrators can get the desired information to multiple VMs and hosts.
3. I want to be able to grasp the results at a glance.
4. I want to implement a component that can support many additional scenarios in plug-in format.
I would be happy if you could comment on the proposal or ask questions.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev