Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "GGUS:LSF Utils FAQ"

From EGIWiki
Jump to navigation Jump to search
m (lsf)
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
'''LSF Utils'''
<!-- * decommission: https://its.cern.ch/jira/browse/GGUS-1595 -->
[[Category:FAQ Former support units (GGUS)]]
<!--
{{GGUS-FAQ
{{GGUS-FAQ
|Unit= gLite LSF Utils
|Unit= LSF Utils
|Interface= H
|Interface= H
|Updated= 2010-10-26
|Updated= 2013-02-14
|purpose=  The gLite LSF Utils Support Unit (SU) is a 3rd level SU, about integrating LSF with the rest of the grid m/w (glite, EMI).
|purpose=  The LSF Utils Support Unit (SU) is a 3rd level SU, about integrating LSF with the rest of the grid m/w (glite, EMI).
The supporters act on a best-effort basis, after GGUS ticket filtering by the TPM (1st level) and the DMSU (2nd level).
<span style="color:red">The supporters act on a best-effort basis</span>, after GGUS ticket filtering by the TPM (1st level) and the DMSU (2nd level).
It provides support for usage of LSF from the Grid.
It provides support for usage of LSF from the Grid.
The gLite LSF SU will not build and package new releases of LSF nor will it fix bugs in LSF.
The LSF SU will not build and package new releases of LSF nor will it fix bugs in LSF.
The LSF SU will not provide support for LSF: it will only address problems concerning the integration between LSF and the CREAM CE
|components=LSF Utils
|components=LSF Utils
|responsible= Grid experts with LSF expertise are behind the e-group lsf-grid-support (@cern) which receives GGUS ticket notification.
|responsible= Grid experts with LSF expertise are behind the e-group lsf-grid-support (@cern) and INFN-Padova which receive GGUS ticket notification.
The support team is located at CERN/IT/PES and the developer (member of the above e-group) is in Padova (INFN).
The support team is located at CERN/IT/PES and at INFN-Padova.
CERN/IT/PES is responsible for the lsf info provider, while INFN-Padova is in charge of yaim-lsf-utils and of the metapackage.
|assigned by=By assignment within GGUS from the DMSU.
|assigned by=By assignment within GGUS from the DMSU.
|solved by=Specifically for LSF, the team at CERN/IT/PES receive and evaluate all tickets for SU 'gLite LSF Utils'. Then:
|solved by=Specifically for LSF, the team at CERN/IT/PES receive and evaluate all tickets for SU 'gLite LSF Utils'. Then:
* they answer the tickets concerning info providers
* they answer the tickets concerning info providers
* they use the field "Assign ticket to specific person(s)" to signal the developer, this ticket is for him.
* they use the field "Assign ticket to specific person(s)" to signal the developer, this ticket is for him.
|documentation= https://twiki.cern.ch/twiki/bin/view/EGEE/BatchSystems
|documentation= Please refer to the CREAM CE documentation available at https://wiki.italiangrid.it/CREAM
|sortname=Glite lsf utils
|sortname=Lsf utils
|type of issue=Computing Services
}}
}}
<!-- put the following lines above the }}
|components= For which components do you provide support?
|assigned by= Who will assign tickets to UNIT?
|solved by= Are tickets typically solved in UNIT or reassigned elsewhere?
-->
-->

Latest revision as of 14:01, 26 April 2018

LSF Utils