search

ssfffss / CloudMan

Data Center Monitoring and Management Tool
0 stars 0 forks source link

GUI for various triggers #1

Open kimececmuedu opened 9 years ago

kimececmuedu commented 9 years ago

We need to resolve different GUI for different trigger mechanisms

dajidan commented 9 years ago

Guide to Traffic Monitor, Agent Analyzer and GUI

Part 1 Traffic Monitor Traffic monitor is responsible for recording the traffic as packets pass through a physical machine.

This module can be started by typing the command line: (on each of the physical machine)

cd /home/ke/nf_test/; ./new_monitor.sh

But typically we do not invoke this manually, it's called by the agent analyzer in the jar file. But for debug purposes, we can run this tool along and check the traffic log file in: /home/ke/nf_test/traffic.log

The parameters involved in this module is the sampling rate of recording. This can be modified in the /home/ke/nf_test/new_monitor.sh.

Part 2 Agent Analyzer

This module is a jar file located in the same place as the first module, which is: /home/ke/nf_test/cloudman0.9.jar

When we want to invoke it, Make sure that we should first cd into the directory: /home/ke/nf_test/ This is very important as this jar file invokes the new_monitor.sh. If we call the jar file in other directory, the script can not be called successfully.

Part3 GUI

Currently, the version with most features is located at 10.1.0.13:/usr/share/tomcat/webapps/ROOT/cloudman/test.html

Kejiang can integrate it into our main page if we are satisfied with the GUI.

dajidan commented 9 years ago

The most popular bugs during maintenance and its corresponding solution

  1. Since now we use the IP-MAC cache table to discover the VMs, it's essential to check that the file: /home/cloudman/.json is ready and correct for each physical machine. The agent analyzer part relies on this file to know the existence of VMs.Sometimes the cache is outdated or after a reboot of physical machine, this file is empty and may cause the analyzer stop analyze. In such situation, Kejiang should run his script to get this file back to normal.
  2. The auto restart part in Kejiang's script is not working well now. The jar file should be called when we are already in its directory. This part should be changed.