PerfSONAR developer workshop - at Berlin GN2 TW6

From GEANT2-JRA1 Wiki

Contents

[edit]

Information (Travel & Accommodation)

Programme on protected Geant2 web page

Registration

Logistical Information

[edit]

Attendees

  1. Szymon Trocha (PSNC)
  2. Jochen Reinwand (DFN Erlangen)
  3. Verena Venus (DFN Erlangen)
  4. Andreas Hanemann (DFN Berlin)
  5. Eric Boyd (Internet2)
  6. Jeff Boote (Internet2)
  7. Jason Zurawski (Internet2)
  8. Martin Swany (University of Delaware)
  9. Cándido Rodríguez (RedIRIS)
  10. Joe Metzger (ESnet)
  11. Tihana Zuljevic (CARNet)
  12. Sasa Cavara (CARNet)
  13. Maciej Głowiak (PSNC)
  14. Roman Łapacz (PSNC)
  15. Nicolas Simar (DANTE)
  16. Frederic Loui (RENATER)

There are no VC facilities available.

[edit]

Agenda

[edit]

Monday, 23 June

Note that NML (Network Markup Language) WG meeting will be held whole Monday 9:00-17:30 in parallel to ps-dev meeting. Therefore it is intended to meet with small groups on specific topics

  • 11:00-13:00
    • Roadmap: features and time (CR, ST, NS, RL)
    • https (Slides) and AS2: getting a better understanding before the JRA1 meeting (NS, ST, CR)
    • Integration of flow MA into RRD MA (TZ, RL)
  • lunch
  • 14:00-15:30
    • Delay and anomaly detection
    • cNIS in the perfsonar release (AH, NS, ST - what do they need to do)
  • break
  • 16:30-18:00
    • MDM prototype
    • Demo preparation (AH, NS, MG)
[edit]

Tuesday, 24 June

  • 9:00-10:30
    • Mapping response message metadata to request metadata. (from Brian/Aaron email exchange recently on perfsonar-dev) Brian gave a good reason why (multiple metrics about the same interface in one query), and Aaron gave some information on 'how' this could be done: https://wiki.internet2.edu/confluence/display/PSPS/Protocol+Proposal
    • User defined 'metadata': How do you identify that a particular service is of interest to a particular user? JB: I suggest using some kind of 'keyword' parameter in the service metadata. (Just as was recently done for interfaces in the SNMP for the same reason.) Anyone have better ideas? We should discuss the advantages/disadvantages and problems associated with this. i.e. how is this information summarized and distributed for global discovery?
  • break
  • 11:00-13:00
    • Replacign http with https (the benefits, what would need to be changed in the visualisations and in the web-services, if it breaks backward compatibility)
    • Demonstrating the use of perfSONAR to monitor T1/T2 network connections. An update as to how the LHCOPN demo went and where we stand in supporting T1/T2 monitoring for LHC (JB)
    • Follow-up of NML discussion
      • Finding related MP
      • Tranformation Service
  • lunch
  • 14:00-15:30
    • Circuit auto-monitoring
      • Involving people from JRA3, cNIS
  • break
  • 16:30-18:00
[edit]

Wednesday, 25 June

  • 9:00-10:30
    • LS registration specification: What should services register to the LS? Where is this defined?
  • break
  • 11:00-13:00
    • gLS developement status and specific deployment plans
    • Update on specification
  • lunch
  • 14:00-15:30
    • LS authentication
    • Preparation for demo if necessary
  • break
  • 16:30-18:00
    • Note that DICE attribute session discussion (follow-up from Bruges) will be held at the same slot

Back to JRA1 events

Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/PerfSONAR_developer_workshop_-_at_Berlin_GN2_TW6"
Personal tools