Changes between Version 6 and Version 7 of GEMINI/Tutorial/GEC20/GENI_Desktop_and_GEMINI_data/RetrieveData


Ignore:
Timestamp:
06/20/14 01:41:33 (5 years ago)
Author:
mkeele@indiana.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEMINI/Tutorial/GEC20/GENI_Desktop_and_GEMINI_data/RetrieveData

    v6 v7  
    99== Overview ==
    1010
    11 In the previous exercise, you may already have configured measurement probes via the GENI Desktop GUI. Here we are going to show you what happens in UNIS, the topology services of the backend periscope framework.
     11In the previous exercise, you may already have configured measurement probes via the GENI Desktop GUI. Here we are going to show you what happens in UNIS, the topology services that actually support and direct the measurements.
    1212
    1313[[BR]]
     
    1717[[Image(wiki:GEMINI/Tutorial/Images:IandM_diagram.png)]]
    1818[[BR]]
    19 The above diagram (a placeholder for now) shows the components of GEMINI framework.
    20 here's the link to the blipp repo and wiki page where you can investigate more about using blipp for your special probes
     19The above diagram shows the components of GEMINI framework. When a user reserve a slice and the slivers on the slice, hosts are created and connections between the hosts are built as well. Next step is to initialize and instrumentize these raw resources, and during this procedure, several tools are installed to your machines. BLiPP, the probe agent is installed at each measurement points. One task that BLiPP carries out is to run various kinds of probes including ping, iperf, traceroute etc. An users can either let these agents run some default probe or manually start probes at selected times.
     20here's the link [https://github.com/periscope-ps/blipp] to the BLiPP repo and wiki page where you can investigate more about using blipp for your special probes.
    2121
    2222[[BR]]
     
    2424== BLiPP generates Metadata and Data ==
    2525
    26 A review of generating data by running BLiPP (the second section about blipp should probably just focus on looking at the metadata and measurement objects in UNIS)
     26BLiPP runs user probes, parses the command line output and eventually uploads the result data to the measurement storage (MS). The MS is running at the Global Node and collecting data for the slice. Because there could be many kinds of measurement data collected at different experiment period, and they all can be large. We separate the data into Metadata and Data. The metadata should describe which particular measurement event a real data set belongs to and the metadata is stored at UNIS as bookkeeping information. The real data, on the other hands will be stored at the Global Node on the slices, so it should not overwhelm UNIS service. Realizing that there are three UNIS objects involved in the business: the measurement, the metadata of the measurement and the data of the metadata.
     27
     28[[BR]]
     29* The measurement object: a measurement object depict what probe the user want to use, and how to run this probe. It configures the probe command line arguments, user preference (e.g. how many times to repeat and what the interval is).
     30* The metadata object: it is a handle stored at UNIS to retrieve the real data on the Global Node on each slice. It is also the key information users should specify if they need to access their raw data.
     31* The data is the real output stored in the format of JSON
    2732
    2833[[BR]]