Changes between Initial Version and Version 1 of INSTOOLSSummaryDeprecated

10/04/11 15:42:22 (11 years ago)



  • INSTOOLSSummaryDeprecated

    v1 v1  
     1= INSTOOLS, Instrumentation Tools =
     3[wiki:INSTOOLSSummaryDeprecated deprecated INSTOOLS Summary]
     5Instrumentation Tools (INSTOOLS) is a network instrumentation and measurement framework designed to make it easy to deploy network measurement infrastructure into a slice.  Once deployed, INSTOOLs allows the user to "see" the network behavior using a standard web browser.
     6From a user's viewpoint, there are basically two steps required to use INSTOOLs:
     7 * Instrument the Slice: The user runs a script that deploys the necessary network monitoring software into a slice which then begins collecting network traffic measurements for that slice -- see [wiki:Instrumentize instrumentize]
     8 * Visualize/Graph the Collected Measurements: After instrumenting the slice, the user is given a web page to visit in order to "see" a live view of the network traffic flowing through the slice.  Users can either use 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.
     9The 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.
     11Each slice receives its own Measurement Controllers (MCs). These machines are responsible for capturing the data. Currently the slice has at least one MC per aggregate. This ensures scalability and efficiency since each set of instrumentation tools is tailored to capture, record, and display only the desired information associated with that slice.
     13The MC's create a measurement plane which is separate from the data plane.  This minimizes interference with the slice caused by the various measurement tools.
     15To get started using INSTOOLS see  [wiki:Instrumentize instrumentize].
     17=== Videos ===
     19[attachment:instrumentize264.mp4 Adding Instrumentation To Slice] [[BR]]
     20[attachment:instools_live_view264.mp4 Instools Live View] [[BR]]
     21[attachment:portal264.mp4 Instools Portal] [[BR]]
     23=== Presentations ===
     25[ Protogeni Tutorial: USING INSTOOLS] GEC9
     27[  GEC7 Conference slides]  March, 2010
     29[ GEC6 Conference slides] November, 2009
     31[ Instrumentation Tools for a GENI Prototype], GEC3 Conference, 2008  (outlines the project goals and relationships with other projects).
     33[ An Instrumentation Approach for ProtoGENI-based Edulabs], GENI Measurement Workshop (June, 2009)
     35[ Kentucky INSTOOL update and proposed Shadowbox projects], GEC6 Conference, November 2009
     37[ INSTOOLS: Instrumentation Tools for a ProtoGENI Prototype], GEC6 Conference, November 2009