Changes between Version 11 and Version 12 of GEMINI/Tutorial/GEC20/GENI_Desktop_and_GEMINI_data/RetrieveData


Ignore:
Timestamp:
06/20/14 16:01:28 (6 years ago)
Author:
mkeele@indiana.edu
Comment:

install instructions

Legend:

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

    v11 v12  
    4444These HTTP requests to UNIS can be executed through the browser, a script, or via the command line. For a more detailed explaination of the UNIS RESTful API see [https://github.com/GENI-GEMINI/GEMINI/wiki/UNIS-REST-API]. A user can supply the same HTTP verbs to interact with the MS but remember that the MS is located on the Global Node for a given slice. For a more detailed explaination of the MS RESTful API see [https://github.com/GENI-GEMINI/GEMINI/wiki/MS-REST-API]. If you would like more information about how UNIS represents the individual components of a network see this detailed resource [http://monitor.incntre.iu.edu/docs/].
    4545
     46If you completed the previous exercise, [http://groups.geni.net/geni/wiki/GEMINI/Tutorial/GEC20/GENI_Desktop_and_GEMINI_blipp/ExecuteExperiment], then you should have an Instrumentized slice with a couple of Virtual Machines and a Global Node.
     47
     48[[Image()]]
     49
     50Above is a sample web server topology that will be used in this example. The GN0 node represents the Global Node and is where the MS runs and where data is collectioned. VM and VM-0 are the Measurement Points where BLiPP executes the probes we supply.
     51
     52* To access the GN0:   {{{ ssh username@pcvm2-4.instageni.illinois.edu }}} [[BR]]
     53* To access the VM:     {{{ ssh username@pc2.instageni.illinois.edu -p 33339 }}} [[BR]]
     54* To access the VM-0: {{{ ssh username@pc2.instageni.illinois.edu -p 33340 }}}
     55
     56If one of the machines asks for a password your ssh keys may not be in place. Visit [https://portal.geni.net/secure/profile.php] and click SSH Keys to download your keys.
     57 
     58Now lets login to the Global Node. Your command prompt should be similar to "[username@GN0]" for confirmation. There are a few important files to note on this machine. The file {{{ /usr/local/etc/node.info }}} contains information about your slice and what services it's using. This file can be found on any Global Node as it is created during the Instrumentation process. The file {{{ /usr/local/etc/certs/unis-proxy.pem }}} is the key, cert used to query the UNIS API, which is also created during the Instrumentation process.
     59
     60When making a request to the UNIS API you will need to supply your key, cert and also the UUID of your slice so that you only see your subsection of UNIS. The slice UUID can be found in the node.info with the following format, auth_uuid=fc028e53-cfbf-463d-9bf3-d26c35333b10.
     61
     62* For example, to query all the nodes on your slice: GET /nodes?properties.geni.slice_uuid=fc028e53-cfbf-463d-9bf3-d26c35333b10
     63
     64If you're going to be using a command line tool, such as curl, you will need to follow this structure to retrieve information from UNIS. Fortunately, we provide a python script [https://github.com/periscope-ps/unis/blob/master/example/unis_client.py] to help facilitate this process.
     65
     66If you would like to try a tool that handles your key, cert and slice uuid for you then you will need to install a dependency on the Global Node. For this example my Global Node is Fedora 15 but if you're using another image you can see more installation instructions here [https://github.com/periscope-ps/periscope/tree/master/peri-js].
     67
     68Install Dependency [[BR]]
     69{{{ cd /usr/src }}} [[BR]]
     70{{{ sudo wget http://nodejs.org/dist/v0.10.28/node-v0.10.28.tar.gz }}} [[BR]]
     71{{{ sudo tar -xvzf node-v0.10.28.tar.gz }}} [[BR]]
     72{{{ cd node-v0.10.28 }}} [[BR]]
     73{{{ sudo ./configure }}} [[BR]]
     74{{{ sudo make }}} [[BR]]
     75{{{ sudo make install }}} [[BR]]
     76
    4677[[BR]]