Use Cases for the Computing Element

Authors:

• Sergio Andreozzi (INFN)
• Balazs Kònya (Lund University)

Use Case 1

A site owns a cluster of 150 nodes managed by the LSF batch system. The LSF interface is abstracted by two Grid services (gLite CREAM and GT4 GRAM). Two shares are configured, one for VO ATLAS and the other one for VO CMS

• Computing Resource
  • LRMSType: LSF
  • Total: 150
  • Used: 50

• Computing Service 1
  • service endpoint 1
    • implementation name: gLite CREAM

• Computing Service 2
  • service endpoint 2
    • implementation name: GT4 GRAM

• Share 1
  • policy
    • max cpu time: 10000
    • max wall time: 100000
    • max run job: 100
  • state
  • run jobs: 30
    • wait jobs: 0
  • authorization
    • • VO: ATLAS

• Share 2
  • policy
    • max cpu time: 5000
    • max wall time: 50000
    • max run job: 50
  • state
    • run jobs: 50
    • wait jobs: 50
    • authorization
  • VO: CMS

• Execution Environment 1
  • Total: 50
  • Used: 20
  • CPUType: ATLHON
  • OSType: CentOS

• Execution Environment 2
  • Total: 100
  • Load: 30
  • XEON
  • CentOS

• Application Environment 1
  • name: CMS-suite-001
  • authorized to VO: CMS
  • association to both Execution Environment 1 and 2

• Application Environment 2
  • name: ATLAS-suite-001
  • authorized to VO: ATLAS
  • association to both Execution Environment 1 and 2

• Application Environment 3
  • name: root
  • authorized to ALL
  • association to both Execution Environment 1 and 2