WIL Conf call 18 December 2007

From GEANT2-JRA1 Wiki

Contents

Meeting details

Date and Time: Friday, the 18th of December 2007, 11:00 - 12:30 CET, 10:00-11:30 BST.

Skype

Actions

  1. SK to investigate why the BWCTL MP tests don't work with the MDM Pilot. To check with perfSONARUI plug-in
  2. NS to check the timeline or LIPCU (for ordering the kits and scheduling the workload)
  3. ST to add in the document the details as which ps-base to go for or which schema version.
  4. AH: Exchange utilisation range (color) Evaluate: how the visualisation could cope with that change (+ ressource estimate)
  5. NS find out who has constrains on providing utilisation data.
  6. NS to plan the end of the Pilot
  7. NS to draft a prototype plan
  8. NS to start setting up the quotes for Prototype and LHC-OPN
  9. LK to follow-up on the starting date for the LHC-OPN activity.
  10. SK to investigate if we can get RH support after having modified the kernel
  11. LK to indicate when the release 3.0 will be available. NS to contact PW about training schedule.
  12. LK to send a summary about issues relater to 3.0 and on-time parts.
  13. SK to send an email about the traceroute : where are they visualised. Which ones are available?


Minutes

  1. Last Meeting Actions - See Below
  2. EC report, no particular mention made about perfSONAR and the transition to service. This means we are doing good (but also that we can improve to be remarked with a "good score").
  3. Issues
    • Andreas : DFN cannot share values. They can only share pre-defined ranged of utilisation (to anybody). The information must be exported by the MA.
      • Evaluate: how the visualisation could cope with that change (+ ressource estimate). Who makes the changes on the MA (DFN - the NOC doesn't have much ressources for it; transformation service: JRA1 doesn't have this service in its pipeline so far)
      • Might have some benefits for other NRENs which don't want to provide that information. Who else has that constrain?
    • ST: How to get further with MDM?
      • Plans for the end of the Pilot and the beginning of the prototype is needed. Leave a break between the Pilot and the prototype.
    • ST: when starts the LHC-OPN activity?
    • LK: deployments and redHat 5.0
      • Push Meinberg or redHat
    • LK 3.0
      • Training is scheduled mid-March. Need postponing
      • Issues with Telnet/SSH MP and with BWCTL MP
      • AA tests = Partricia and David involved.
    • LK and traceroute
      • where are they stored and where are they represented
    • NS RRD MA
      • no profiling done. ST: wait for Ilias scripts.


Agenda

  1. Last Meeting Actions
  2. EC Review report
  3. Current Issues (all to prepare a list)
    • Deployment issues
    • Utilisation categories - AH
  4. Security
  5. JRA1 demo at plenary
  6. Rome sessions organisation
    • Tuesday 09:00 - 10:30 - AA/eduGAIN (CR, NS, web-servi develop?, GUI developer?)
    • Tuesday 13:00 - 17:30 - cNIS v1 developer meeting (DS/PM, NS, JK, DM?)
    • Wednesday 09:00 - 13:00 - Plenary (JRA1 demo - who?) ; attendance (who?)
    • Wednesday 14:00 - 15:30 - JRA1-PERT progress, demo (who: AI, GC, NS, CW)
    • Wednesday 16:00 - 17:30 - JRA1-JRA2 (netflow progress, set-up a document template to submit to TF-CSIRT, netflow deployment) (NS, HT, AI, JKH)
    • Thursday 09:00 - 13:00 - Cross activities (monitoring, ticket, statistics, users, training) (NS, LK, ??)
    • Thursday 09:00 - 18:00 - JRA1 meeting (someone to lead and organise session, session animation)
    • Friday 09:00 - 13:00 - TC Meeting (NS)
    • Friday 09:00 - 13:00 - JRA1 meeting (Someone to lead, session animation)
  7. Priority Action Plan - identify our priorities for the next 6 months
    • NOC and PERT requirements
  8. Change process
  9. Documents needed for perfSONAR
    • Gina
    • protocol
  10. Product contact information - Primary dev, Backup dev and QA/team leader
  11. MDM-perfsonar release
  12. Next perfSONAR meeting

Last Meeting Actions

  1. NS to try the BWCTL plug-in. - Not working
  2. WIL to evaluate EB's proposal for packaging software. - Done
  3. ST to get confirmation that the reutilisation of ps base is clear to everybody. Can be done through pS3.0 specs. - Done
  4. NS to check with Baiba about who in Latnet is involved - - Possible actions: move manpower to another NREN: Ugent, Arnes. Work on SNMP MP, TrS, QoS metric into RRD MA. Can left 3PM to Latnet for Network engineers to try things out. AH not favourable
  5. NS to ask JM and LHC to specify who are the users of those data so that we can tailor the visualisation.
  6. NS to coordinate the development side for ps3.0 - release management follow this up
  7. LK to provide a plan for release and testing. - Done
  8. NS to schedule a conf call with the developers for release 3.0 (1st of October) - Done
  9. ST to add in the document the details as which ps-base to go for or which schema version.
  10. LK to check that pSbase has all the feature required.
  11. WILs to identify topics for the Rome meeting. - Done
  12. NS to as a general question about the topic to the ML.- Done
  13. AH (feature for visualisation and users), LK (service desk features) to attend cNIS meeting (10th of October, Cambridge)- Done
  14. NS to attend cNIS meeting via VC.- Done
  15. AH, LK and NS to organise themselves for the cNIS meeting- Done
  16. LK to coordinate the deployment of the GEANT RRD MA (restricted to MDM participants)
Personal tools