1. Klaster obliczeniowy WLCG – cz.I Alice::WTU::LCG - skład: VOBOX  alicluster.if.pw.edu.plVM: saturn.if.pw.edu.pl CREAM-CE  aligrid.if.pw.edu.pl VM: saturn.if.pw.edu.pl SE  alix.if.pw.edu.plca 12 TB disk RAID6 DBII  bdii.if.pw.edu.pl VM: saturn.if.pw.edu.pl TORQUE  torque.if.pw.edu.pl VM: saturn.if.pw.edu.pl 16x WN  node10[57-72].grid4cern.if.pw.edu.pl IntelQ6600 8GBRAM 13x WN  node10[81-99].grid4cern.if.pw.edu.pl AMD-Athlon 2C 4GBRAM NFS,WEB,NTP,NAT server  neo1.if.pw.edu.pl ca 2 TB disk RAID5 SLC5 – 64bit, gLite 3.2 (ca 10.000 rpms SLC+ 1.000 gLite) 3x APC UPS, 3x GB-eth switch saturn.if.pw.edu.pl - HP DL385 4x Opteron 2.4GHz 4GB RAM + VMWare Infrastructure3

15. LCG Information System Levels Resource level: Grid Resource Information Server (GRIS) One GRIS on top of each CE, SE, RB, MyProxy (no WNs). –Sensors and scripts get status of concrete resources statically (e.g. GlueCEUniqueID) or dynamically (e.g. GlueCEStateWaitingJobs) Site level: Grid Index Information Server (GIIS) –Compiles all the information of the different GRISs in a site. –LCG-2 recommends using a BDII instead of a GIIS Improves robustness and stability. Called the site BDII. Top level: Berkeley DB Information Index (BDII) –Keeps all Grid information about the VOs (generally only one). –Stores information from local BDIIs or GIISs in its database. –Only queries sites that are included in a configuration file.

16. Each site can run a BDII. It collects the information coming from the BDIIs/GIISs At each site, a site GIIS collects the information given by the GRISs Local GRISs run on CE, SE, RB, MyProxy at each site and report dynamic and static information Abbreviations: BDII: Berkeley DataBase Information Index GIIS: Grid Index Information Server GRIS: Grid Resource Information Server LCG Information System Hierarchy From LCG2.3.0 site GIIS has been replaced by “site” BDII

17. LCG Information System Hierarchy RB Local GRIS SE Local GRIS CE Local GRIS BDII-A BDII-B SE Local GRIS SE Local GRIS CE Local GRIS SE Local GRIS BDII-C Site 1 Site 2 Site 3 Site BDII

24. Old AliEn Framework 100% perl5 SOAP Local Site elements Central services User

25. AliEn ‘Pull’ Protocol One of the major differences between ALiEn and LCG grids is that AliEn uses the ‘pull’ rather than ‘push’ protcol. EDG/Globus model: ALiEn model: userserver Resource Broker userserver Resource Broker job list

26. Resource Broker “Pull” instead of traditional “Push” architecture Broker Authen Logger TransferBroker IS TransferOptimiser EDG/Globus

29. http://www.if.pw.edu.pl/~alix/