Changes between Version 12 and Version 13 of GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute

07/18/13 16:29:34 (7 years ago)



  • GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute

    v12 v13  
    156 === 3.2 Verification of Topology ===
     156=== 3.2 Running the init script ===
     158The 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.3.2 GIMI Init installation ====
     185This section describes the installation procedure
     188==== 3.3.3 How to run ====
     189Open a terminal window and run:
     193The output should look like this:
     195Welcome to the GIMI initialization script, please make sure to install omni and set up your credential before running this script
     196Are you creating a new experiment?
     198Since you are creating a new experiment enter “yes”.
     199Your output should be the following:
     201Enter your preferred experiment path (please use absolute path, e.g., /home/geni/your/dir):
     203You will now need to input the path to the directory on your VM that you would like to store your experiment information in. [[BR]]
     204For example you might want to store it your experiment files here:
     208If the path doesn't already exist  your output will look like this:
     210Path doesn't exist, do you want me to create directory for you? (Yes or No)
     212Enter “yes” if you would like to create that directory.
     213The init script will now ask you a few question about yourself to be put in the descriptor files that will accompany your experiment files.
     215Tell us about yourself: enter your name:
     217It will now ask for the organization you are a part of. This could be a company or university.
     219Your organization:
     221Next 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].
     223Your next output will list your slices and ask you to choose which slice you are using for this experiment.
     225Your user name is ...
     227Your active slice names:
     231Please enter your preferred slice name for this experiment:
     233After 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.
     235Your slice name is: ...
     236Your project ID is:
     238Enter your experiment name:
     240You will then be told the experiment ID. Then the output will look like this:
     242Retrieving the manifest rspec...
     243Checking resources from aggregates... (this might take some time)
     245Depending on which aggregates your slice has resources, you should get additional output about where your resources were found. Here is an example:
     247Found resource in aggregate:
     249Next 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.
     251iRODS initial collection setup was successful
     253Ticket for new directory: ...
     254Ticket expiration date is set to: ...
     255Do you want to push manifest to iRODS? (Yes or No)
     257You should push manifest to iRODS if you have already reserved your resources so enter “yes”.
     258You should get the following output:
     260Manifest has been pushed to iRODS
     262Pushing experiment information to GIMI Experiment Registry...
     263Saving JSON to file:
     266This will be followed by the JSON files that are pushed to the registery. At the end of all this output you should see:
     268Pushed data to registry successfully
     270You have successfully run the GIMI initialization script.
     274==== 3.4 Experiment descriptor and iRODS ====
     276'''Initial Experiment Collection'''
     277This 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 “keleigh-myFirstExperiment-2013-06-21T08:35:53” .[[BR]]
     279[[Image(MainCollection.png, 100%)]]
     282'''Descriptor Files'''
     283Descriptor 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]]
     285[[Image(ExperimentCollection.png, 100%)]]
     287''' Manifest Rspecs'''
     288The 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]]
     290[[Image(ManifestCollection.png, 100%)]]
     293'''Experiment Templates'''
     294Template 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]]
     296[[Image(ExperimentTemplates.png, 100%)]]
     299== 4. Verification of Topology ==
    157300After establishing the slice on which the experiment will be executed, the experimenter will be most likely
    158301be 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.
    374 === 3.3 Setup Routing in Experiment Topology ===
     517=== 5. Setup Routing in Experiment Topology ===
    375518In 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.