The new version of the gLite Middleware (gLite 3.0) has been released  on the 4th of May.

To visit the official site, click here!

New Features:

(This is not a complete list of all new features, but it highlights the most important changes. It is taken from the gLite's official page)

• lcg-RB
  1. Condor is upgraded to 6.7.10 there is a new condor-lcg package which provides LCG modifications to the gahp_server and grid_monitor.
  2. Configuration of these is handled by YAIM.
      
• UI
  1. The gLite 3.0 UI is a 'combined' UI, incorporating LCG and gLite components.
      
• WN
  1. The gLite WN has combined gLite and LCG components
      
• DPM
  
  1. SRM V2.1.1 interface implemented. Available without srm-copy nor functional global space reservation.
  2. Changes in DPM from LCG2.7.0: Virutal IDs, VOMS, DPM replicate and drain utilities for admin Upgrade from LCG-2_7_0 is supported.
      
• LFC
  
  1. VOMS enabled. 
  2. LFC supports dirs and files permissions based on VOMS roles, groups, subgroups and user DN. No VOMS metadata associated to user DN is available. Custodial flag requested by CMS available as ftype (file type). No replica attributes since they are available from SE via getFileMetadata (SRM v1) or srmLs (SRM v2). DLI interface available in LFC v1.4.5. Possibility to set this flag is not implemented, not available on SE either.
  3. Improved read performance for experiment access patterns. It is possible to use DNS switch to balance servers load. Not possible to serve 100Hz requests per server if security is on. The performance measured is 150Hz requests served on a normal 2GHz PC. SSL sessions are not currently implemented. Bulk operations not available, but there is support for sessions (no failure prone) and transactions (failure prone).
      
• GFAL
  1. Posix file access via LFN available.
  2. Best replica selection based on site location only.
      
• dCache support
  1. The yaim script for configuring dCache has received many updates from GridPP. It offers extended functionality but is backward compatible.
     
• FTS
  
  1. Improved retry logic, option for VO specific setting and plugin to control retry policy.
  2. Improved monitoring.
  3. The FTS web-service can authorise using VOMS roles; DN; groups; subgroups.
  4. The FTS does not currently use the VOMS credentials when contacting the SRMs (it uses the plain credential retrieved from plain MyProxy).
  5. Reshuffling, cancellations possibles. VO managers can change order of jobs.
  6. Plugin retry policy is available. Catalog plugin mechanism is available and is being validated (currently by Atlas) to check that it meets their requirements. The deployment model for these VO-
     specific plugins is not clear yet. A VO can provide a pluging for catalogue operation. Currently based on Python script. The script is currently in a file and there is no mechanism to distribute it.
  7. FTS endpoint discovery using the BDII to match source and destination.srmcpy is now supported.Infoprovider to publish channel topology.Improved error handling. Full error messages are available to users and experiment frameworks using a polling pattern.Notification (i.e. messaging) to users or to experiment frameworks is not available.
      
• gLite WLM
  
  1. Compared to the LCG functionality.
  2. Support for DAG (compound jobs).
  3. Bulk jobs with shared input sandboxes
  4. Parametric Jobs
  5. VOMS proxy renewal
  6. Sandbox located on webs servers or SEs
  7. Shallow resubmission improving the reliability (only for single jobs)
  8. Web service interface ( WM Proxy) reducing the latency of the submission process.
  9. Support for MPI on non shared file system clusters.
  10. Information caching from potentially multiple sources ( Information supermarket)
  11. Real time access to selected job output
  12. APIs and command line tools for accessing logging and booking, enabling user monitoring and monitoring of non RB jobs.
       
• R-GMA
  
  1. Minor bug fixes only.