Changes between Version 22 and Version 23 of GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute

10/21/13 11:29:11 (8 years ago)



  • GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute

    v22 v23  
    156 === 3.2 Running the init script ===
    158 The GIMI init script in Exper Mgmt Envir (EME) aims to interactively initialize the experiment environment for each user-running experiment.
    160 ==== 3.2.1 Tasks for Init Script ====
    161    * Get experiment name from user, and derive experiment-id
    162    * Retrieve project_id from omni or CH
    163    * Get list of slice_ids from omni or CH, select slice_id for this experiment
    164    * Get sliver_manifests_rspecs from AMs
    165    * Parse sliver_manifest_rspec to get slice_node_names (fully qualified)
    166    * Select default GIMI Portal, or override
    167    * Setup GSAS (iRODS) structure
    168       * derive defaults for user_irods_home_directory and
    169       * target(exper)-directory, or override
    170       * derive and load proj_exper_step_descriptors
    171       * load template OMF scripts
    172       * get user_irods_target(exper)_iticket, assigned to selcted GIMI Portal agent
    173    * Push sliver_manifest_rspecs and exp_descriptors to iRODS
    174    * Holding user_credentials, config GIMI Portal exper info:
    175       * user_identity
    176       * experiment_id,
    177       * project_id, and slice_id
    178       * slice_node_names
    179       * sliver_manifest_rspecs
    180       * user_irods_home_directory
    181       * user_irods_target(exper)_directory
    182       * user_irods_target(exper)_iticket
    184 ==== 3.2.2 GIMI Init installation ====
    185 This section describes the installation procedure
    188 ==== 3.2.3 How to run ====
    189 Open a terminal window and run:
    190 {{{
    191 python
    192 }}}
    193 The output should look like this:
    194 {{{
    195 Welcome to the GIMI initialization script, please make sure to install omni and set up your credential before running this script
    196 Are you creating a new experiment?
    197 }}}
    198 Since you are creating a new experiment enter “yes”.
    199 Your output should be the following:
    200 {{{
    201 Enter your preferred experiment path (please use absolute path, e.g., /home/geni/your/dir):
    202 }}}
    203 You will now need to input the path to the directory on your VM that you would like to store your experiment information in. [[BR]]
    204 For example you might want to store it your experiment files here:
    205 {{{
    206 /home/geni/GIMIexperiment
    207 }}}
    208 If the path doesn't already exist  your output will look like this:
    209 {{{
    210 Path doesn't exist, do you want me to create directory for you? (Yes or No)
    211 }}}
    212 Enter “yes” if you would like to create that directory.
    213 The init script will now ask you a few question about yourself to be put in the descriptor files that will accompany your experiment files.
    214 {{{
    215 Tell us about yourself: enter your name:
    216 }}}
    217 It will now ask for the organization you are a part of. This could be a company or university.
    218 {{{
    219 Your organization:
    220 }}}
    221 Next iRODS will be initialized. You should already have created  the file “~/.irods/.irodsEnv”. If you have not done this you will need to answer the iRODS questions with information from your iRODS account which you created in the GENI Portal. You can get additional information at [ HowToUseiRODS].
    222 [[BR]][[BR]]
    223 Your next output will list your slices and ask you to choose which slice you are using for this experiment.
    224 {{{
    225 Your user name is ...
    227 Your active slice names:
    228 ...
    229 ...
    231 Please enter your preferred slice name for this experiment:
    232 }}}
    233 After you enter which slice you would like to use, the output will tell you which slice you chose and which project that slice is a member of. Then it will ask you to name your experiment.
    234 {{{
    235 Your slice name is: ...
    236 Your project ID is:
    238 Enter your experiment name:
    239 }}}
    240 You will then be told the experiment ID. Then the output will look like this:
    241 {{{
    242 Retrieving the manifest rspec...
    243 Checking resources from aggregates... (this might take some time)
    244 }}}
    245 Depending on which aggregates your slice has resources, you should get additional output about where your resources were found. Here is an example:
    246 {{{
    247 Found resource in aggregate:
    248 }}}
    249 Next the OMF template scripts will be pushed to iRODS if they are not already there & iRODS will be set up for the experiment. You will also be given a ticket for the experiment directory that can be used to give other users access.
    250 {{{
    251 iRODS initial collection setup was successful
    253 Ticket for new directory: ...
    254 Ticket expiration date is set to: ...
    255 Do you want to push manifest to iRODS? (Yes or No)
    256 }}}
    257 You should push manifest to iRODS if you have already reserved your resources so enter “yes”.
    258 You should get the following output:
    259 {{{
    260 Manifest has been pushed to iRODS
    262 Pushing experiment information to GIMI Experiment Registry...
    263 Saving JSON to file:
    265 }}}
    266 This will be followed by the JSON files that are pushed to the registery. At the end of all this output you should see:
    267 {{{
    268 Pushed data to registry successfully
    269 }}}
    270 You have successfully run the GIMI initialization script.
    274 === 3.3 Experiment descriptor and iRODS ===
    276 '''Initial Experiment Collection'''
    277 This script sets up an experiment collection within the user's iRODS account. The user and GIMI will store objects associated with this experiment in this collection. In the example below the experiment collection is called “dbhat-Explabwiki-2013-07-16T22:11:42” .[[BR]]
    279 [[Image(checkinfoirods.png)]]
    281 [[BR]]
    283 '''Descriptor Files'''
    284 Descriptor files are generated which collect metadata about the experiment and objects being pushed into iRODS. These descriptor files are used to help organize and search for data. "project.xml" and “experiment.xml” are descriptor files created in each experiment collection. [[BR]]
    287 [[BR]]
    288 ''' Manifest Rspecs'''
    289 The user is asked if he would like the manifest rspecs from his slice to be added to this experiment collection in iRODS. If the user says yes, a new collection is created within the experiment collection. The manifest rspecs are then pushed to this new collection and descriptor files are created. In this example "manifest-keleigh-myFirstExperiment-2013-06-21T08:35:53.rspec" is a manifest rspec and "artifact.xml" and “step.xml” are descriptor files. [[BR]]
    291 [[BR]]
    293 '''Experiment Templates'''
    294 Template OMF scripts are added to the user's iRODS account in their own folder titled “experimentTemplates” the first time a user runs this script. These OMF scripts are also available in Labwiki[[BR]]
    297 [[BR]]
    299 === 3.4 Verification of Topology ===
     157=== 3.2 Verification of Topology ===
    300158After establishing the slice on which the experiment will be executed, the experimenter will be most likely
    301159be interested in verifying if the slice has been initiated correctly. In this tutorial, we use an [[ OMF experiment script]] that executes pings between neighboring nodes.
    459 === 3.5 Setup Routing in Experiment Topology ===
     317=== 3.3 Setup Routing in Experiment Topology ===
    460318In more complex topologies routing has to be set up. In our case, this is achieved with the aid of an [[ OMF experiment script]]. The one we use for this tutorial is shown below.
    513 === 3.6 Verification of Routing ===
     371=== 3.4 Verification of Routing ===
    514372After establishing the routing, we use an [[ OMF experiment script]] that executes pings between each pair of nodes that contains one hop, to verify the correctness of routing setup.
    771629'''Figure (2)'''
    772630=== 5.2 Plan ===
    773 Labwiki accounts have already been created for you for this tutorial. To use !LabWiki, go to [ GIMI portal] and login with the username and password you have been given.[[BR]]
     631There is a link to !LabWiki now available through the GENI Portal or you can click here to use !LabWiki
    787 The left column could contain the steps to run the experiment or general information about the experiment.[[BR]]
     646The left column could contain the steps to run the experiment or general information about the experiment.[[BR]] The scripts are written using a simple [ markdown scripts].
    804663=== 5.4 Execute ===
    806 Here, you can start your experiment and Visualise it. In the name tab, type in the name you wish to give the experiment. There are no particular rules for this.[[BR]]
    808 Under slice name, type in the name of your slice as you have entered in the Flukes tool while setting up your slice. [[BR]]
    809 Then. scroll towards the bottom of this column and under the tab named Graph, type 'true'.This enables the graph view on your execute column.[[BR]]
     665Here, you can start your experiment and Visualise it. In the name tab, type in the name you wish to give the experiment. Your name should only consist of alphanumeric characters. Only '_' is allowed as a special character.[[BR]]
     667==== 5.4.1 Add a Context ====
     669If you do not want to create a new context, skip this step. [[BR]]
     671At the top-right corner there is a button called 'Add Context'. This allows you to create an Experiment context which can be useful when you want to store related experiments in the same folder with associated metadata. This Context can then be browsed using the iRODs web interface. [[BR]]
     673Give the context a name, as shown below and click on 'Save': [[BR]]
     676==== 5.4.2 Run Experiment ====
     678Give your task a name. Select the Project, Experiment Context and Slice from the drop down menu on the screen.[[BR]]
     681Then scroll towards the bottom of this column and under the tab named Graph, type 'true'.This enables the graph view on your execute column.[[BR]]
    810684Once the experiment starts running you will be able to scroll down and view the graph.[[BR]]
    826700'''Figure (9)'''
     702At any point during the run of your experiment, click on Dump at the top of the Execute column to save your experiment data in iRODs.[[BR]]
    829704You can click and drag it to the Plan screen just above Figure 12. This will display the graph along with the experiment description. This graph is also dynamic.[[BR]]