perfsonar development work

Author: gijs
Date: 2007-01-25 08:18:33 -0500 (Thu, 25 Jan 2007)
New Revision: 1983

Modified:
   trunk/perfsonar/contrib/FlowMP-client/README
   trunk/perfsonar/contrib/FlowMP-manager/README
Log:

improved documentation



Modified: trunk/perfsonar/contrib/FlowMP-client/README
===================================================================
--- trunk/perfsonar/contrib/FlowMP-client/README        2007-01-25 12:58:57 
UTC (rev 1982)
+++ trunk/perfsonar/contrib/FlowMP-client/README        2007-01-25 13:18:33 
UTC (rev 1983)
@@ -1,14 +1,23 @@
 
 flowmp client
 -------------
+This is a simple python client that can connect to a Flow Subscription MP.
 
-requirements:
- * zebedee
+
+requirements
+------------
+ * zebedee (tested with 2.4.1A)
  * python (tested with 2.4)
+ * access to a Flow Subscription MP ;)
 
+
+usage
+-----
 change config.py to your needs and run client.py.
 
-This script is a prove of concept to demonstrate are flow MP for perfsonar.
 
-any comments are welcome: Gijs Molenaar 
<>
+about
+-----
+This code is developed for perfSONAR by SURFnet.  any comments are
+welcome: Gijs Molenaar 
<>
 

Modified: trunk/perfsonar/contrib/FlowMP-manager/README
===================================================================
--- trunk/perfsonar/contrib/FlowMP-manager/README       2007-01-25 12:58:57 
UTC (rev 1982)
+++ trunk/perfsonar/contrib/FlowMP-manager/README       2007-01-25 13:18:33 
UTC (rev 1983)
@@ -1,42 +1,39 @@
 
-To run, you need:
- -python
- -elementtree
- -zebedee
+FlowMP-manager
+--------------
 
+These scripts are part of the Flow Subscription MP. This part of the code 
will manage
+the nfsen and zebedee proceses. It will read XML files writen by the tomcat 
axis part
+of Flow Subscription MP and dump flow data in a zebedee tunnel for every 
client
+described in the XML file.
 
+requirements
+------------
+ * nfsen
+ * python
+ * elementtree
+ * zebedee
 
-* service.properties.flowmp
-config file. Here you need to specify path, routers, ports etc.
-Flow format and transport protocol are currently not used.
 
+usage
+-----
+First set up the Flow Subscription MP axis part. Then edit the config.py 
file and set
+the location to the service.propterties.flowmp file. here are all the 
routers defined
+and also the path to the zebedee binary. Now you can start the manager.
+
 * manager.py
 python script to start all the collectors. For every router in 
service.properties.flowmp a
 collector is started. Logfiles are rotated every minute.
 
 * process.py
 this script is called after a flowfile rotation. It will process the file 
for every
-subscription and replay it to the zebedee port for the client.
+subscription and replay it to the zebedee port for the client. It is not 
meant to
+be called directly from console.
 
 * common.py
-module with shared program  stuff
+module with shared program stuff
 
 * config.py
 module used to parse config. If service.properties.flowmp is not in current 
dir, you have
 to edit "propFile".
 
-
-
-connection story:
-
-inPort: zebedee port at flow MP side where nfreplay should dump flow into 
(11110 + clientID)
-outPort: the port that the subscriber supplied. The port where it wants to 
receive the flows 
-betweenPort: port used by zebedee to setup connection (22220 + ID)
-clientIP: de flow subscriber
-serverIP: de flow subscription service
-
-on flow MP subscription servcie side:
-zebedee -z 0 -u -d -l <inPort>:<clientIP>:<outPort> -T <BetweenPort> -x 
"udptimeout 5"
-
-on flow subscriber side:
-zebedee -z 0 -u -s -d -c <serverIP> -T <betweenPort> -x "udptimeout 5"