11
Access to the training Infrastructure Emidio Giorgio Istituto Nazionale di Fisica Nucleare lunedì 6 luglio 2009

Session5 T Infr Access Emidio

Embed Size (px)

Citation preview

Page 1: Session5 T Infr Access Emidio

Access to the training Infrastructure

Emidio GiorgioIstituto Nazionale di Fisica Nucleare

lunedì 6 luglio 2009

Page 2: Session5 T Infr Access Emidio

Overview

• A shared t-infrastructure

• Training room

• Network

• Support infrastructure for different technologies

• access to User interface

• certificates

lunedì 6 luglio 2009

Page 3: Session5 T Infr Access Emidio

A shared training infrastructure• The school program offers a wide set of grid technologies

• extremely hard to set up a different testbed for each of them

• too much resources needed

• many technologies have common components

• too many access policies needed

• much more effective to reuse common components : MultiMiddleware approach

• Resources localization

• client machines installed locally

• server machines (resources) in remote

• technologies sharing common parts (gLite, Condor, globus, UNICORE, ARC) provided from GILDA testbed

lunedì 6 luglio 2009

Page 4: Session5 T Infr Access Emidio

4

Middleware co-existence in GILDA

lunedì 6 luglio 2009

Page 5: Session5 T Infr Access Emidio

4

Middleware co-existence in GILDA

Super UI

Condor UNICORE Globus gLite

lunedì 6 luglio 2009

Page 6: Session5 T Infr Access Emidio

4

Middleware co-existence in GILDA

Super UI

Condor UNICORE Globus gLite

Condor UNICORE Globus gLite

Super CE

lunedì 6 luglio 2009

Page 7: Session5 T Infr Access Emidio

4

Middleware co-existence in GILDA

Super UI

Condor UNICORE Globus gLite

Condor UNICORE Globus gLite

Super CE

lunedì 6 luglio 2009

Page 8: Session5 T Infr Access Emidio

4

Middleware co-existence in GILDA

Super UI

Condor UNICORE Globus gLite

Condor UNICORE Globus gLite

Super CE

Single Authorization

Framework

lunedì 6 luglio 2009

Page 9: Session5 T Infr Access Emidio

Training room and local network• The training room is equipped with 20 desktop machines, where

client software for some technologies have been installed on top of Ubuntu 9.04

• work in pairs

• Desktop machines (aka client machines) wired, with a public IP address

• issgc-client-XX.polytech.unice.fr, XX=[01,20]

• client machines don't share a common area, work always with the same machine

• login : user -- password : issgcuser

• you can use your own laptop

• SSID (hidden) is ETUD_POLYTECH (accessible also from lecture room)

• Installation of technologies client software on laptops is up to you

lunedì 6 luglio 2009

Page 10: Session5 T Infr Access Emidio

Support infrastructure for technologies

• Most of the practicals will use the UI machine, where you will login via ssh (either from client machines or your laptop)

• at registration time, an ID number (from 01 to 40) has been assigned to you

• ui machine is issgc-ui.polytech.unice.fr

• your login is issgc<ID>, password GridISS<ID>

• you can change the password if you wish, but don't forget it then

• At the beginning of each practical, the instructor will tell you whether you have to login on the UI or work from the client

grace:~ emidio$ ssh [email protected]@issgc-ui.polytech.unice.fr's password: GridISS59[issgc59@issgc-ui ~]$

lunedì 6 luglio 2009

Page 11: Session5 T Infr Access Emidio

Digital certificates• Most of technologies make use of digital certificates for user

authentication

• they have been provided under your area on issgc-ui, on the standard location of .globus

• certificates are protected by a password : ISSGC

• where needed, certificates have been authorized on technologies resources

• next session will show how to request a personal certificate, that you could eventually use for practicals

[issgc59@issgc-ui ~]$ ll .globustotal 24-rw-r--r-- 1 issgc59 issgc59 1773 Jun 17 11:01 ISSGC59.p12-rw------- 1 issgc59 issgc59 1074 Jun 17 11:01 usercert.pem-r-------- 1 issgc59 issgc59 963 Jun 17 11:01 userkey.pem[issgc59@issgc-ui ~]$

lunedì 6 luglio 2009