middleware:Glite
From Dgiref
| |||
 The gLite middleware itself is a complex system with interconnected parts, interacting over the network. This includes as the middleware to store a data (dCache Storage Element (SE)) as cluster resources (Worker Nodes, Local Resource Management System, NFS server). Every gLite instance has Computing Element as a frontend for job submission. All connections need to pass a generic interface to the cluster (Grid Gate). Information Service (IS) or "site BDII" provides information about the Grid resources and their status which can be used for monitoring and accounting. Current D-Grid gLite implementation uses Globus Monitoring & Discovery Service (MDS) for resource discovery and to publish the resource status. |
| ||
|
Note from ticket 614: WARNING: It is possible that user files found in the user accounts home folders get deleted by a gLite cleanup cronjob if the Sites used gLite together with some other middleware (Globus, Unicore or both). The problematic cronjob is:/etc/cron.d/cleanup-grid-accounts D-Grid uses shared instead of poolaccount accounts with fixed user mappings, hence the problematic cronjob should be disabled. This cronjob creates logfiles: /var/log/cleanup-grid-accounts.log* /opt/lcg/etc/cleanup-grid-accounts.conf The recommended solution is to completely disable that cronjob in the gLite CE. Please be aware that:
| |||
