perfsonar development work

[Nicolas Simar <>]

Hi Michalis,

I am sending you a basic perfSONAR information welcome pack. You are the 
first developer to join the project since the beginning, so this list 
may not be complete. If you feel that something is missing, please let 
us know, so we can complete this pack.

1. Communicating

PerfSONAR/JRA1 has several site of information:

1.0. The public facing web-site
www.perfsonar.net

1.1. perfSONAR wiki

http://www.perfsonar.net/jra1-wiki/index.php/Main_Page which is divided 
into two parts:

- the JRA1 one  http://www.perfsonar.net/jra1-wiki/index.php/JRA1_Main

- the general perfSONAR one, currently a little bit of a shamble 
http://wiki.perfsonar.net/jra1-wiki/index.php/PerfSONAR_About . We will 
soon have a static site with the information oriented towards the users.


1.2. JRA1 intranet

http://intranet.geant2.net/server/show/nav.698, for which you need an 
account (GN2 account for the GEANT2 project participants). Please 
contact the GEANT2 webmaster ()if you got a 
question about this account.


1.3. Mailing lists and mailing lists archives

There are several mailing lists for which you can find a description at 
http://monstera.man.poznan.pl/jra1-wiki/index.php/JRA1_Contacts.
The mailing list to which you should subscribes are the
-  (as GEANT2-JRA1 member, general discussions and 
information about JRA1)
- 

 where the perfSONAR services developers are

1.4. Information about meetings and conf call can be found at
http://www.perfsonar.net/jra1-wiki/index.php/PerfSONAR_Events

1.5. Most of us are using IM (yahoo or msn accounts) and skype.
http://www.perfsonar.net/jra1-wiki/index.php/PerfSONAR_Contacts

1.6. The JRA1 communication tools are summarise at 
http://intranet.geant2.net/server/show/conWebDoc.1055 (including phone 
number, H.323 dedicated numbers).

1.7. Meetings
We got meetings every three months. (1..5 day with status update session 
and parallel session where people meet in small groups).

2. Working

2.1. The coding guidelines are available at 
http://www.perfsonar.net/jra1-wiki/index.php/Coding_Standards

2.2. You will need to be able to use CVS to start with, and SVN later on 
(as we are intending to migrate towards it).
To get an CVS account, please contact Jeff Boote (Cc-ed). If you got 
questions about the CVS, please send it Jeff Boote or to the 
Prototype-JRA1 mailing list.

2.3. The programming language is Java 1.5

2.4. you can use any Integrated Development Environment (such as 
Eclipse, SUN netbeans)

2.5. In your particular case, you won't have to deal with SOAP, you will 
deal with XML mostly. (So no strong need to learn SOAP, but a overview 
of SOAP is a good thing).

2.6. We are using Junit to automate the test the code done (we have 
recently started to do so).  Panagiotis Louridas <> is 
the person to be contacted to have example and advices on Junit.

2.7. Once a service is about to be released, the specification of its 
interface have to be passed onto the test team which will then perform 
functional tests on them before having the code released.

2.8. To realise what has to do someone who needs to install perfSONAR, 
we strongly encourage you to install an instance of the MA (please check 
with Roman Laplacz which one to use and where to find the relevant 
information).

2.11. You can find the document related to the perfSONAR services at:
http://www.perfsonar.net/jra1-wiki/index.php/PerfSONAR_and_JRA1_Resources#perfSONAR_services_related_documents
http://www.perfsonar.net/jra1-wiki/index.php/Generic_Service_Design_resources


3. How do we work?

3.1. Typically for a new service, we follow the guidelines provided by 
the GFD (General Framework Design) and the development done. A first 
discussion happens to get ideas. Then the a responsible is nominated to 
write a strawman proposal which will be sent to the mailing list (the 
answer can take some times to come back (2-3 weeks).
The strawman is amended, conf call are scheduled when points need to be 
discussed or decision taken.  The strawman consist of two parts: the 
internals of the service itself and the schema updates (to be discussed 
with Martin Swany).
By order of priorities the following functionalities are implemented: 
the basic of the service itself, scripts to ease the installation, 
script to help with the population of the data, the service registration 
to a lookup, the AA, the resource protection.

3.2. Development of the code, includes Junit tests. The code need to be 
deployed once.

3.3. The test team perform some functional tests on the service (upon 
specification and documentation of the interface).

3.4. The release management team verifies if all the documentation is 
provided, if installation scripts are being provided and if the 
documentation is provided:
a) The services specifications: For developers who need to understand 
how to make their applications compliant with Perfsonar. It will include 
message and message formats and high level interfaces and protocols. -> 
In "developers info"
b) User's guide - For people who will install perfsonar. Sysadmins, 
nocs, users. It will include installation, configuration and use of Java 
Services -> "Getting started" and/or "downloads"

3.5. Release

3.6. Bug fixes
Once released, done by SA3 WI-15.

3.7.Additional documentation : Developers guide - For new developers. 
API and it tells how the reference implementation fits together and how 
to extend the Java Reference Implementation -> In "developers info"


Cheers,
--
Nicolas
______________________________________________________________________

Nicolas Simar
Network Engineer

DANTE - www.dante.net

Tel - BE: +32 (0) 4 366 93 49
Tel - UK: +44 (0)1223 371 300
Mobile: +44 (0) 7740 176 883

City House, 126-130 Hills Road
Cambridge CB2 1PQ
UK
_____________________________________________________________________