Dirac v6r10

The are 3 main features introduced within this release:

1. The full use of the new version of the Request Management System, introduced first within release v6r9, together with the Data Management system.
2. Many changes are applied in the TransformationSystem, and particularly in the TransformationDB.
3. A new "package", named Workflow, has been introduced. This package makes it easier, for VOs, to define Job Workflows, introducing generic modules implementations that can be extended by the VOs.

Those new features that need special care when upgrading from previous versions to v6r10 are outlined below.

New RMS everywhere

Using the new RMS system everywhere means using it for all the replication activities, that were using the old RMS system up to version v6r9. The old system, populating the old set of tables, will not be feed any more. System administrators might want to check that all the requests are treated within the old system before stopping the corresponding agents. If you are upgrading from DIRAC v6r9, no new agents nor services need to be started.

FTSDB

A new DB, and a new set of tables will be created at the start of the FTSManagerService. This DB, together with the new implementation of the service and clients, will substitute the old system.

TransformationDB

The tables definition is switching from MyISAM to InnoDB, and few triggers are being introduced. Applying this change needs special care. It has to be noted that, for this release, both the tables definition, and the triggers, are defined in the TransformationDB.sql file, and that system administrators are required to manually intervene at the database level to apply them. The changes to apply follow: << insert here >>

In any case, it is not strictly necessary to apply such changes: tables defined within MyISAM will keep working.

Workflow

The new workflow package provides four generic modules. Detailed instructions on how to use it and extend it can be found in the DIRAC.Workflow.Modules.ModuleBase module.