FrenchSitesInputtoTEGOp

Un article de lcgwiki.
Revision as of 15:16, 10 novembre 2011 by Chollet (talk | contribs) (Other comments)
Jump to: navigation, search

BACK to TEG

Input provided by french sites

Input for WG1 : Monitoring & Metrics

Input for WG2 : Support tools & Underlying services + WLCG operations

  • Scope ====
    • Support tools : Ticketing, Accounting tools, Request trackers,Administration tools [GOCDB, CIC]
  • Underlying services : Messaging services, Information services
  • WG2 Sub-Wiki : https://twiki.cern.ch/twiki/bin/view/LCG/WLCGTegOperationsWG2
  • What works well? What is used ?
  • What are the three main problems?

Input for WG3 : Application Software Management

Input for WG4 - WG 5

Scope

  • Middleware operational requirements
    • Example topics: log files, error messages, manageability, robustness, system requirements, documentation
  • Service and middleware configuration
    • Example topics: puppet, quattor, yaim...
  • Service and middleware deployment
    • Example topics: Packaging, upgrade paths, release schedules, rollout policy
  • Middleware distribution
    • Example topics: Distros - EMI, EPEL, UMD, OSG, repositories, OS support, source availability

What is in use currently and works well?

  • Quattor (FC)

Top problems

  • Too many information on logfiles or finding the good information on log file is too hard (IN2P3-LAPP)

What takes the most effort?

  • Middelware dependency understanding (IN2P3-LAPP)

What can be improved about operational procedures?

  • A clear and single channel to announce a new release and documentation (IN2P3-LAPP)

What can be dropped?

Strategic directions you would like to recommend

  • Middelware compatibilities with the larger set of technical constraints (yaim/quattor, NAS/SAN storage infrastructure,...) (IN2P3-LAPP)

Other comments

  • Aware of EGI stage rollout procedure ? (FC)
  • A clear statement regarding "EGI staged rollout procedures" is required from WLCG. (FC)


  • besoin relocable mware
  • distribution mware :ergonomie des interfaces EMI UMD
  • OS : distribution UI en 32 bits toujours nécessaire
  • solution SL6 pour les workers et serveurs de disque nécessaires rapidement