1 / 6

Improvements in the CREAM.pm module

Improvements in the CREAM.pm module. AliEn WS CERN 7-Oct-2010. New implementations. We have implemented to new features affecting basically the information source used by AliEn : We get rid of any query to the CREAM-DB

orpah
Télécharger la présentation

Improvements in the CREAM.pm module

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Improvements in the CREAM.pm module AliEn WS CERN 7-Oct-2010

  2. New implementations • We have implemented to new features affecting basically the information source used by AliEn: • We get rid of any query to the CREAM-DB • The only information source used at this moment is the resource BDII • We observe the “Status=Maintenance” of the CREAM-CE published in the BDII to prevent any new bunch of agent submission

  3. Getting rid of the CREAM-DB • One of our “best” features implemented in the current CREAM module version • In the past we observed instabilities in the “resource” BDIIs • In principle the idea was good and accorded together with the CREAM experts • Based on the experiences collected this summer we got rid of this info source • Too many timeouts when the CREAM-DB was not properly purged • Heavy query • Waiting for a new inform provider tool which will provide the number of running/waiting jobs besides the BDII • Status of the new implementation: In production at CERN and Subatech

  4. Using the GlueCEStateStatus information • Motivation: Each time CREAM-CE was declared in Maintenance, Draining… mode in the BDII we had to take it manually out of production • Such procedure does not escalate • Site admins had to prevent us before doing any operation • Goal: Let’s automatize it • Site admins can operate easily the service without even preventing us

  5. Using the GlueCEStateStatus information • Bad news: • We submit in direct submission mode • With this procedure the matchmaking features of the WMS simply cannot be applied • It is more complicated than simply adding this requirement to the level of the jdl… • Good news: • Not so complicated… • The status of each CREAM-CE has to be queried before performing any new submission

  6. Using the GlueCEStateStatus information • No matter how many CREAM-CEs are declared in the LDAP, the status of each CREAM-CE is queried to the BDII and only those in production will be used • Status: Tested this week in Subatech, Jean-Michel has confirmed its performance • Ready to be put in production for the rest of the sites • Next candidate: RAL

More Related