, view all tags

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


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.

Topic attachments
I Attachment Action Size Date Who Comment
Unknown file formatjdl wms_4039.jdl manage 0.4 K 2012-10-08 - 07:59 CristinaAiftimiei JDL to test #4039
Edit | Attach | PDF | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r2 - 2012-10-08 - CristinaAiftimiei
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback