Changes between Version 21 and Version 22 of INSTOOLSSummary


Ignore:
Timestamp:
10/04/11 17:58:22 (8 years ago)
Author:
carpenter@vis.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • INSTOOLSSummary

    v21 v22  
    55From a user's viewpoint, there are basically two steps required to use INSTOOLs:
    66 * Instrument the Slice: The user presses the "Instrumentize" button in [http://protogeni.net/flack.html FLACK] that deploys the necessary network monitoring software into a slice which then begins collecting network traffic measurements for that slice -- see [wiki:Instrumentize instrumentize]
    7  * Visualize/Graph the Collected Measurements: After instrumenting the slice, press the "Go to portal" button to visit the Portal View [wiki:SlicePortal INSTOOLS Portal] that shows the slice on a map and allows users to click on any link or node in the slice to see its performance.  A second interface [wiki:INSTOOLSInterface INSTOOLS Live View] provides a very detailed live view of the links and nodes supported by a particular aggregate.
     7 * Visualize/Graph the Collected Measurements: After instrumenting the slice, press the "Go to portal" button to visit the [wiki:SlicePortal INSTOOLS Portal View] that shows the slice on a map and allows users to click on any link or node in the slice to see its performance.  A second interface, [wiki:INSTOOLSInterface INSTOOLS Live View], provides a very detailed live view of the links and nodes supported by a particular aggregate.
    88The INSTOOLS framework is designed to make configuration, deployment, and visualization of measurement data easy. The INSTOOLS user does not need to be an expert in system administration or network management. The goal is not to reinvent the wheel, but, rather develop ways to automatically deploy and leverage existing tools. Network state information is typically more important than packet trace information, therefore many of the tools used measure data such as routing tables, packet counters (e.g., interface counters), cache entries (e.g., ARP, DNS, and NAT tables), processor load averages, memory statistics, host configurations, firewall rules, etc.
    99