Migrating Desktop

 

Next exercise Back to menu

 

Requirements:

Every user should have a valid CrossGrid certificate. Account and certificate issues should be resolved before the tutorial takes place, so the user will not be faced with such problems just at the beginning of the tutorial. For the description and meaning of the fields please refer to the User Guide (http://wp3.crossgrid.org/ ). The User Guide is also available on-line after clicking on the proper desktop icon .

 

 

I. Goal: to get familiar with user-friendly Migrating Desktop environment, to learn a few basic operations, to understand what advanced functionality the Migrating Desktop provides.

 

Steps:

  1. Start web browser capable of executing Java applets goes to the address of Migrating Desktop (the applet should be loaded automatically), see chapter 2.2. You should be equipped with private certificate and key, give a path to them. In Server settings tab, specify port number 8443. Hostname: willow.crossgrid.man.poznan.pl (or any given by a tutor).

 

  1. Learn a few basics on creating windows, adding shortcuts to local or remote files (user Virtual Directory), saving his profile (User Profile database).

 

 

  1. Make a file transfer with chosen file and source/destination sites (using Grid Commander). Try to connect to Private Storage, GridFTP and FTP server (menu CONNECTIONS).

 

II. Goal: to run both simple job and full Grid application using the tools and infrastructure delivered by the CrossGrid project.

         Tutorial-dedicated MPI application component

         Migrating Desktop Job Wizard

         Application Scheduler with MPI scheduling facility (example of running crossgrid application)

 

Steps:

 

  1. The first exercise consists of simple batch job submission (like ‘/bin/ps’ command). Open Migrating Desktop and invoke a Job Wizard with commandline application.

 

 

 

 

 

In this dialog box you must specify the logical names for standard unix streams: output and error. If you do not define them, the computational results become lost. Clock on the three dots. The Grid Explorer will occur (similar to this one):

 

At the beginning, you have no additional filesystem mounted to the file tree. Virtual Directory is your grid home directory. Create a new folder and give a new filenames for stdout and stderr streams in it. These are only logical names stored in a repository. After execution of job, they will suppose to be filled with data. Stdout at least. These files are type “out”, no refresh rate is needed.

 

 

 

 

 

 

 

 

Go to Files tab, and choose StdOutput item, then press Visualize button. The proper visualiser will be launched automatically. In this case, text viewer. You can also refer to the Grid Commander, and do some well-known file operation on the output file.

 

 

  1. The second MD submission exercise takes place with real grid application choosing the provided MPI application (eg. Air Pollution)

 

 

Executable path (DESCRIPTION tab) set to: /flatfiles/SE00/cg/wp1_4_4/STEMII_SE00.exe

hostname (RESOURCES -> DEFINITION) set to: cg01.ific.uv.es:2119/jobmanager-pbs-infinite

Job type set to ‘mpich’, give a number of spawned processes.

Choose FILES (add Name=mapadebits.bmp, StdError and StdOutput and create them in their virtual space – use Grid Explorer), set Refresh=number of seconds, eg.: 5 – mapadebits refresh, eg.:

 

 

 

 

You should be able to observe the example of semi-interactivity support in MD environment. No full interaction provided in that exercise.

 

 

 

Comments:

 

Tutorial Application description:

 

New feature worth testing:

Multiple private storage accessing.

MPI jobs submission.

 

Next exercise Back to menu