PerfSONAR developer workshop

From GEANT2-JRA1 Wiki

Contents

[edit]

Attendees

Please indicate whether you are going to attend via VC

  1. Jeff Boote (Internet2)
  2. Martin Swany (UDel)
  3. Joe Metzger (ESnet)
  4. Szymon Trocha (PSNC)
  5. Roman Łapacz (PSNC)
  6. Maciej Glowiak (PSNC)
  7. Andreas Hanemann (DFN), Tuesday after 2pm and Wednesday
  8. Stephan Kraft (DFN Erlangen)
  9. Jochen Reinwand (DFN Erlangen)
  10. Verena Venus (DFN Erlangen)
  11. Cándido Rodríguez (RedIRIS), Wednesday by 12.30pm.
  12. Luís Marta (FCCN), Wednesday
  13. Guilherme Fernandes (RNP)
[edit]

via VC

  1. Jason Zurawski (Internet2) VC
  2. Aaron Brown (Internet2) VC
  3. Eric Boyd (Internet2) VC
  4. Mark Yampolskiy (DFN) VC
  5. Matthias Hamm (DFN) VC
[edit]

Agenda

[edit]

Monday, 7 April

10:00-18:00

[edit]

perfSONAR integration into standard Network Monitoring Frameworks

This topic should be summarised here and presented and discussed further during JRA1 plenary meeting

  • Leader: JM
  • Descirption: What should we do now that we have archives full of network measurement data? Integration with: Nagios, BigBrother, Spectrum, etc
  • Expected goals:
    • Discuss the topic and solicitation of ideas and direction (rather than a presentation of accomplished work)
[edit]

Implementation experiences

  • Leader: RL
  • Description: Exchange of knowledge gathered implementing services in Java and Perl
  • Expected goals:
    • Share development experience between partners
    • Identify benefits and problems, decisions made
    • Suggestions for the future
[edit]

Protocol specifications

  • Leader: VV
  • Description: Discuss the breakdown of documents that are needed to ensure interoperability.
  • Expected goals:
    • List of documents needed, not just for individual services but for the complete pS architecture and set of protocols.
    • Individuals signed up for working on those specific documents.
    • Have individual to start producing those document (whilst most of the people are on site - easier for questions)
  • Proposal on Document Organization
  • Action Items:
[edit]

Protocol Clarifications

  • Leader: JB
  • Description: Discuss standardization of the protocol semantics for the various services with respect to message types, subjects and event types. This should ease the writing of new services as well as allow for more code reuse between services. Uniformity in behavior between services should also help ease the construction of clients.
  • Expected goals:
    • Normalize the behavior of the SNMP MA, Utilization MA, L2 Status MAs, perfSONOBUOY MA and PingER MA
    • Normalize the behavior of the Lookup Services and Topology Services
    • Introduce new message type indicating response to a wrong request e.g. "ExceptionResponse" (see bug #331)
      • And to a larger extend the protocol for result code/error messages.
[edit]

Tuesday, 8 April

10:00-18:00

[edit]

LHC Community Support

  • Leader: NS
  • Description: Discuss what efforts are underway so they can be coordinated.
  • Expected goals:
    • Coordinated effort from all pS participants to encourage pS tools to be used by the LHC community.
      • communication between JRA4 E2EMon MP and SQL MA and needed functionalities
    • What functionalities to prioritise for the LHC operators? (visualisation, on-demand)
    • Do we need a training program on measurement results interpretation?
  • Notes: Notes
[edit]

Dynamic Circuit Support

  • Leader: JM
  • Description: Discuss perfSONAR support for dynamic circuits
  • Expected goals:
    • An understanding of the requirements for cross referencing Reservation Identifiers with Circuit Names
    • A straw-man list of additional attributes that dynamic circuit provisioning systems should provide circuit monitoring systems.
    • Determine if we need a more structured interaction between the perfSONAR developers and the dynamic circuit provisioning projects

Slides

[edit]

dLS Implementation

  • Leader: MG
  • Description: Meeting of the dLS implementors to discuss current status of the design document. See http://anonsvn.internet2.edu/svn/nmwg/trunk/nmwg/doc/dLS/dLS_spec_1.html for reference.
  • Expected goals:
    • Complete specification document - determine any areas that need to be described in more detail or enhanced due to additional design constraints (i.e. Dynamic Circuit requirements, integration of Topology information)
    • Discuss current state of implementation, ways forward for testing with clients and between services.
    • Present design decisions to developers of other services, and changes to the API that will be necessary to continue to use LS functionality.
[edit]

New metrics and future plans

  • Leader: ST
  • Description: Discuss new metrics to be added in MAs, new services, new functionalities that will be needed in near future (for other projects). This could also include ResourceProtector discussion.
  • Expected goals:
    • Identify the list of metrics with high priority
    • Timeframe for these metrics
    • Discuss schema
    • Summarise if there are any new functionalities to include in the future development
    • Discuss introducing of RP
[edit]

Wednesday, 9 April

10:00-18:00

[edit]

Optimizing large data transfers (including Push Interface)

  • Leader: RL
  • Description: Return to project of push proposal. It should also cover the possibility of sending measurement data using non-XML protocol
  • Expected goals:
    • Identify benefits and problems
    • Work on sequence diagram
  • Discussion results:
    • Decision to identify and write down the list of performance issues (e.g. parsing, object creation), possible solutions and test methods (e.g. profiling)
    • Two possible improvements for large data transmission (1. two communication channels: conrol & data; 2. in-line encoding) need further investigation
    • Introduction of new important rule in the protocol: metadata blocks are present before data blocks
    • Martin is going to prepare a general proposal of protocol improvements
[edit]

Roadmap for release 3.x and further

  • Leader: NS
  • Description: Announce and agree a roadmap for next pS releases.
  • Expected goals:
    • Draw w roadmap for the next releases
[edit]

Authentication and Authorisation

Start when Candido arrives

  • Leader: CR
  • Description: Authentication will be enabled in EU for some services and for some NRENs around summer 2008 (NOC and PERT restricted)
  • Expected goals:
    • Assess the impact on US NOC groups seeking for data in EU
    • Highlight the AutZ principles that are foreseen.

Slides

[edit]

Topology Service Discussion

  • Leader: AH
  • Description: Discuss the current ways topology is shared. (cNIS, Internet2 topology service, original java topo service)
  • Expected goals:
    • Determine exactly what common request/response messages will be supported across these multiple efforts. (cNIS has said they will be compliant with pS protocol - what does that mean?)
    • Finding the closest MP (IP level): presentation of the proposal of the algorithm and of the information to be registered to the LS.
  • Action points:
    • AH: Specify NM-WG request/response to cNIS for getting a mapping between IP interface address and router host name
    • AH: draft a timeline with a simple starting point which can be achieved by the end of the year
    • AH/MS: registration of the MA to the LS to enhanced. It should contain a summary of interface addresses. Internet2 has an algorithm for this.
    • AH: Detail the business logic which should be implemented by perfsonarUI.


Back to JRA1 events

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