1. ALICE-PanDA Pilot Factorizations Kaushik De Nov. 7, 2014

2. Goal Factorize pilot services into three parts Distribute the load of various services between three different CPU engines – Worker Node (WN) is main engine – On HPC, login node is second engine Introduce VoBox as third engine Two possibilities are shown in next slides – the choice depends on which services are needed, and on some technical implementation issues

3. Possible Plan A VoBox DDM site services ALICE services PilotHPC (i.e. login) HPC scheduling SAGA submission Environment pre- processing Local file staging (lsm from vobox or shared /fs) Heartbeat and PanDAMon services PilotRunJob (i.e. WN) Local environment setup Execution

4. Possible Plan B VoBox PilotHPC Lsm from SE to local /fs SAGA submission Heartbeat ALICE services SAGA layer (i.e. login node) Local scheduling (needs some extensions, integration with HPC scheduling) PilotRunJob (i.e. WN) Environment setup Execution

5. Requirements on Pilot Both plans use the HPCPilot modular structure that is currently being used at Titan & NERSC Both plans should allow smooth transition to Event Service (will require some discussions)

6. New Developments Needed Plan A – Need DDM site services for ALICE (which can be developed by MegaPanDA team) Plan B – Need new capabilities in SAGA (which will require joint effort between BigPanDA and SAGA teams)