BEgrid gLiteWMS gLiteLB

From Begrid Wiki
Revision as of 09:11, 9 June 2021 by Maintenance script (talk | contribs) (Created page with " == BEgrid gLite-WMS admin notes == === 1. WMS configuration : === glite_wms.conf file === 2. User Authentication and Mapping === User Authentication is performed by t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

BEgrid gLite-WMS admin notes

1. WMS configuration :

glite_wms.conf file

2. User Authentication and Mapping

User Authentication is performed by the WMSProxy component based on a GACL module. glite_wms_wmproxy.gacl is the authorization file which contains the DNs or FQANs that are authorized to make use of the WMProxy service.

File location: /opt/glite/etc/glite_wms_wmproxy.gacl


For example to authorize a single user identified by the following DN: (even if he does not belong to the VOs allowed to use the WMS) /C=BE/O=BEGRID/OU=IIHE/OU=ULB-VUB/CN=Antal Bulanza

<gacl>
  <entry>
    <user>
      <dn>/C=BE/O=BEGRID/OU=IIHE/OU=ULB-VUB/CN=Antal Bulanza</dn>
    </user>
    <allow>
      <exec/>
    </allow>
  </entry>
</gacl>

To authorize the users of some VOs

<entry>
    <voms>
      <fqan>/betest</fqan>
    </voms>
    <allow>
      <exec/>
    </allow>
  </entry>
<entry>
    <voms>
      <fqan>/dteam</fqan>
    </voms>
    <allow>
      <exec/>
    </allow>
  </entry>

To forbid the access to the users of some VOs

<entry>
    <voms>
      <fqan>/beapps</fqan>
    </voms>
    <deny>
      <exec/>
    </deny>
  </entry>

3. Log files

All the log files are located in /var/log/glite directory

  • glite-wms-wmproxy-purge-proxycache.log
  • lcmaps.log:
  To check the mapping of remote users to local pool accounts 
  • glite-wms-wmproxy-purge-proxycache-date_of_the_day.log
  • httpd-wmproxy-access.log
  • httpd-wmproxy-errors.log:
  reports the problems while contacting the WMProxy service
  • lcmaps.log

In the /var/log/glite/wms directory

  • jobcontroller_events.log:
  Used to check the jobs events once arrived on condor
  • logmonitor_events.log:
  Here every job information coming from various log files is aggregated
  • wmproxy_events.log
  • workload_manager_events.log:
  To check the status of the matchmaking process (Waiting, Ready, Done,... status) and  
  query the information system to fill in the Information Supermarket

4. Garbage collection

  • Sandbox Directories
  • Condor Sandbox Directories
  • Log files


Back to Servers


Template:TracNotice