Difference between revisions of "UKI-SOUTHGRID-CAM-HEP"

From GridPP Wiki
Jump to: navigation, search
 
(No difference)

Latest revision as of 14:25, 25 July 2012

UKI-SOUTHGRID-CAM-HEP

Topic: HEPSPEC06


UKI-SOUTHGRID-CAM-HEP
OS+cores,Bits OS Kernel 32/64 mem gcc Total Per Core
Dual Xeon E5420 2.50GHz SL4.6 2.6.9-78.0.1.ELsmp 64 16GB 3.4.6 59.95 7.5
Dual Xeon 2.80GHz SL4.5 2.6.9-78.0.1.ELsmp 64 2GB 3.4.6 9.33 4.66
Dual Xeon 5150 2.66GHz SL4.5 2.6.9-78.0.1.ELsmp 64 8GB 3.4.6 34.86 8.72



UKI-SOUTHGRID-CAM new results July 2012. Dark Green indicates CPUs in use
Processor+cores OS Kernel Kernel 32/64 compiler 32/64 mem gcc Effective #cores Total Per Core Notes
Dual 2-core Xeon 5150 2.66GHz SL5.7 2.6.18-308.8.2 64 32 8GB 4.1.2 4 39.4 9.85 HT off
Dual 4-core Xeon E5420 2.5GHz SL5.7 2.6.18-308.8.2 64 32 16GB 4.1.2 8 69.7 8.71 HT off
Dual 4-core Xeon L5520 2.25GHz SL5.7 2.6.18-308.8.2 64 32 16GB 4.1.2 8 87.9 10.99 HT off
Dual 4-core Xeon L5520 2.25GHz SL5.7 2.6.18-308.8.2 64 32 16GB 4.1.2 16 110.7 6.92 HT on
Dual 4-core Xeon E5540 2.5GHz SL5.7 2.6.18-308.8.2 64 32 16GB 4.1.2 8 102.9 12.86 HT off
Dual 4-core Xeon E5540 2.5GHz SL5.7 2.6.18-308.8.2 64 32 16GB 4.1.2 16 126.3 7.89 HT on
Dual 4-core Xeon E5620 2.4GHz SL5.7 2.6.18-308.8.2 64 32 24GB 4.1.2 8 HT off
Dual 4-core Xeon E5620 2.4GHz SL5.7 2.6.18-308.8.2 64 32 24GB 4.1.2 16 HT on
Dual 6-core Xeon X5650 2.66GHz SL5.7 2.6.18-308.8.2 64 32 32GB 4.1.2 12 164.1 13.68 HT off
Dual 6-core Xeon X5650 2.66GHz SL5.7 2.6.18-308.8.2 64 32 32GB 4.1.2 24 195.4 8.14 HT on


Topic: Middleware_transition

All nodes running SL5, exceptfollowing nodes:

  • lcgCE 3.1 (condor)
  • SE (DPM)


running SL4
Upgrading

SE under progress. the lcgCE would stay longer I imagine.

gLite3.2/EMI


ARGUS/glexec

Not yet installed


BDII_site

gLite 3.2


CE (CREAM/LCG)

1 LCG CE (condor)
1 CREAM CE (torque)


SE

The SE itself running DPM v1.7.4 (SL4)
All the disk servers running v1.8 (SL5)


UI

gLite 3.2


WMS

N/A


WN

gLite 3.2


Comments


Topic: Protected_Site_networking


  • Gigabit backbone with 1Gbps connection onto the University network shared with Group Systems
  • Two HP HP E2910-48G al Switches.
  • All the WNs are on the gigabit-network
  • Dual 10Gbps University connections on to JANET
  • GRID systems on same public subnet (/24) as Group Systems.
  • Gradual rearrangement of Group IP addresses to put Group and GRID systems in separate halves of this subnet – nearly completed (2 critical servers left to move).
  • Monitoring – use MRTG for traffic history.


Topic: Resiliency_and_Disaster_Planning



      • This section intentionally left blank


Topic: SL4_Survey_August_2011

We have following nodes running SL4

  • lcgCE 3.1 (condor)
  • SE (DPM)
  • 7 x disk-servers


Upgrading SE and the disk-serves currently under progress. the lcgCE would stay longer I imagine.

Topic: Site_information


Memory

1. Real physical memory per job slot:

  • 2GB - 152 job slots
  • 1GB - 20 job slots




2. Real memory limit beyond which a job is killed:

  • None




3. Virtual memory limit beyond which a job is killed:





4. Number of cores per WN:

  • 2 cores - 10 WNs
  • 4 cores - 32 WNs
  • 8 cores - 03 WNs




Comments:

Network

1. WAN problems experienced in the last year:

  • None (apart from unscheduled departmental network disruption).




2. Problems/issues seen with site networking:

3. Forward look:

Comments:

Topic: Site_status_and_plans



SL5 WNs

Current status (22/03/2011): SL5 on all WNs

Comments:

SRM

Current status (19/11/2009): Presently at 1.6.11 ob gLite 3.1 (glite-SE_dpm_mysql-3.1.10-0.x86_64)

Planned upgrade: Already tried several times but error returned reporting:

Error: Missing Dependency: libapr-0.so.0()(64bit) is needed by package apr-util
Error: Missing Dependency: libapr-0.so.0()(64bit) is needed by package httpd


Comments: There is already a opened ticket for that: #52552

SCAS/glexec

Current status (19/11/2009): Reviewing the compatibility issue with Condor at site.

Planned deployment:

Comments:

CREAM CE

Current status (22/03/2011): CREAM CE with PBS deployed, not functional yet.

Planned deployment:

Comments: