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 "Agenda-12-03-2012"

From EGIWiki
Jump to navigation Jump to search
Line 29: Line 29:
*Currently only few clusters have EMI WN deployed.  
*Currently only few clusters have EMI WN deployed.  
** The [http://glite.cern.ch/glite-WN/ end of security updates] for gLite 3.1 will require to upgrade glite3.1 worker nodes in the next months.
** The [http://glite.cern.ch/glite-WN/ end of security updates] for gLite 3.1 will require to upgrade glite3.1 worker nodes in the next months.
*In general changing the execution environment may cause problems with the users' code.
*In general, changing the execution environment may cause problems with the users' code.
** Changes in the client libraries installed in the WN
** Changes in the client libraries installed in the WN
** Example of problem with [https://ggus.eu/tech/ticket_show.php?ticket=78315 CMS code].
** Example of problem with [https://ggus.eu/tech/ticket_show.php?ticket=78315 CMS code].

Revision as of 11:36, 12 March 2012

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security



Detailed agenda: Grid Operations Meeting 12 March 2012 14h00 Amsterdam time

EVO direct link Pwd: gridops
EVO details Indico page


1. Middleware releases and staged rollout

1.1 EMI-1 release status

1.2 Staged Rollout

UMD-1

2. Operational Issues

2.1 Testbeds for EMI WN

  • Currently only few clusters have EMI WN deployed.
  • In general, changing the execution environment may cause problems with the users' code.
    • Changes in the client libraries installed in the WN
    • Example of problem with CMS code.
  • VOs may want to validate their applications on the new WorkerNode.
    • In order to do that they would need some EMI WNs available for the tests.

Question: Are there NGIs deploying a testbed with EMI WN?

  • Can this testbed be used by VOs to validate their code?
  • This testing activity can be coordinated by EGI.

2.2 OPS VO Membership

Recently there were few requests (triggered by the glexec monitoring tickets)to replace some ops VO members because they were no more part of the NGIs' staff. I would encourage NGIs to replace their ops members as soon as they are not working on this task anymore, if possible:

  1. Currently only 2 members per NGI are allowed in ops, it would be important to have both of them active members of the NGI's staff. If the main SAM admin is unavailable(e.g. he needs to wait few days for a new certificate), there is the need for an immediate backup.
  2. It is also important to have in ops only who strictly needs the membership.

2.3 Temporary area for job execution

Topic already discussed last year in the operations meeting: Here, for example.

  • VOs require a minimum disk space on the worker node. The required disk space is specified in the VO ID card.
  • There is the need to agree on an env. variable that points to the file system to be used for jobs' temporary files.
  • How information system advertises the information:
    • GLUE 1.3
      • SubCluster.GlueSubClusterWNTmpDir: The path of a temporary directory local to each Worker Node.
    • GLUE 2.0
      • ComputingManager.GLUE2TmpDir: The absolute path of a temporary directory local to an Execution Environment instance.
    • These information need to be available in the jobs' execution environment, in a way standardized across the different clusters.

First draft proposal: The worker node environment should contain the variable: $TMPDIR, that points to the file system where the jobs are supposed to find the required disk space.

3. AOB

3.2 Next meetings