Component development leads
The component lead is responsible for the planning and development of patches and features for the respective component. This does not mean that the component lead is the only person developing the component, but he/she should direct the efforts and be the point of contact in case of problems.
Rucio Project Leader: Martin Barisits
| Component | Lead (+Deputies) | Description |
|---|---|---|
| Authentication & Authorisation | Dimitrios Christidis, Mario Lassnig | Client-server authentication, Rucio tokens, auth methods (kerberos, ssh, userpass, OIDC, ...) |
| Clients | Maggie Voetberg, Mario Lassnig | General Python Clients and Command Line interface related development, rucio download, rucio upload; Specific component related client functionality is part of the other components |
| Consistency checks | Fabio Luchetti, Guilherme Lima | Dark data detection daemon: Auditor |
| Core & Internals | Martin Barisits, Mario Lassnig | Core functionality not specifically part of other components |
| Database | Dimitrios Xenakis, Mario Lassnig, Martin Barisits | Database (Compatibility and optimisation) and SQLAlchemy framework specific issues |
| Dataset deletion | Alexander Richards, Martin Barisits | Dataset deletion daemon: Undertaker |
| Deletion | Hugo Gonzalez Labrador, Cedric Serfon | File deletion daemon: Reaper |
| DIRAC | Cedric Serfon | Rucio integration with Dirac |
| Docker & Kubernetes | Riccardo Di Maio, Mario Lassnig, Eric Vaandering, Hugo Gonzalez Labrador | Docker & Kubernetes deployment |
| Documentation | Martin Barisits, Maggie Voetberg | General documentation |
| Jupyterlab extension | Francesc Torradeflot, Enrique Garcia Garcia | Rucio Jupyterlab extension |
| Life time model | Dimitrios Christidis | Life time model processing and exceptions |
| Messaging | Alexander Richards, Mario Lassnig | Messaging daemon: Hermes, Creation of eMails and ActiveMQ messages |
| Metadata | Rob Barnsley, Dimitrios Xenakis | Metadata workflows |
| Monitoring & Traces | Mayank Sharma, Mario Lassnig | All things internal monitoring and traces |
| Multi VO | Tim Noble | Issues and developments related to Rucio Multi VO mode |
| Policies | James Perry | All things related to separate settings/config/policies into community specific things |
| Probes & Alarms | Dimitrios Christidis, Eric Vaandering | Probes and alarms for Nagios |
| Protocols | Maggie Voetberg, Mario Lassnig | Protocols (Upload, Download, Deletion) |
| Rebalancing | Cedric Serfon | Data rebalancing daemon: BB8 |
| Recovery | Cedric Serfon | Data recovery daemon: Necromancer and suspicious replica recovery |
| Release management | Martin Barisits, Dimitrios Christidis | Packaging of new versions, package configuration |
| Replicas | Riccardo Di Maio, Alexander Richards | Replicas related workflows (list_replicas, add_replica, ...) |
| REST & API | Maggie Voetberg, Martin Barisits | Web-Framework (Web.py & Flask) |
| Rules | Riccardo Di Maio, Martin Barisits | Replication rules and rule daemons: Judge |
| Subscriptions | Cedric Serfon | Subscription daemon: Transmogrifier |
| Testing | Mayank Sharma, Riccardo Di Maio | Regression and Unit tests, automatic tests of submissions |
| Transfers | Riccardo Di Maio, Hugo Gonzalez Labrador | Transfer daemons: conveyor and functional transfer tests |
| WebUI | Mayank Sharma, Eraldo Silva Junior | Web user interface: Rucio Web UI |