Summary of the interactions with users from Spanish Tier1

Contact persons: Josep Flix (jflix at, Xavier Espinal (espinal at and Gonzalo Merino (merino at

Friday 23rd January 2009: first feedback from Gonzalo Merino.

  • Problem due to too many simultaneous connections: already planned an action to fix it.
    Very high priority!
    Migration to integration database done on Tuesday 27th Jan

  • About the site status: suggested to employ something similar to Site Status Board also for other VOs. Actually this has already been proposed to LHCb. Still no answer yet.
    Eventually Andrei gave a positive answer (27th Jan 09), Pablo promptly answered he will provide a prototype implementation for LHCb
    Waiting ...

  • About the targets: it would be interesting to have them published in the Gridmap. The problem is where to find them.
    Gonzalo provided values for the pledged values about CPU slots for jobs VO by VO, and Elisa introduced them in the DB schema. Now they are displayed as 'targets' in the gridmap (27th Jan 09)ok
    Important remark Don't call them 'pledged values'! They are not pledged values. The only pledged values are the KSI2K for every VO average in a time period. See feedback from Nikhef where Jeff gives a clear explanation of this.

  • Some metrics are missing: yes, not all VOs provide all metrics. Ask again

  • About metrics: add queued jobs.
    Julia answered (26th Jan 09)Most of job processing information (at least for ATLAS and CMS) is consumed from ATLAS and CMS Dashboard. The problem with pending jobs is that this data is unfortunately not very reliable, due to incomplete and not reliable input from GRID related sources. While info about running and accomplished jobs is mainly obtained either from jobs themselves or UIs of the Job submission tools (and it is pretty consistent with what we see in the local batch systems monitoring at the sites), number of pending jobs is highly dependent on information of Grid related sources, and it is normally not reliable at all. We are certainly looking for ways of improvements and are working in this direction, but for the current moment I am afraid, if we publish this data, it can be quite confusing.

  • About CMS/data transfer: the values published are inconsistent with the content of the URL associated to that metric. Moreover, it would be better to have a link redirecting to a URL phedex page with a graph showing the evolution of the rate into pic from all sources in the last 24h for instance.
    Check again with Pablo
    Julia adds (26th Jan 09): The limitation we currently have is due to the fact that Phedex does not for the moment provide machine readable information about metrics which we would like to publish. It is also not clear how to generate links to Phedex graphs with concrete set of attributes. But this limitation is temporary. We are working with Phedex developers and hopefully soon will get all necessary API from Phedex
    Waiting for new release of Phedex...

  • About LHCb/data transfer: no value available. This seems to be because of a lack of activity. Asked to Adrian many times.
    Check from time to time if some data are published..

-- ElisaLanciotti - 15 Jan 2009

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2020-08-30 - TWikiAdminUser
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox/SandboxArchive All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback