-- CyrilLorphelin - 13 Jun 2008

COD Tools


The third pole “COD tools” will be dedicated to the internal/external handling of technical requirements for the current and future COD work needs, coming out namely from the second pole.

Namely, the inventory, the follow-up of technical requirements chargeable to external providers – i.e. besides COD teams and contributors - and the internal development themselves can be achieved by this pole. Also, COD teams need to have specific needs fulfilled such as regular update of COD dashboard (integration of the daily COD tools and of several external sources including monitoring tools), reliable access to operations and monitoring tools results whatever they are or may become. This pole will integrate the work that has already started in EGEE-II on this matter in 4 working groups. Remark: This pole should be in charge of the technical interface with the external contributors and technical providers (e.g. monitoring tool developers, OAT).

Actions List

Actions list from COD-16 meeting

Actions List Federation/Pole Started Last update status
Improvements of Handover form Pole3 COD-15 COD-16 on-study
Creation of regional dashboards for SWE and NE Pole3 COD-15 COD-16 done
Failover procedure for GOCDB Pole3/IT COD-15 COD-16 on-going
Failover foc CIC DB Pole3 COD-16 on-going
Integration of ldap mechanism into failover Pole3/Osman COD-16 on-going
Study mechanism of replication/failover for LCF , VOMS ,BDII Pole3/Kai COD-16 on-going
Study mechanism of failover at site level Pole3/Kai COD-16 on-going


Failover of Grid Ops Tool and core services

Tools Improvements for COD

  • Collect and implement improvements to tools offered or used by COD Team and makes sure that all needs are satisfied
  • Ensure that improvements are done
  • Collect, analyze and present suggestions to COD (discussion on feasibility, impact to other areas etc.)

COD dashboard

  • Evolution towards N regional instances + 1 specifically dedicated for C-COD. Incl Alarm weighing mechanism.
  • Request for change on monitoring tools through OAT
  • Follow-up of requirements on OAT
  • Follow-up of requirements on the separate tools

Integration of tools into EGI

At the beginning of EGI each region must be able to work on stand-alone mode which means that each EGI :
  • Will integrate COD Tools in their own scope
  • Will operate these tools
  • Will assume the failover of these tools also !!
Immediate Actions :
  • Determine ASAP on how countries will integrate COD tools : totally , partially , and when ?
  • Study the model given by OAT
  • Begin the work of integration with a ROC partner (For example Italy was interested for an instance of CIC portal)
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2011-06-16 - VeraHANSPERExternal
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback