Changes between Version 46 and Version 47 of GENIExperimenter/Tutorials/GENIDesktop/GEC23/GENIDesktop_CLI


Ignore:
Timestamp:
06/12/15 13:11:29 (9 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/GENIDesktop/GEC23/GENIDesktop_CLI

    v46 v47  
    2525To Download the GENIDesktop CLI Tool, please log in to the GENIDesktop if you are not already logged in. Click on the setting wheel like icon on the far top-right of the page to launch the settings menu. Click on '''GDCLI''' button.
    2626
    27 [[Image(wiki:GEMINI/Tutorial/Images:settings_wheel.png, align=right)]]
     27[[Image(wiki:GEMINI/Tutorial/Images:settings_wheel.png)]]
    2828
    2929This takes you to the [https://genidesktop.netlab.uky.edu/stable/gdcli_instructions/gdcli_quickstart.php quick start guide] for the CLI .
    3030
    31 [[Image(wiki:GEMINI/Tutorial/Images:qs.png,400px, align=center)]]
     31[[Image(wiki:GEMINI/Tutorial/Images:qs.png,400px)]]
    3232
    3333
    34 Step 1 talks about downloading the appropriate installer for your operating system. We currently have installers for MAC OS, Windows and !Ubuntu/Debian (or any other debian based Linux OS). If you are using any other OS and have python 2.7 or greater (python 3.0 not supported), you can go ahead and use the python version of the GDCLI.
     34Step 1 talks about downloading the appropriate installer for your operating system. We currently have installers for MAC OS, Windows and !Ubuntu/Debian (or any other debian based Linux OS). If you are using any other OS and have python 2.7 or greater (python 3.0 is not supported), you can go ahead and use the python version of the GDCLI.  Otherwise, please download the appropriate installer package for your machine.
    3535
    3636[[Image(wiki:GEMINI/Tutorial/Images:accounts.png,400px)]]
     
    4444   1. Drag the gdcli-1.16 icon to the Applications icon.
    4545   1. Open a terminal window.
    46    1.Run the script /Applications/gdcli-1.16/addAliases.command. This script will add aliases for the various GENIDesktop CLI in your ~/.bash_profile or ~/.bash_login or ~/.profile. (The script looks for these files in this order).
     46   1. Run the script /Applications/gdcli-1.16/addAliases.command. This script will add aliases for the various GENIDesktop CLI in your ~/.bash_profile or ~/.bash_login or ~/.profile. (The script looks for these files in this order).
    4747
    4848 === Windows ===
     
    6060If you do not see this output or run into any error , please ask for help.
    6161 
    62  == STEP 2. Generate and Copy GDCLI key. ==
    63   If you never used the GENIDesktop CLI Tool before, you will have to first generate a gdcli key which is an authentication token used by the system. Click on the setting wheel like icon on the far top-right of the page to launch the settings menu. Click on '''Account''' button. Click the "generate key" button under '''GDCLI Key''' Section on the Account Settings page.
    64   Then copy the gdcli key for further use. Please save the key to a file since it will required in the next step.
     62 == STEP 2. Generate and Copy the GDCLI key. ==
     63  The first time you use the GENIDesktop CLI Tool, you will have to generate a gdcli key which is an authentication token used by the system. Click on the settings wheel icon on the top-right of the page to launch the settings menu. Click on '''Account''' button. Click the "generate key" button under '''GDCLI Key''' Section of the Account Settings page.
     64  Then copy the gdcli key into the clipboard of your windowing system so that it can be pasted in the next step.
    6565
    6666 == STEP 3. Enable the GDCLI using the GDCLI key. ==
    67  Open a terminal (command prompt if using Windows. Also cd c:\GDCLI .).
     67 Open a terminal (command prompt if using Windows. On Windows you also need to '''cd c:\GDCLI .''').
    6868
    6969
     
    7575
    7676
    77  == STEP 4. Using GENIDesktop CLI ==
     77 == STEP 4. Using the GENIDesktop CLI ==
    7878
    79  In this exercise we will use the existing slice that we had created for this tutorial. We assume here that you have "iperf" installed on your nodes in the previous sections of this tutorial. Please note down your slicename and projectname your slice belongs to. This will be needed as the command line parameters for this exercise. There are numerous operation that can be performed using the CLI, but this example will focus on three things
     79 In this exercise we will use the existing slice that we created earlier in this tutorial. We assume that you have "iperf" installed on your nodes from the previous sections of this tutorial. Please note down your slicename and the projectname your slice belongs to. This will be needed in the command line parameters for this exercise. There are numerous operation that can be performed using the CLI, but this example will focus on three things
    8080
    8181 * List your nodes
     
    8484 * View the traffic on the link graph after downloading the PNG
    8585
    86  A user may want to automate these steps using custom scripts which is what we would like to emphasize in this section. We have created
     86 We can automate the above steps using a GENI Desktop CLI script.   We have created example scripts for Mac/Linux and also for Windows:
    8787{{{
    8888#!html
     
    103103}}}
    104104
    105 If the script finishes sucessfully , windows users should see a folder window pop up with the relevant graphs in them. Linux/MAC users should see a folder called "mygraphs" appear on the Desktop which should contain the graph files. Double-clicking on them to view.
     105If the script finishes sucessfully , windows users should see a folder window pop up with the relevant graphs in them. Linux/MAC users should see a folder called "mygraphs" appear on their local window system's desktop which should contain the graph files. Double-click on them to view them.
    106106
    107107 Some of the sample GENIDesktop CLI operations are show below. These could be combined in a custom script like the one you just ran.