Changes between Version 29 and Version 30 of GEMINI/Tutorial/GEC19/GENI_Desktop_and_GEMINI_instrumentize/ExecuteExperiment


Ignore:
Timestamp:
03/15/14 20:55:48 (10 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEMINI/Tutorial/GEC19/GENI_Desktop_and_GEMINI_instrumentize/ExecuteExperiment

    v29 v30  
    3737 
    3838[[BR]][[BR]][[BR]]
    39  
    40 == Initialize Slice ==
    4139
    42 === What does Initialize mean ? ===
    43   In order to use the basic functionality of the !GeniDesktop, it is required to install and configure some slice, sliver and user information onto the Global Node (added by you to your slice on slice creation ). The following things happen during this operation
    44     * Software like webserver, MySQL Server,etc are installed on the Global Node.
    45     * SSH keys are generated dynamically on the Global Node. The public key is then installed on all the other nodes in your slice.
    46     * A software called [https://code.google.com/p/shellinabox/ Shellinabox] is installed on the Global Node and is used as a proxy to provide web-based SSH to all experimental nodes in your slice.
    47     * Authentication/Authorization setup is performed in order to access the the above mentioned services.
     40== The GENI Desktop Slice List Page ==
    4841
    49 === what does this do for my slice ? ===
    50   As you will see later in this session, you will now be able to use a web-console based terminal to connect to your experimental nodes just by clicking on a node in the topology diagram and a few clicks on a button. You will also be able to copy files to your nodes and the ability to run commands on your nodes simultaneouly using the web based tools provided by the !GeniDesktop.
     42Once you are logged into the GENI Desktop, you will be presented with the "Slice List" page as shown below.
    5143
    52 === So What do I do now ? ===
     44
     45    [[Image(wiki:GEMINI/Tutorial/Images:gec_has_init_button_arrow.png)]]
     46
     47The slice list page provides a list of all your slices.  It allows you to create new slices and to work with your existing slices.
     48Each line lists the name of the slice, a description of the RSPEC (if available), the number of Aggregate Managers (AMs) used by the slice,
     49whether the slice has resources (slivers) allocated to the slice, whether the slice lifetime should be automatically renewed by the GENI Desktop,
     50the slice's expiration date/time, and the next action to take on this slice. 
     51
     52In this exercise, we assume you have already created a slice and allocated slivers (resources) to the slice resulting in a
     53slice line like that shown above.  At this point your next step is to "Initialize" the slice for use in the GENI Desktop.
     54
     55== Initializing a Slice ==
     56
     57=== What does Initialize mean? ===
     58  In order to use the basic functionality of the !GeniDesktop, the !GeniDesktop must install and configure the Global Node (GN) -- which you added at slice creation time.  In particular, it must:
     59    * Install and configure software on the GN  such as the apache webserver, a mysql server, a content management system, etc.
     60    * Generate ssh keys dynamically on the Global Node, and then distribute the public key to the other nodes in the slice so that they can be controlled/monitored by the GN.
     61    * Install software called [https://code.google.com/p/shellinabox/ Shellinabox] on the Global Node which is used as a proxy to provide web-based ssh access to all other nodes in your slice.
     62    * Setup the necessary authentication/authorization in order to access the the above-mentioned services.
     63
     64=== Why is Initialize Needed? ===
     65  As you will see later in this session, once the slice is initialized, you will be able to use a web-based terminal to connect to your nodes just by clicking on a node in the topology diagram. You will also be able to copy files to your nodes and will have the ability to run commands on all the nodes (or a subset of nodes) in your topology at the same time.
     66
     67=== So What do I do next? ===
    5368
    5469Under the header "Next Action" there will be a button that will perform the next logical step for the slice. Once the resources are allocated, you can initialize the slice. The Next Action button will say "Initialize". Click it to start the Genidesktop Initialization process for that slice
     
    6782  Once you have your experiment running, you may want to collect statistics (system/network). The statistics may be collected using active probing of your slice or you may just want to collect data passively from the nodes. Active Tests can include bandwidth measurement tests, Round trip time and many others. These measurements are taken by actively sending traffic on the nodes and link in your slice. Passive measurements may include, monitoring the traffic flow on links/nodes, system statistics like CPU and Memory monitoring, monitoring of system processes, IP tables and routes where in no data is actually sent through your nodes/link. All data collected is from the activity being performed by you or the Testbed on your nodes. For this to happen, we utilize the [http://groups.geni.net/geni/wiki/GEMINIv3 GEMINI I&M] system which is installed, configured and setup for you during this phase. This involves installing a lot of software on your nodes including the global node. This operation can take quite a considerable amount of time depending on which Disk Image is loaded on your nodes. If using a GEMINI enabled Disk Image listed at [http://groups.geni.net/geni/wiki/GEMINIv3#GEMINIGlobalNodeImages this page], this phase should complete within 10 minutes. IF you use your own Disk Image on the nodes in your slice which is also supported by GEMINI, this phase may take about 30 minutes or sooner.
    6883
    69 === what does this do to my slice ? ===
     84=== Why is Instrumentize Needed? ===
    7085  Once instrumentized, you can use the full capability of the !GeniDesktop. This includes viewing network and system graphs, tabular data collected from your nodes, and reconfiguring the data you want collected and displayed. You also now have the ability to archive your data to your Irods account created at the !GeniPortal. Once instrumentized, there will be additional data collection routines and daemons running on your nodes. The additional system and memory load should be minimal though and should not affect the performance of your nodes. You should also be able to use features you had when you initialized your slice.
    7186