Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    Deployment team

    → Europe/Zurich
    VRVS - Ocean virtual room

    VRVS - Ocean virtual room
    Jeremy Coles
    Minutes
      • 11:00 → 11:20
        Experiment problems/issues 20m
        Review of weekly issues by experiment/VO - LHCb Of course theplatform used by the WNs of the CEs (OS, architecture and possibly compiler usedfor the client libraries) should be advertised in a consistent way according toa well defined convention and this should be enforced before the CE is put intoproduction. The current definition of the Glue schema information are still veryvague and difficult to use for matching resources. Many equivalent platformshave different advertisements and the version of the compiler is not published(which is not yet relevant but will in the near future when applications mightmove to gcc 4.1 for example). We remind that the LCG has defined a convention avery long ago for the applications (__) that is usedby the LHC VOs and matching capabilities should be provided based on thisnomenclature. - CMS - ATLAS - Other
      • 11:20 → 11:35
        SE downtime 15m
        Clarify site implications from SE downtime, as tests on CE of course fail as well since they need a default SE. Should the site be put in complete downtime? (Note from the minute taker, the default SE could be changed to some other site during the SEs downtime) How does this affect the VOs? Progress on 2007-03-26: In progress. Maite is coordinating. Progress on 2007-04-16: No news, to follow up Progress on 2007-04-23: Proposal to follow the SAM site availability calculation rules: http://goc.grid.sinica.edu.tw/gocwiki/SAM_Metrics_calculation#head-a5fda62884f5a769de0fa7c3532622a9f94fb40c Which would mean: - for sites with only one SE, if the SE is down, the whole site will be considered as down, so schedule site downtime - for sites with more than 1 SE, if only one (or less than all) will be down, schedule downtime only for that SE - for sites with more than 1 SE, if all will be down, schedule site downtime Summarizing: If a site has no SEs available, it should be declared as down Progress on 2007-05-07: There is a long running e-mail discussion on this. Progress on 2007-05-07: no update Progress on 2007-05-21: In progress.
      • 11:35 → 11:55
        Action review 20m
      • 11:55 → 12:00
        AOB 5m
        - Decision on F2F meeting in July - Is Duram the only site that uses pre-emption? - UPDATE: job priorities and YAIM Very Short term: the FQAN VOViews should disappear from the information system. The VO:atlas view will then show inclusive information for ATLAS jobs submitted with any role. This means the FQAN VOViews should not come anymore with the default YAIM configuration (action for SA3) *and* they should disappear from the sites which already have deployed it, both via YAIM and by hand (action for SA1) UPDATE: T1s requested via broadcast and GGUS tickets to remove the configuration manually.