From GEANT2-JRA1 Wiki

Contents 1 Dates 2 Venue 3 Registration 4 Hotel 5 Agenda 5.1 Wednesday, 28th of March 5.2 Thursday, 29th of March 6 Parallel Sessions 6.1 General Topics 6.1.1 Evaluation Criteria 6.1.2 Feedback and training - Strategic orientation 6.1.3 Additional topics 6.2 WI2/MCF (Athanassios Liakopoulos) 6.2.1 MCF 6.3 WI3/Services (WIL Szymon) 6.3.1 Lookup Service rollout in the pilot 6.3.2 Extending the Developers FAQ 6.3.3 AA implementation 6.3.4 WI3 Y4 planning 6.3.5 LS API for visualisation and other services 6.3.6 Additional topics 6.4 WI5/Measurement Tools (WIL Stephan) 6.4.1 Netflow 6.4.2 Additional topics 6.4.3 WI5 - Y4 plan review 6.5 WI6/Visualisation (WIL Andreas) 6.5.1 Release process of visualisation tools 6.5.2 Visualisation tool development and year 4 plans 6.6 SA3 WI-15 In Service Support (WIL Loukik) 6.6.1 Service Desk Set-up - Requirement and Brainstorm 6.6.2 Paper about perfSONAR release management process (QuaTIC conference) 6.6.3 Testing experiences and plans 6.6.4 Release Management - Micro release and bundle 6.6.5 Documentation 6.6.6 Minutes 6.7 Session Proposal Template 6.8 Actions from the last meeting ISS session

Dates

Wednesday 28th of March: 10:00 - 18:00 Thursday 29th of March: 09:00 - 13:00

On the contrary of what was previsouly annouced, the JRa1 meeting won't be coupled with the Pilot installation training session.

Venue

The meeting will be kindly hosted by Surfnet, Radboudkwartier 273, 3511 CK Utrecht, The Netherlands. Surfnet's office is based in the shopping mall 'Hoog Catharijne', in the officecomplex Radboudburcht on the 4th and the 5th floor. http://www.surfnet.nl/info/en/organisation/directions.jsp

Registration

http://www.terena.org/events/details.php?event_id=952

Hotel

• There is a hotel nearby that has rooms available, it is however unfortunately not possible to make a "group reservation" at this hotel. This hotel is 30 min from the SURFnet office (by public transport) and costs around 100 Euro a night per person.

So if you want to stay here you should make your reservations as soon as possible at: http://www.bastionhotel.nl/en/ There are currently 10 rooms available for March 27 and 19 rooms for March 28.

• SURFnet has also arranged a group reservation at the Park Plaza hotel nearby the SURFnet Offices, these rooms costs 143 Euro a night. You can make a reservation by email: ppures at pphe.com, please refer to "SURFnet". The rooms will be held until February 23.
• If for some reason you were unable to get hold of a hotel room and need assistance in finding one in a city nearby (for example

Amsterdam) Monique (see mailing list for email address).

Agenda

Wednesday, 28th of March

• (9:00 - 10:00: WIL meeting)
  
• 10:00 - 10:20: Introduction
  
• 10:20 - 10:30: Passive - Sven Ubik -
  
• 10:30 - 11:00: Year 4 objectives - Nicolas Simar
  
• 11:00 - 11:15: perfSONAR, JRA1, MDM and pilot.
  
• 11:15 - 11:30: Hades Alarm System
  
• 12:00 - 13:00: lunch
  
• 13:00 - 14:30: Parallel Session slot1
  • WI5 - Y4 plan review (video-conf - DFN JRA1)
  • LS rollout in the pilot and LS API
  • MCF
  • Service Desk Set-up - Requirement Brainstorm
• 14:30 - 14:50: Break
• 14:50 - 16:20: Parallel Session slot2
  • Release Management - Micro Release and Bundle
  • Visualisation tools development and year 4 plan (video-conf - DFN JRA1)
  • Extending the Developers FAQ
  • Evaluation Criteria
• 16:20 - 16:40:Break
• 16:40 - 18:10: Parallel Session slot3
  • Documentation
  • Visualisation tools Release process (video-conf - DFN JRA1)
  • WI3 Y4 planning
  • Netflow

Thursday, 29th of March

• 09:00 - 11:00: Parallel Session slot3
  
  • AA Implementation (video-conf - DFN JRA1) (starts 15 min later)
  • Testing Experiences and plans
  • Feedback and training - Strategic Orientation (starts 15 min later)
• 11:00 - 13:00: reports on parallel sessions

Parallel Sessions

General Topics

Don't forget to be SMART (Specific, Measurable, Attainable, Realistic, Timely).

Evaluation Criteria

• Session helper: Nicolas; WI: all, session lenght: 1h00
• Description: All the developments we do won't be part of the MDM service on the long run for support cost reasons (This doesn't mean that the development of those services not part of the MDM will be abandoned). During the last review the EC has asked to limit the tools involved in the MDM (web-services and visualisation), they have also asked to merge the functionalities of multiple tools. In order to, in the future make a choice based on specified criteria, we need to list the criteria that the different tools need to comply with and the way to have users judging which tools should be part of the MDM service.
• Attendance: Service deployers, NOC members, PERT members.
  • Expected: Chris, Jon Kare, Avgust, Alessandro, Ulisses, Hans, Sven.
  • Confirmed: Nicolas, Sven
  • Apologized:

Feedback and training - Strategic orientation

• Session helper: Nicolas; WI: all, session lenght: 1h00
• Description:
  • How to get feedback from NOC and PERT? We need to focuse our development towards what the NOC and PERT needs. How can we get more effectively feedback from them?
  • How to train NRENs NOC and staff member to use the perfSONAR tools? What format? (hand out, let them alone, scenarios on the network).
• Attendance: Service deployers, NOC members, PERT members.
  • Expected: Chris, Jon Kare, Avgust, Alessandro, Ulisses, Hans, Sven, Jerome.
  • Confirmed: Nicolas, Sven, Jerome
  • Apologized:

Additional topics

• Cross activity colaborations
• Overal goal description

WI2/MCF (Athanassios Liakopoulos)

MCF

• Session helper: Athanassios Liakopoulos; WI: 2, session lenght: 1h30
• Description:
  • L3 metrics examination at IBBT
    • First Pathload results
    • Initial Analysis Framework
  • L1/L2 metrics composition
  • CNM dashboard
• Attendance:
  • Expected: Thanassis, Andy, Johannes, Brecht, Maurizio, Andreas, Stephan, Jochen;
  • Confirmed: Andreas, Matthias, Andy, Johannes, Jochen, Stephan, Thanassis
  • Apologized: Brecht
• Notes

WI3/Services (WIL Szymon)

Lookup Service rollout in the pilot

• Session helper: Maciej; WI: 3-5-6, session lenght: tbd (1h30)
• Description: The objectives of the sessions are
  • to provide guideline on how the services and visualisation will make use of the LS during the Pilot (May-September).
  • to define a workplan to have the visualisation tools accessing the LS (what data do they need, from which instance).
  • to describe the information registered per service and the one needed by the visualisation (potential harmonisation)
  • (optional) to describe failure scenario of the LS and multi-LS seen from the point of view of the web-services and visualisation tools. Describe an expected behavior in such conditions (registration, information propagation, request from visualisation).
• Attendance:
  • Expected: Maciej, Loukik, Nicolas, Szymon, Andreas, David, Matthias, Vedrin, Nina.
  • Confirmed: Andreas, David, Matthias, Maciej
  • Apologized: Vedrin, Nina, Szymon

Extending the Developers FAQ

• Session helper: Loukik; WI: all, session lenght: 1h00
• Description: Based on identified questions raised on the mailing lists, identify additional FAQs, draft answers, identify who could best check the answer and take the opportunity that most of the people are there to fill the FAQs. Make use of contact detail to identify who to ask.
• Preparatory work: the session leader is to go over ps-dew emails to identify FAQs.
• Attendance:
  • Expected: Candido, Maciej, Matthias, Stijn, Andreas, Uros, Danijel, Loukik, Jochen/Stephan, Gijs, Sven.
  • Confirmed: Maciej, Jochen/Stephan
  • Apologized: Szymon

AA implementation

• Session helper: Stephan Kraft; WI: 3-5-6, session lenght: 1h30
• Description: The objective for this session is to get status update and a common understanding about what the visualisation developers and the web-services developers will have to do to integrate and make use of AA. Will they be provided with classes or only with an interface specification. An secondary objective is to have them working together on that topic, so that we end-up with a single implementation per programming language. The AA developer should laso describe his worplan for next months so that the others know what to expect and when.
• Topics:
  • Status of the AS development (Cándido)
    • Phases of development
  • Authorization process for developers of clients (?)
    • There are three cases. Which is mine?
    • Which library? Can you provide me some classes?
  • Authorization process for developers of resources (?)
    • Which library? Can you provide me some classes?
    • Flow of a request/response with authorization request
  • Authorization process for developers of AS (?)
    • Which library?
    • Using eduGAIN

• Attendance:
  • Expected: Cándido, Maciej, Andreas, David, Uros, Jochen, Matthias, Maurizio, Jeff, Loukik
  • Confirmed: Matthias, Andreas, David, Maciej, Cándido, Jochen
  • Apologized: Maurizio (maybe via VC), Jeff
  • slides
  • minutes_SK

WI3 Y4 planning

• Session helper: Nicolas; WI: 3, session lenght: 1h00
• Description: Start from high level WI4 Y4 objectives: understand them, comment them (if needed), prioritise them and refine the objectives for each WI. This work will lay the ground for the ressources needs identification for Y4+6M as done previsouly for Y3+6M. As input for this session AA status update and workplan, TopS as well as MA+LS workplan are necessary.
• Attendance:
  • Expected: Nicolas, Maciej, Roman, Ulisses, Candido.
  • Confirmed: Maciej, Stephan, Jochen, Sven
  • Apologized: Szymon, Roman

LS API for visualisation and other services

• Session helper: Maciej; WI: 3-5-6, session lenght: tbd
• Description: The objective is to identify the requirements for API - a set of classes and message genrators for LS. This API will be used by other services and visualisation tools as well as other activities e.g. SA3.
  • Input from visualisation developers
  • Input from Anand Patil
  • Timescale - for when it is needed
• Attendance:
  • Expected: Maciej, Andreas, David, Vedrin, Nina
  • Confirmed: Matthias, Andreas, David, Maciej
  • Apologized:

Additional topics

• What in the perfSONAR base and what to prioritise
• Service performances
• Schema work - plenary

WI5/Measurement Tools (WIL Stephan)

Netflow

• Session helper: Hans Trompert; WI: 5, session lenght: tbd
• Description:
• Attendance:
  • Expected:
  • Confirmed: Alessandro Inzerilli, Jerome
  • Apologized:

Additional topics

• A Trouble Ticket MP : Is it feasible? What should we be careful of? How could it be done?

WI5 - Y4 plan review

• Session helper: Stephan; WI: 5, session lenght: 1h00
• Description: Start from high level WI5 Y4 objectives: understand them, comment them (if needed), prioritise them and refine the objectives for each WI. This work will lay the ground for the ressources needs identification for Y4+6M as done previsouly for Y3+6M.
• Tools:
  • Command Line Measurement Point (Guilherme)
  • Flow Subscription Measurement Point (Hans)
  • Tbwtools - TCP performance analysis (Sven)
  • SSH/Telnet Measurement Point (Stijn)
  • Tracefile Capture Measurement Point (TCMP) (Uros)
  • Short-timescale available bandwidth monitoring (ABW) Measurement Point (Sven)
  • Hades Measurement Archive (Jochen)
  • BWCTL Measurement Point (Jochen)

• Attendance:
  • Expected: Stijn, Jochen, Sven, Uros, Mark, Gijs, Uros, Loukik, Danijel
  • Confirmed: Stijn, Jochen, Sven
  • Apologized:
  • Minutes: http://wiki.perfsonar.net/jra1-wiki/images/1/10/WI5_Y4_plan_review_minutes.doc
  • 

WI6/Visualisation (WIL Andreas)

Release process of visualisation tools

• Session helper: Andreas Hanemann; WI: 6,15, session length: 1h00
• Description:
  • Approve process proposal
  • Steps to be taken for CNM/perfsonarUI.
• Attendance:
  • Expected: Andreas, David, Danijel, Jon, Matthias, Vedrin, Nina, Loukik, Luis, Nicolas
  • Confirmed: Andreas, David, Matthias, Luis
  • Apologized: Vedrin, Nina

Visualisation tool development and year 4 plans

• Session helper: Andreas Hanemann; WI: 6, session length: 1h30
• Description:
  • Development of VisualperfSONAR
  • Issues for CNM/perfsonarUI not related to release process (Looking Glass integration, BWCTL for plug-in design) needed?
  • Collaboration with RNP (ICE tool)
  • cNIS and visualisation tools
  • infographist (year4)
  • evolution from visualisation into analysis tools
• Attendance:
  • Expected: Andreas, David, Danijel, Jon, Matthias, Vedrin, Nina, Stijn V., Stijn M., Verena
  • Confirmed: Andreas, David, Matthias, Stijn M., Jochen, Jerome
  • Apologized: Vedrin, Nina, Verena

SA3 WI-15 In Service Support (WIL Loukik)

Service Desk Set-up - Requirement and Brainstorm

• Session helper: Nicolas; WI: N/A, session lenght 1h00
• Description:
  1. Collect requirements from NRENs about their requirement on inter-action with the Service Desk. The information will be used when defining the SD structure and communication mechanism (15 min).
  2. Create incidents classification - Collect different type of incidents that can happen on software - Brainstorm (20 min - need sysadmin and NOCs).
  3. Collect Service Support tool specifications - Brainstorm. The objective is to create a list of features required by Service Supoprt tools.
• Attendance:
  • Expected: NOC operators/ service deployers [Chris Welti, Jon Kare Hellan, Alessandro Inzirelli, Avgust Jauk], System Admin [Looking for people with sys admin background who could help here], Danijel.
  • Confirmed: Nicolas, Jerome, Fred
  • Apologized:

Paper about perfSONAR release management process (QuaTIC conference)

• Session helper: Andreas; WI: 15, session length: 1h00
• Description:
  • Discuss potential submission of a paper to the QuaTIC conference
  • Agree on structure of paper
  • Distribute work
• Attendance:
  • Expected: Andreas, Luis, Nicolas, Loukik, Michalis
  • Confirmed: Luis, Andreas
  • Apologized:

Testing experiences and plans

• • Topic lead: Michalis (main) and Ilias
  • Topic discussion period: 45 minutes
  • Description: Testing experiences and plans
    • What have we done so far?
      • Functional testing
      • Installation testing
      • Document verification
      • Use of documents
      • Conf. calls
    • What have we learnt?
      • Time and Resources needed for testing a service functionality, Priorities, people for the testing team
      • Documentation - advantages, disadvantages
      • Timing issues
      • Reporting findings from a test
    • Next steps
      • New tools (SOAPUI)
      • Procedures
      • Performance Testing
      • Testing analysis/visualization tools
      • Documentation
      • Resource estimates
      • Potential Testing teams
      • Timing related issues (when should testing begin, etc)
• Session helper: Loukik
• Attendance
  • Expected: Luis, Loukik, Michalis, Ilias, Szymon, Roman, Maciej, Stijn M., Stijn V., Verena, Jochen, Guilherme, Uros, Gijs, Andreas, David
  • Confirmed: Andreas, David, Stijn M, Luis., Maciej, Jochen, Ilias
  • Apologized: Szymon, Roman, Verena

Release Management - Micro release and bundle

• • topic lead: Luis Marta (main), Loukik
  • topic discussion period: 45 minutes
  • Description
    • What have we done so far?
      • Hand over procedure
      • Micro-release Definition
      • Bundle installer and service installers
      • Documentation
      • Testing
      • Bug reporting
      • SVN trunk, branches, tags and structure, tar repository
      • Conf. calls
    • What have we learnt?
      • Need for better specifications of releases
      • Need for similarity in installation procedure
      • Documentation needs
    • Next steps
      • Release specification document, Release strategy
      • Release management for analysis/visualization tools
      • Bundle Installer and service installers
      • Jar repository, Tar repository, licensing
• Attendance
  • Expected: Luis, Loukik, Michalis, Ilias, Szymon, Roman, Maciej, Stijn M., Stijn V., Verena, Jochen, Guilherme, Uros, Gijs, Andreas
  • Confirmed: Andreas, Stijn, Luis, Maciej, Jochen, Ilias, Fred
  • Apologized: Szymon, Roman, Verena

Documentation

• • This session was merged with the session on release management
  • topic lead:
  • topic discussion period:
  • Description
    • Documentation process so far
      • documents from developers - content/structure, authors, timelines, format, verification process
      • documents from release mgmt
      • location of documents
    • What have we learnt?
      • document format and location improvements
      • resource requirements
    • Next steps
      • List of documents from developers - indicates content/structure, timelines, format, verification process, document updating process
      • List of documents from release management team
      • List of documents from testing team
      • Indication of resources required to do documentation
      • Verifying these documents
      • Where and how will these documents be stored?
      • What formats will be used (pdf, word, text, etc)
• Attendance
  • Expected: Luis, Loukik, Michalis, Ilias, Szymon, Roman, Maciej, Stijn M., Stijn V., Verena, Jochen, Guilherme, Uros, Gijs, Andreas, David
  • Confirmed: Andreas, David, Luis, Maciej, Jochen, Ilias
  • Apologized: Szymon, Roman, Verena

Minutes

• Minutes and presentations for WI-15 session are available here

Session Proposal Template

• Session helper: xxx; WI: xxx, session lenght: xxx
• Description:
• Attendance:
  • Expected:
  • Confirmed:
  • Apologized:

Actions from the last meeting ISS session

• Action (all): Major number of service version will indicate protocol change. NUmbering of individual services can be different from bundle number - ACCEPTED
• Action (all): psBase is a set of classes which can be used by developers. psBase versioning will also take place using the same schema as individual services. - ACCEPTED
• Action (LK): To find a person who will take care of psBase versioning - ONGOING - NS is involved in this
• Action (all): Use the following naming scheme for projects: - ACCEPTED
• Action (JB): Create mailing list for the Steering Committee - NOT NECESSARY. PUT INFO IN WIKI
• Action (all): Keep functional and interface specifications separate - DONE
• Action (all): Continue with RNC file included for the current release but review it later on - DONE
• Action (MS): Evaluate tools for creating application documentation like docbook. Send example of tools to the mailing list.
• Action (MG): Produce tar file for LS in order to start installation testing - DONE
• Action (LK): Define what should be in which step of installation (in Wiki) - LATER - AFTER 2.0
• Action (ST): Investigate how SVN structure can be used for docs and how to move from Wiki to SVN as well as what to remove (end of January)
• Action (all): Wait for users' feedback on current installation scripts and then decide - ONGOING
• Action (LK): Work on a simple how-tos/FAQ on a Web page - DONE - SHOULD BE UPGRADED CONSTANTLY
• Action (all): Evaluate perl/ant installation scripts in order to choose perl or ant scripts for future - ONGOING
• Action (all): RC tags should be kept over release but removed afterwards apart from leaving the last one and possibly renaming it instead of "RCx"
• Action (all): When bug fix is done this particular tag should be copied to branches directory
• Action (all): We should maintain a particular version of dependencies across all services
• Action (all): jar files should not be collected in one place on SVN. Just use URLs. Developers should use reliable project dependencies
• Action (all): tar files for release bundles can be place on SVN in Downloads directory
• Action (JB): To send proposal to the mailing list for accepting about using fully qualified names defined by NMWG for eventTypes - DONE
• Action (MS): To send to the mailing list information about a new group in OGF