Support #859
GRID Installation
100%
Description
Files
Updated by Rogers, Chris over 11 years ago
Following phone discussion
There is a problem with installation of the dependencies particularly some of the devel libraries on GRID nodes. Propose to build on local machine and then move across to the GRID. This is possibly okay, except there is a problem with python relocation #819 that needs to be resolved.
Updated by Rogers, Chris over 11 years ago
I found several problems, but fixed the one that would stop the tests from passing on the new installation. So now, to relocate the code, you just have to rerun the configure script
./configure
Note that the relocated code will not build, but should still be executable. Let me know if there is a problem. The code is pushed to the unstable branch - I attach a tarball. I will make a release on Tuesday or Wednesday with the update in.
Updated by Rogers, Chris over 11 years ago
- Category set to bin(aries)
Following phone discussion today:
- Plan is to call GRID server from the data mover DAQ machine on MICEnet
- Rogers to write a script that takes filename as input, runs reconstruction, submits the job, writes an output tar ball including any stdout, etc.
- Janusz to handle data movement, GRID API
- look for data file moved to GRID node
- submit job, restricted to Imperial GRID node (so we don't have to worry so hard about job tracking)
- recover data file, push to CASTOR
- Janusz to contact Henry, check he's okay with that, ask about file structure on CASTOR
Updated by Rogers, Chris almost 11 years ago
- Status changed from Open to Closed
- Assignee changed from Martyniak, Janusz to Rogers, Chris
- % Done changed from 0 to 100
This was done ages ago