| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | This page outlines the procedures and responsibilities for the person currently acting as 'IPP Processing Czar'. In a nutshell, these include: |
| | 4 | |
| | 5 | * monitoring the various pantasks servers running on the production cluster |
| | 6 | * alerting the IPP group to any notable errors or failures |
| | 7 | * keeping an eye on production cluster load using 'gagglia' |
| | 8 | * adding and removing labels based on the current set of processing priorities, outlined here |
| | 9 | |
| | 10 | |
| | 11 | = Setup = |
| | 12 | |
| | 13 | You will need to have ipp user access on the production cluster. For convenience, have someone with access (anyone on the IPP team) add your ssh public key to ~ipp/.ssh/authorized_keys. |
| | 14 | |
| | 15 | |
| | 16 | = Rebuilding the IPP code = |
| | 17 | |
| | 18 | The IPP in use presently is in |
| | 19 | |
| | 20 | |
| | 21 | {{{ |
| | 22 | ~ipp/ipp-20100211 |
| | 23 | }}} |
| | 24 | |
| | 25 | If the code needs an update and rebuild, then: |
| | 26 | |
| | 27 | * stop pantasks (as above) |
| | 28 | * {{{cd ~ipp/ipp-20100211}}} |
| | 29 | * {{{svn update}}} |
| | 30 | * {{{psbuild -optimize}}} |
| | 31 | |