CNGrid GOS 3.0 Practice OMII-Euro & CNGrid Joint Training Material QiaoJian Jan

2 Outline  Introduction  Part 1: User-level practice (App Portal)  Part 2: Admin-level practice (Mgmt Portal)

3 Introduction  Originally, we intended to use our 3-node testing environment to support the exercise, but it’s occupied now for robustness testing.  So here we will use the newly installed one- node environment kindly provided by HKU to do the CNGrid GOS 3.0 demonstration. –Portal server: –Backend Server:  This exercise is to show the basic functions on CNGrid GOS 3.0. For more information, pls come to our website : – –See “Material” Section on the left side

4 Part 1: User-Level Operation  Step1.1: Login onto GOS3.0 portal  Step1.2: Submit a grid job  Step1.3: Get global job records  Step1.4: Query job details  Step1.5: Get job output  Step1.6: Manipulate files in job directory  Step1.7: Manage job  Step1.8: Accounting facilities  Step1.9: File facilities

5 Step1.1: Login onto GOS3.0 portal  Get your Login Username and Passwords: –We have prepared one username for each column: –E.g: Users in column 1: UserName is : Password is: demo001  Each Login Account has been mapped onto one local linux account on this testing node. –e.g: is mapped to demoHKU001 The password for this local username is: ictgos3

6 Step1.1: Login onto GOS3.0 portal  Please open your Internet Browser –Both IE and Firefox is okay, Firefox is strongly recommended –“ Start ”  “ All Programs ”  “ Mozilla Firefox ”  Type in the URL of the GOS Application Portal  Type in your Grid account and password:

7 Step1.2: Submit a grid job  The administrator has added two types of software into this testing grid node: – Blast : Basic Local Alignment Search Tool DNA & Protein sequence searching – General : the simplest application for testing You may specify any Job logic in this software type Not safe for grid node, Just for testing purpose  Here I ’ d like to use the Blast software

8 Step1.2: Submit a grid job

9

10 Step1.3: Query Global Job Records  Query all the jobs submitted by yourself –No matter they are on which grid node

11 Step1.4: Query job details –Right-click a job record and press “ View ” –Input passwd for the mapped linux account

12 Step1.5: Get job output  Get the standard out stream of indicated job (even when it ’ s not finished yet)

13 Step1.7: Manage Job  To terminate the indicated job  To re-run the indicated job –Generated job will share the same home dir with the original job, with data shared between these 2 job.

14 Step1.8: Accounting facilities –Click the “ AccountInfo ” button on the left StatisticInfo: the job statistics of this node for this Grid user Accounting details: List the local job accounting information

15 Step1.9: File facilities  Access your files on the cluster via portal

16 Part 2: Admin-level functions via portal  The admin-level functions could only be operated by the Administrator of Grid-Node.  So I will show the whole processing of using Admin-level functions via portal.

17 Step2.1: Manage Cluster Info.  Add/Manage Cluster information –The jobs are finally be passed to local cluster  Add/Manage Queue on this cluster –The jobs will be waiting in some queue of this cluster –Different queues may have different restrictions on them.

18 Step2.2: Manage Software Info.  Add/Manage SoftwareType: –A SoftwareType is identical within a grid –Same type of applications provided by different Grid nodes could be grouped into one SoftwareType –Define the common logic of the same type of jobs.  Add/Manage Software instance for this Grid Node.

19 Step2.3: Manage User Mapping  UserMapping: Grid User  Linux Account –Grid User : identical in multiple Grid Nodes. –Linux account : on local Cluster system.

20 Any Questions ?