Introduction

This page is intended for VDT/VOMS client side sys-admin and users for running jobs on compute element.

Add VOMSes entry

  • The VDT page explains vomses string format, but here it is again for reference:
    "pacific" "voms2.lab.ac.uab.edu" "15000" "/O=Grid/OU=GlobusTest/OU=simpleCA-voms1.lab.ac.uab.edu/CN=http/voms2.lab.ac.uab.edu" "pacific"
    
    • Local VOMS name – an arbitrary local label for the VO
    • Server host name
    • Server port (on which this VO's service is running)
    • Server Distinguished Name (DN)
    • VOMS name on the server (should it be VO name?)
    • [Optional] The server's Globus version (digits only)
  • Add VOMSes entry to the VOMSes file. Non-root users may add ~/.edg/vomses file and root/sys-admin may add edit vomses file in etc directory. The VDT install will have two vomses files: 'glite/etc/vomses' and 'voms/etc/vomses'. The $VOMS_USERCONF variable will point to the vomses file used by the VDT install.
    echo $VOMS_USERCONF
    

Request VOMS proxy

  • Get VOMS-proxy without VOMS information - essentially a grid-proxy
    voms-proxy-init
    

  • Get VOMS-proxy with VO information
    # voms-proxy-init --voms <vo-name> 
    voms-proxy-init --voms pacific
    

  • Get VOMS-proxy with VO information + Group information
    # voms-proxy-init --voms <vo-name>:/<vo-name>/<sub-group-name>
    voms-proxy-init --voms pacific:/pacific/japan
    
  • Get VOMS-proxy with VO information + Role information
    # voms-proxy-init --voms <vo-name>:/<vo-name>/Role=<role-name>
    voms-proxy-init --voms pacific:/pacific/Role=moderator 
    
  • Get VOMS-proxy with VO information + Group information + Role information
    # voms-proxy-init --voms <vo-name>:/<vo-name>/<sub-group-name>/Role=<role-name>
    voms-proxy-init --voms pacific:/pacific/japan/Role=moderator 
    

Globus commands

globus-job-run 

References