perfsonar development work

[Szymon Trocha <>]

I will put it on Wiki too.
Sz.

Monday
1. RNP development status update (Leonibo) - 50min
2. SLAC plans and first experience with perfSONAR (Yee) - 20 min
3. Dissemination Workshops (1h30)
        - Jerome from the meet the NRENs (10 min)
        - Loukik or Roman (remotely) on the SEEREN2 one (10 min)
        - Loukik or Nicolas on the L2 status workshop (10 min)
        - Eric or Jeff on their past training for OWAMP and BWCTL (10 min)
        - draw conclusion from them and find out ways of improving them (15
min)
        - start from there and decide on a strategy for the next ones (20 min)
        - set-up a rough workplan for the next tutorials and build set of
slides re-usable by other NRENs?  (15 min)
4. misc Schema developments including:
	- Location: How and were should we indicate geographic location for 
interfaces in the RRDMA, topology service, and L2 Status
	- Units for RRDMA  (Bps vs bps vs errors per minute etc.). When will it 
be implemented? Is it mandatory, etc.
5. Relationship of the L2 Status tool with the perfSONAR core.
        - from a publicity & education perspective
	- It is one of the first pieces of perfSONAR that is being deployed in 
a multi-domain production environment.
        - How is it supported?
6. How can we move the L2 status monitoring tool forward so that it uses 
a schema that allows cross referencing it's components with utilization 
information from the RRDMA and topology info from the Topology service?
7. Which formal perfSONAR release (if any) will support the L2 Status 
tool, or the SQLMA implementation of the L2 Status?

Tuesday:
1. Performance tests (update from MG) Extend them to other services?
Input from Nina based on their experience)  - 1h00
2. Junit tests - review of work done - 30 min
3. Functional tests (MM)
4. Introduce and discuss www.perfsonar.net (NS, LK)
5. Finalize license discussion
6. LHC, GLIF - cooperation with other projects
7. perfSONAR Extension Process: How do we review extensions by non-core
developers before allowing them to use the perfSONAR name.  Do we want
to have any standards or process, or can anybody use the perfSONAR name?
8. Multiple service on a single tomcat instance and ANT (LK) - 30min
9. AA call (// session lead by MM) - 1h30 (16:00)
10. multi-LS update (JZ  - video conferencing) - 30min (17:30)

Wednesday:
1. summary and classification of the questions/issues encountered by the
users when installing the services + conclusion drew from the first pS
release. (ST) - 30 min
2. release management (Luis) - 2h (?)
        - First release and lessons learned (15min)
        - Summary of questions encountered (15min)
        - Bug status report (15 min)
        - How to improve the installation scripts (30 -45 min)
        - What in the next release and which candidates? (1h)
        - Timeline for next release (1h)
4. Installation process improvements (all developers) - 2h30
5. Topology service (Ulisses) - 2h
6. cNIS update (AH) - 30 (?)

--
Szymon Trocha

Poznan Supercomputing & Ntw. Center ::: NETWORK OPERATION CENTER
Tel. (+48 61) 8582022
http://noc.man.poznan.pl  ::: http://noc.pionier.gov.pl