Certifying WMS HOWTOS

Checks before starting

• hardware requirements for WMS & L&B
• disable yum-autoupdate
• disable puppet (if "allowed")
• check eventual important notes for WMS and L&B, and UI

EMI UI

The EMI UI for the certification can be installed following the instructions reported here.
A further configuration is required in order to match the resources tagged with other.GlueCEStateStatus == "Testing":

In /etc/glite-wms/dteam/glite_wmsui.conf and /etc/glite-wms/dteam/glite_wms.conf comment out the following line:

//    requirements  =  other.GlueCEStateStatus == "Production";

Advisory #4039

Submitting this JDL (wms_4039.jdl) will cause arbitrary code to be run as 'glite' user on the WMS, when time to renew the user proxy. It must select only CREAM CEs, so as to trigger the ICE's (WMS component that submits to CREAM) proxy renewal mechanism.

Using a short proxy results in an almost immediate execution.

Standard conformance tests (always)

# yum install glue-validator
# glue-validator -t glue1 -h cert-XX.cnaf.infn.it -p 2170 -b o=grid
# glue-validator -t glue2 -h cert-XX.cnaf.infn.it -p 2170 -b o=glue