Skip to content

DIRAC Requests For Comments (RFC)

fstagni edited this page Sep 8, 2015 · 29 revisions

The DIRAC RFCs are descriptions of proposals for new functionalities which are exposed by the authors to the DIRAC development team for comments. The RFC description is maintained and updated in the corresponding DIRAC Wiki page. Each new RFC must have a distinct number by which it can be referred to, the author and the date of the first submission. Each RFC is announced in the DIRAC developer forum inviting the developers to send their comments. It is the responsibility of the author to incorporate the results of the discussion into the RFC. As soon as the RFC is getting a consensus agreement of the developers, it becomes a development task.

The current RFCs:

RFC #1: System wide message about DIRAC outage

RFC #2: Replication Service

RFC #3: Proxy creation and upload via a browser

RFC #4: "Path to executable not found" as the minor status

RFC #5: Resources CS section structure

RFC #6: Refactoring Request Management System

RFC #7: Applying JobRequirements during TaskQueue filling

RFC #8: Review of dirac command line tools

RFC #9: Description and usage of Site to Resource mappings

RFC #10: Asynchronous File Catalog operations

RFC #11: Deleting files in an ancestor/daughter relationship

RFC #12: Schedule jobs to SE

RFC #13: Gathering some reusable functions in a utilities package

RFC #14: Number of streams in putFile method of SRM2Storage

RFC #15: Fast job splitting

RFC #16: Extended Job Manifest with Execution logic

RFC #17: Refactoring of the ReplicaManager

RFC #18: Generic, configurable, pilots

RFC #19: DFC requirements

RFC #20: Error system

RFC #21: Transformation System evolution

RFC #22: On the use of messaging services (i.e. RabbitMQ)

Clone this wiki locally