MDM Pilot NOC Training Conf Call 5 Feb 2008

From GEANT2-JRA1 Wiki

[edit]

Agenda

  1. training development plan + update (where we stand)
  2. training date
  3. provide the training material to the MDM Pilot NRENs (for the 7/02)
  4. Rome's presentation overview
[edit]

Actions

  1. Update Berlin training material - NS to investigate with Peter Webster.
  2. Provide information about the interpretation of the delay and throughput information - NS to coordinate with Erlangen to capture specific events and work with MDM participants, RHJ to have a data interpretation.
  3. NS to provide few scenario and data of interest to GARR
  4. GARR translate slides, use cases identified and feedback forms to English
  5. GARR to ensure buy in from NOC manager
  6. pSUI: show utilisation, dorp and errors on the same graph
  7. Unrelated issue: difficulty to deploy the BWCTL MP
  8. Erlangen to add TCP throughput historical information between NRENs
  9. Next call: 26th of February, 10:00 CET
  10. GARR to make proposal for delay display on pSUI
[edit]

Notes

Attendance: NS, MR, AI, GI

  • GARR's view are more on establishing a permanent cycle between the NOC and perfSONAR (as expressed in the presentation)
    1. Present the tools (one hour) - they expect they'll be provided with presentation by the project (i.e. an update from the Berlin training). This is a change over the orginal plan. They provide few real cases that can be solved using the visualisations. (that's the added value of GARR's experience. They also state that they'll gather use cases from the presentation to the NOCs.
      • Issue foreseen: not are used to status up/down type of information. They need infomation on how to interprete delay and throughput information.
      • the slides are in Italian, they can be translated to English
    2. For two weeks, they ask the NOC to use the visualisation tools when solving case.
      • GARR is working on feedback form
      • Topology information is needed to understand the measurements (servers connected to what switches, routers, etc).
      • If measurement unstable, dig to indentify what is happening
      • Issue: requires buy in from NOC manager
  • For PERT, a good tool user is sufficient as they are used to deal with delay, throughput information.
  • GARR mentioned that to get the NOC attention, it needs to happen during a not so busy period. February is very busy for GARR. So they suggest to postpone the GARR training to March. As the exercice is too important for the project, it is agreed.
    1. When a new release is provided, GARR present it to the NOC to gather feedback and directions for the activity.
  • Questions related to the Rome presentation
    • ST mentioned that the presentation wasn't about training, but about feedback collection.
Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/MDM_Pilot_NOC_Training_Conf_Call_5_Feb_2008"
Personal tools