Technical-SAM

SAM = Service Availability Monitoring

Suggestions for SAM sensors for ARC based on finding equivalents to the original LCG/gLite sensors:

SE sensors

• SE-lcg-cr: Copy and register a file to the SE (uses lcg-cr)
  • ARC equivalent: Copy a file to the SE using ngcp

• SE-lcg-cp: Copy a file back from the SE (uses lcg-cp)
  • ARC equivalent: Copy a file from the SE using ngcp

• SE-lcg-del: Delete a file from the SE (uses lcg-del)
  • ARC equivalent: Delete a file from the SE using ngrm

SRM sensors

• SRM-put: Store file to SRM (put) using lcg-cr
  • ARC equivalent: Store file to SRM (put) using ngcp

• SRM-get: Copy a file back from the SRM (get) using lcg-cp
  • ARC equivalent: Copy a file back from the SRM (get) using ngcp

• SRM-advisory-delete: Delete a file from the SRM (advisory-delete) using lcg-del
  • ARC equivalent: Delete a file from the SRM (advisory-delete) using ngrm

testjob/glite-testjob sensors

• CE-sft-wn: WN hostname
  • ARC equivalent: WN hostname

• CE-sft-softver: Software Version
  • ARC equivalent: ARC version

• CE-sft-caver: CA certs version
  • ARC equivalent: CA certs version (tricky to find out remotely)

• CE-sft-brokerinfo: Get the CE hostname using edg-brokerinfo/glite-brokerinfo
  • ARC equivalent: none (very middleware specific)

• CE-sft-csh: Simple csh test
  • ARC equivalent: This one work for ARC too

• CE-sft-lcg-rm: Tests data management on the WN
  • ARC equivalent: testjobs with inputfiles and outputfiles

• CE-sft-vo-tag: VO Tag management
  • ARC equivalent: none

• CE-sft-vo-swdir: VO software directory
  • ARC equivalent: Maybe check for VO specific RTEs?

• CE-sft-rgma: Test R-GMA client software configuration
  • ARC equivalent: none

• CE-sft-rgma-sc: R-GMA Secure Connector
  • ARC equivalent: none

CE/gCE sensors

• CE-sft-job/gCE-sft-job: Tests jobsubmission
  • ARC equivalent: Test jobsubmission using ngsub

• CE-sft-apel/gCE-sft-apel: Checks some R-GMA based accounting
  • ARC equivalent: none

LFC sensors

ARC should probably have RLS sensors instead...

• LFC-ls: Check we can do a lfc-ls
  • ARC equivalent: RLS query

• LFC-writefile: Check we can create a file in the LFC for this VO
  • ARC equivalent: RLS registration

WN sensors

• WN-jobstart: publish job info on startup
  • ARC equivalent: Except for the R-GMA part this should work for ARC too

• WN-ver: WN middleware version
  • ARC equivalent: none (no middleware on WNs)

• WN-swdir: WN VO software area
  • ARC equivalent: Maybe check for VO specific RTEs?

• WN-is: WN information system
  • ARC equivalent: none (no middleware on WNs)

• WN-se-ping: WN pings the close SE
  • ARC equivalent: none (no middleware on WNs)

• WN-home: WN home test
  • ARC equivalent: Session directory test

• WN-caver: CA certs version on the WN
  • ARC equivalent: none (no middleware on WNs)

• WN-perl: Perl version on WN
  • Should work for ARC too

• WN-python: Python version on WN
  • Should work for ARC too

• WN-java: Java version on WN
  • Should work for ARC too (possibly by specifying a java RTE)

• WN-jobend: publish job info in the end
  • ARC equivalent: Except for the R-GMA part this should work for ARC too

FTS sensors

Since we use the same FTS as glite the FTS sensors should work...