Dirac v6r7

The man new feature in the release is starting to use the Resource Status System for providing status information for the Storage Elements as a starting point. There are other modifications as well. Those new features that need special care when upgrading from previous versions to v6r7 are outlined below.

Resource Status System

In this release the RSS functionality is partially available. To start using the RSS it should be installed and configured following instructions that you can find here .

In order to activate the use of the ResourceStatus system to provide SE status information the following option must be defined in CS in the /Operations section using standard root Operations path:

/<Operations>/ResourceStatus/Config/State = Active

Once this is done, the usual SE status setting and lookup scripts will start using the ResourceStatusDB as a source of status information.

Transformation System

Several modifications were made to the Transformation System. Instructions how to update installations using it can be found here.

Selection of VO Catalog services

There is now a possibility to select the File Catalog services to be used based on Setup and VO using /Operations configuration section with a usual rules for Operations parameters resolution. The catalogs present in the following section will be available for users <Operations>/Services/FileCatalogs. For example:

Operations
{
   lhcb
   {
      Production
      {
         Services
         {
            FileCatalogs
            {
               DIRACFileCatalog
               {
                  Status = Active
                  AccessType = Read-Write
                  Master = True
               }
               LcgFileCatalog
               {
                  Status = Active
                  AccessType = Write
                  UseProxy = True
               }
            }
            StorageElements
            {
               CERN-USER
               {
                  UseProxy = True
               }
            }
         }
      }
   }
}

where DIRACFileCatalog and LcgFileCatalog access details are specified as usual in the /Resources section.

FileCatalogProxy service

Note the UseProxy option in the example above for LcgFileCatalog. This way one can specify that the catalog should be accessed via a FileCatalogProxy introduced in this release. This allows to access any file catalog, including LFC, using DIRAC specific client/service protocol. It means that the catalog can be accessed without installation of a specific client UI, e.g. gLite UI for the LFC allowing to access these service even on the platforms on which native clients do not exist. To help users specify the same flag in the individual local condiguration the following option can be used, for example:

/LocalSite/Catalogs/LcfFileCatalog/UseProxy = True

StorageElementProxy service

Similarly to the Catalogs a proxy service exists for the StorageElements. The use of the proxy service can be triggered by the /Operations option as in the example above. In the local configuration, this can be also specified as:

/LocalSite/StorageElements/CERN-USER/UseProxy = True

Other changes

/DIRAC/VOPolicy/OutputDataModule option moved to <Operations>/Transformations/OutputDataModule to allow per VO specification of this setting.