Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "OMB"

From EGIWiki
Jump to navigation Jump to search
Line 23: Line 23:
|}
|}
== The Operations Manager's Agenda==
== The Operations Manager's Agenda==
===March 2011===
* ACTION 1. All NGIs to contact sites that deploy gLite 3.1 DPM to check problems and timelines to upgrade to gLite 3.2 or UMD 1.0, and to report the feedbacl to the OMB. In case of many sites with upgrade problems, we will request a memory leak in glite 3.1 DPM (due to a VOMS library) to be fixed by EMI.
* ACTION 2. DEADLINE 09 MARCH. To provide input on your self-assessment of NGI international tasks that will be used for MS109. Input is collected on wiki [https://wiki.egi.eu/wiki/NGI_International_Task_Review_MS109 here].
NGI international task metrics will be collected by EGI.eu [https://wiki.egi.eu/wiki/NGI_International_Task_Metrics_MS109 here]


===February 2011===
===February 2011===

Revision as of 18:05, 1 March 2011

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security



The Operations Management Board (OMB) is a EGI policy board which aims to define policies needed to provide a reliable transparent infrastructure composed of multiple national infrastructure providers (Terms of Reference).


Contact information noc-managers at mailman dot egi dot eu
Membership NGI Operations Managers, EGI-InSPIRE SA1 task leaders, EGI.eu COO
Meetings OMB on Indico
OMB Documents Document DB
Actions noc-managers queue on EGI Request Tracker

The Operations Manager's Agenda

March 2011

  • ACTION 1. All NGIs to contact sites that deploy gLite 3.1 DPM to check problems and timelines to upgrade to gLite 3.2 or UMD 1.0, and to report the feedbacl to the OMB. In case of many sites with upgrade problems, we will request a memory leak in glite 3.1 DPM (due to a VOMS library) to be fixed by EMI.
  • ACTION 2. DEADLINE 09 MARCH. To provide input on your self-assessment of NGI international tasks that will be used for MS109. Input is collected on wiki here.

NGI international task metrics will be collected by EGI.eu here

February 2011

  • ACTION 1. DEADLINE 10 Feb. Submmission of QR3 report and metrics:
    • Please supply NGI reports and metrics for QR3 at here
    • Please supply SA1 task reports and metrics for QR2 at here
  • ACTION 2. DEADLINE 10 Feb. Survey on supported OS platforms, LB, service management and monitoring (for EMI components). We would like to launch the first SA1 survey covering the following capabilities: Logging and Bookkeeping, Service Management and and Auditing and gLite-CLUSTER. All these capabilities are relevant to EGI and feedback - after internal processing - will be provided to the EMI project, so it is very important that you give this survey high priority. For some of the questions, you may need to consult your site managers. Instructions for submission.
  • ACTION 3. DEADLINE 10 Feb.Call for Requiements: EMI 2.0 and Nagios tests. The requirement gathering process for EMI 2.0 (ARC, gLite and UNICORE) needs to start now, as EMI software development will start in May 2011, and all requirements need to be internally gathered and prioritized in the OMB and OTAG (depending on the type of requirement), and then discussed at the Technical Coordination Board of EGI. All requirements are gathered through the RT requirements queue.
  • ACTION 4. DEADLINE 10 Feb. APEL-Pub change of policy At the last OMB in Amsterdam, we discussed the possibility to change the policies of the APEL-Pub probe. APEL-Pub is an OPERATIONS probe, which returns CRITICAL if after 30 days the site is not publishing accounting data. This probe was introduced during EGEE-III to enforce publication of accounting data (at that time a large fraction of sites were not publishing correctly). It is a OPERATIONS test, as it generates an alarm in the Operations Dashboard when it turns to CRITICAL. The Italian NGI requested this policy to be reviewed, to return CRITICAL after 7 calendar days (instead of 30), as lack of publication of accounting records after 7 days is a good symptom that something needs to be fixed in the site, and waiting 30 days makes debugging of the problem more difficult. As at the end of February the R-GMA central databases will be decommissioned, having this change of policy will help the RODs to pro actively support the sites that still have to migrate to the Active MQ client. At the OMB the majority of the NGIs were in favor, and a couple were not. We decided to poll the missing NGIs with this mail. So, if any NGI objects for this change, please reply by Thursday 10. Silence will be interpreted as agreement.

Previous OMB agendas


Tferrari 09:49, 4 February 2011 (UTC)