Commit bab33b6d authored by 's avatar
Browse files

Minor updates in documentation and database format


git-svn-id: file:///home/svn/mapi/trunk@343 8d5bb341-7cf1-0310-8cf6-ba355fef3186
parent 4722d70d
- abw application can be used for:
abw application:
1) one flow only, with all parameters specified by command-line
arguments (this is primarily for testing)
- abw obtains number of packets and bytes per-flow (specified by header
filtering, sampling and payload searching), per-protocol, per-interval.
2) multiple flows, with all parameters specified in a configuration
file given by command-line argument -f
- by protocol we mean real protocols such as TCP, UDP or IPv6, or all
when the real protocol does not matter or pseudoprotocols such as
multicast
- abw starts measurement for specified flows and produces results on
stdout and stores them to MySQL database
- these numbers of packets and bytes should be stored as raw results
- type "abw -h" to print all possible command-line arguments
- Examples of use:
Further processing can compute:
- used bandwidth, available bandwidth and utilization percentage
- aggregates for multiple protocols
- aggregates for multiple flows
abw
processes all packets captured by eth0 and produces results each 1 second
the above velues can be always computed on the fly for presentation,
they does not need to be stored in database
abw -d eth0 -m d -r 1 -i 1 -s 01.01.1970-00:00:00 -e 31.12.2099-23:59:59 \
-l 1000
the same as previous default command, but with all parameters specified
- statistics such as average, minimum, maximum, standard deviation,
etc. for various longer periods
abw -d /dev/dag0 -m p -r 0.2 -i 0.1 ip src net 192.168.0.0/16
processes packets originated in subnet 192.168.0.0/16 captured by
/dev/dag0, sampled with probability 0.2 and produces results each
0.1 second
abw -f abw.cfg
processes packets as specified in configuration file abw.cfg
- Measurement Point (MP) of perfsSONAR takes measurement specification in XML,
translates it to configuration file abw.cfg and (re-starts) abw
- abw uses MAPI to open the required number of flows, applies monitoring
functions on them and reads results
(- One flow specified in abw configuration can result in multiple flows in
MAPI, such as separate flows for TCP, UDP, etc. )
- abw produces measurement results on its standard output (stdout)
- The results can be stored in local database (RRD, MySQL) by an external
script or translated by MP back to XML and passed to other components of
perfSONAR.
- abw produces results per-characteristics, per-interval. External processing
can compute:
- average, minimum, maximum, standard deviation, etc. for various
longer periods
- aggregates for multiple characteristics (e.g., all protocols together)
- aggregates for multiple flows
should be computed and stored in database when aggregating
to a longer period and deleting data for shorter period
Design decisions:
- in active monitoring, requests to MP (Measurement Point) can be requests
- in active monitoring, requests to MP (Measurement Point) can request
to perform measurements (send probes) and return results
- in passive monitoring, we assume long-term (possibly continuous) packet
processing, which should run independently and requests to MP should
just return previously obtained results
- therefore MP must somehow internally store measured characteristics,
it can be in plain text files or in SQL database, in any way old data
should be aggregated
- therefore MP must internally store measured characteristics, it can be
in plain text files or in SQL database, in any way old data should be
aggregated
- measurement configuration should be conveniently editable through web-based
interface, for this purpose, it is most convenient to store this configuration
......@@ -90,7 +63,7 @@ Design decisions:
- processing measurement configuration
- doing measurements and storing raw results
- aggregating results
- computing and aggregating results
- retrieving results
- Interaction of components:
......@@ -184,6 +157,18 @@ Interface with perfSONAR and Stager:
When using Stager abw_aggregate is not necessary and can be provided by
Stager aggregate.pl script.
- ABW Measurement Point (MP) of perfSONAR takes measurement specification
in XML, translates it to measurement configuration file abw.cfg for
abw_print and starts abw_print
- abw_print reads results from MySQL database and prints them to stdout
- ABW MP takes results from textual form and translates them back to XML
- abw_measure is configured outside of ABW MP, but in future we can add
XML messages to ABW MP to edit measurement configuration and restart
abw_measure
Measurement configuration file (usually abw.cfg):
It is used for two purposes:
......
......@@ -42,7 +42,8 @@ CREATE TABLE tValue (
parameters_id int NOT NULL,
timestamp_sec int,
timestamp_usec int,
characteristics varchar(32),
characteristics varchar(16),
protocol varchar(16),
unit varchar(16),
statistics varchar(16),
value_int int,
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment