 |
 |
Hi Linda, > Re: "the deadlines only apply to software which is currently out of security > support. They do not apply to the gLite 3.2 WN" and "a request has been > made to extend security support for UI and WN." Batch system software (i.e. torque etc) pulled from the GLITE 3.2 repositories does not use munge (an identity checking program). i.e. GLITE 3.2 CREAM, TORQUE_SERVER and WNs do not use munge. But batch system software (i.e. torque etc) pulled from elsewhere (e.g. EMI/UMD/EPEL) does use munge. Thus EMI/UMD/EPEL CREAM, TORQUE and WNs all must have munge. This means that any site that uses a consistent set of repositories (i.e. all GLITE or all EMI/UMD/EPEL) must use a consistent set of CE, TORQUE and WN software. So just extending the deadline for WN 3.2, as you propose, may not be sufficient for sites that use a consistent set of repositories. It would also be necessary to relax the deadlines on TORQUE_SERVER and TORQUE_UTILS and (arguably?) CREAMCE. I say "arguably" because it may be possible to mix and match EMI/UMD/EPEL repositories with GLITE repositories to overcome this obstacle, but that sort of cherry-picking is way too expensive in terms of risk and effort. So we must have a fully working, consistent set of EMI/UMD/EPEL batch, cream and worker node software, and we need it all to be released in a consistent way before any deadline. Is anybody else in this position? Steve -- Steve Jones [log in to unmask] System Administrator office: 220 High Energy Physics Division tel (int): 42334 Oliver Lodge Laboratory tel (ext): +44 (0)151 794 2334 University of Liverpool http://www.liv.ac.uk/physics/hep/