-
Notifications
You must be signed in to change notification settings - Fork 176
DIRAC v6r6
The DIRAC v6r6 release has many new minor features and a large number of bug fixes.
The FileCatalog has got the storage usage subsystem which allows to generate instantly storage usage reports. This needs special database tables to be filled before usage. In case of upgrade of an already existing installation, the tables must be filled ( one time command ) with the following command in the FileCatalog console::
> rebuild storage
Rebuilding can take more than an hour for a DB with about 10M entries.
Among other new features can be mentioned command and path completion using Tab key. It is now possible to define which catalog service to be used by members of a given VO by specifying options in the /Operations/<VO>/Services/FileCatalogs section.
Added possibility to connect sites with Condor batch system. ComputingElement specific implementations are better protected against command failures. The new SSHBatchComputingElement allows to group together multiple PCs accessible through SSH as a single site. A possibility to kill pilots was added to all kinds of ComputingElements.
Estimation of the time left in the slot is now based on the DIRAC CPU normalization if available and the CPU time already spent on the site is sufficient to provide a precise enough measurement of the consumed slot part.
There is a better support of multi-VO installations: Multiple user groups per VO are now supported with generic pilot jobs service the whole VO.
Accounting of finished jobs was updated to distinguish jobs in Failed and Rescheduled final status.
The RequestManagement system was considerably reworked to increase the reliability of request state machine. A new service RequestProxy is now supposed to be installed at the request relay hosts. It replaces the old RequestManager services with the File based RequestDB and the Zuzia agent for forwarding requests to the central services.
The TransformationAgent is made multithreaded to speed up transformation treatment
/DIRAC/VOPolicy/OutputDataModule option moved to <Operations>/Transformations/OutputDataModule to allow per VO specification of this setting.