PerfSONAR-Bundle-Release-Notes

From GEANT2-JRA1 Wiki

Change log

perfSONAR MDM 3.0

perfSONAR MDM bundle does away with the bundle installer and introduces linux packages (rpms and debs) along with WAR files for Java based applications and an executable for pinger software. The bundle in this release simply represents a collection of software (i.e a folder where software are grouped) and a consistent manual for installation of these software.

RRD Measurement Archive

Version 3.0
Detailed Change logs available here

SQL Measurement Archive

Version 2.0
Detailed change logs available here

SSH Telnet Measurement Point

Version
Detailed change logs available here

BWCTL Measurement Point

Version 0.4
Detailed change logs available here

Lookup Service

Version 1.2
Detailed change logs available here

Authentication Service

First release of Authentication Service
Version 1.0
Detailed change logs available here

Command Line MP

Version
Detailed change logs available here

perfSONAR Buoy

First release of perfSONAR Buoy
Version
Detailed change logs available [here]

PingER MP and MA

First release of PingER MP and MA
Version
Detailed change logs available [here]

perfSONAR 2.2

Bundle installer

- Fixed Bug #219: Undeploy task of perfsonar 2.1 bundle
- Fixed Bug #272: Bad regexp in install.pl

RRD Measurement Archive

Important upgrade information: If you are upgrading from previous version (2.0/2.1) of the bundle installer, the metadata configuration file has to be updated as per the new structure. Please follow the stitching guide for details.

- New: support for two additional characteristics: ifErrors and ifDiscards
- New: new RRD test file to reflect new characteristics
- New: eventType paremeter added to the key
- Change: nmwg namespace for utilization datum element
- Change: defaultly all log messages are collected in one log file
- Change: defaultly debug log level is switched off
- Change: base chanining switched on, propert in service.properties exist to switch it off 
- Change: eventType URL-based only
- Change: service moved to new SVN structure
- Change: ant scripts improved
- Change: namespace of datum elements in SetupDataResponse message tied to eventType value 
- Change: supportedEventType parameter replaced by eventType element in metadata config file (excluding utilization). But service supports both
- Change: use of new versions of base and NMWG libraries
- Change: if 'jar' target is called and const.properties file does not exist then const.properties.template is renamed into const.properties before compilation
- Change: new parameters set in data element in SetupDataResponse message containing general parameters used to create rrd file
- Change: updated support for LookupInfoRequest to include all service properties
- Change: service can generate keys with parameters elements of different namespaces
- Fixed Bug #102: missing data in response
- Fixed Bug #103: missing data in response
- Fixed Bug #150: time interval shifted
- Fixed Bug #157: namespace declaration
- Fixed Bug #195: directories structure

SSH/Telnet MP

- Change: to the parameters of the Ping command for Juniper
- Change: Updated some questions during the stitching process to make the questions more clear
- Fixed Bug #220 a bug which resulted in commands not working due to a fault in the Regular Expressions validation system
- Fixed Bug in the parsing of the CSV file during stitching

2007-10-26: Version 1.2.2
- Fixed Bug - VTY problem with Telnet connection to (mainly) cisco routers

Command Line MP

- New: Internal Resource Protector to limit concurrent threads for each tool.
- New: Support added for fully qualified eventTypes
- Fixed Bug #171 bwctl 'protocol' parameter with invalid value ignored
- Fixed Bug #169 measurements timeout bug
- Fixed Bug #165 unhandled malformed requests
- Fixed Bug #159 scheduled bwctl tests in CL-MP

Versions of bundled products

RRD MA - 2.3.2
CL MP - 1.1
Java SSH-telnet MP - 1.2.2
SQL MA - 1.3
LS - 1.1.1
BWCTL MP - 0.2
E2EMon MP - 1.1

Known Issues

Leading and trailing White spaces (spaces, new lines, tabs) in xml elements contained in requests can sometimes lead to undesirable/incorrect behavior. It is suggested that unnecessary/formatting white spaces SHOULD NOT be introduced either in xml requests or in the xml metadata configuration file
The installer may not clearly mention that tomcat restart is required before the last action it does in deploy step.
Jakarta Tomcat log files (catalina.out) tend to overflow (especially when LS registration is turned on). Re-routing them to /dev/null is suggested
XML-LS pre-installation step requires that eXist database be installed and 'initiated'. This varies from RRD MA and SQL MA services which can automatically do the installation and initiation.
BWCTL MP installer stores the configuration insider the perl files (except pre-install). This is not similar to the Java services
SQL MA could encounter problems due to user privileges. The default installation scripts for SQL tables (lightpath and utilisation) make use of '%'. Sometimes this use of '%' instead of 'localhost' or any specific service name causes the SQL database to not allow the request to continue. This can be handled on the SQL database side by changing the user's privileges to 'localhost' or the dns entry of the machine where the SQL MA is installed.
SQL MA - store functionality does not validate the store request thoroughly. Although proper requests succeed, improper ones could end up being stored as well
The collection names that need to be provided in eXist (XML database) is fixed (see default values in interactive questions section). This means that you won't be able to provide your own names to these collections.

perfSONAR 2.1

New product added - E2EMon MP
Improvements to commands configuration during SSH/Telnet MP installation. Easy-to-use, pre-defined commands now available during installation. You can also create your own pre-defined command set by following the ascii file format.
Enhancements to bundle installer - some dependency checks for ant, environment variables, perl modules and system commands such as wget

SSH/Telnet MP

Changed the way the stitching goes for the SSH/TELNET MP. Users now have the option to provide a service.properties file, a CSV file containing the configuration, or configure the devices manually and choose which commands they wish to be supported for the devices (either from a list, or a preconfigured package of commands).

2007-08-20: Version 1.2
- Changed the stitching procedure
        - CSV file supported
        - users choose the commands instead of providing all information themselves
        - minimum packages of commands supported for several device types

G2_E2EMon_MP

2007-08-20: Version 1.1
- E2EMon MP is capable of providing Web Service based access to status of lightpaths stored in XML file 
- auto-installation is added. perfsonar-bundle approach for installation
- Supports perfSONAR error notifications
- MP is automatically started after installation
- test.pl can be used to test communication with MP

Known Issues

Leading and trailing White spaces (spaces, new lines, tabs) in xml elements contained in requests can sometimes lead to undesirable/incorrect behavior. It is suggested that unnecessary/formatting white spaces SHOULD NOT be introduced either in xml requests or in the xml metadata configuration file
The installer may not clearly mention that tomcat restart is required before the last action it does in deploy step.
Jakarta Tomcat log files (catalina.out) tend to overflow (especially when LS registration is turned on). Re-routing them to /dev/null is suggested
XML-LS pre-installation step requires that eXist database be installed and 'initiated'. This varies from RRD MA and SQL MA services which can automatically do the installation and initiation.
BWCTL MP installer stores the configuration insider the perl files (except pre-install). This is not similar to the Java services
SQL MA could encounter problems due to user privileges. The default installation scripts for SQL tables (lightpath and utilisation) make use of '%'. Sometimes this use of '%' instead of 'localhost' or any specific service name causes the SQL database to not allow the request to continue. This can be handled on the SQL database side by changing the user's privileges to 'localhost' or the dns entry of the machine where the SQL MA is installed.
SQL MA - store functionality does not validate the store request thoroughly. Although proper requests succeed, improper ones could end up being stored as well
The collection names that need to be provided in eXist (XML database) is fixed (see default values in interactive questions section). This means that you won't be able to provide your own names to these collections.

perfSONAR 2.0

New installation concept - each service is a separate product/project.
Light weight bundle
- It only contains the bundle installer
- Bundle installer downloads tar balls of services that the user wishes to install
Multiple Services can be installed on same tomcat
New installer script
- Menu based interactive installation, on-demand download of services
- Improved robustness - 4 steps for installation (pre-install, configure, deploy, test)
- Can work with both Java services and perl services
- Installer is written in perl (requires perl) but to install Java services, it requires Apache Ant
Products: 4 new services, 2 improved services
- New Services: Command Line MP (Java), SSH/Telnet MP (Java), BWCTL MP (Perl), SQL MA (Java)
- Improved Services: RRD MA (Java), Lookup Service (Java)
- Versions of services
  - Command Line MP - 1.1
  - RRD MA - 2.2
  - SQL MA - 1.3
  - BWCTL MP - 0.2
  - Lookup Service - 1.1.1
  - SSH/Telnet MP - 1.1
New features in all Services
- Result codes used extensively - converted most java exceptions returned to client into xml result codes
- Echo functionality on all java services - More like a ping message to the service. Helps in determining status of deployments
- Automatic download and installation of Tomcat (all Java services) and eXist XML database (RRD MA and SQL MA only)
- Lookup Service registrations and keep-alives across all 6 services

Known Issues

Leading and trailing White spaces (spaces, new lines, tabs) in xml elements contained in requests can sometimes lead to undesirable/incorrect behavior. It is suggested that unnecessary/formatting white spaces SHOULD NOT be introduced either in xml requests or in the xml metadata configuration file
The installer may not clearly mention that tomcat restart is required before the last action it does in deploy step.
Jakarta Tomcat log files (catalina.out) tend to overflow (especially when LS registration is turned on). Re-routing them to /dev/null is suggested
XML-LS pre-installation step requires that eXist database be installed and 'initiated'. This varies from RRD MA and SQL MA services which can automatically do the installation and initiation.
BWCTL MP installer stores the configuration insider the perl files (except pre-install). This is not similar to the Java services
SQL MA could encounter problems due to user privileges. The default installation scripts for SQL tables (lightpath and utilisation) make use of '%'. Sometimes this use of '%' instead of 'localhost' or any specific service name causes the SQL database to not allow the request to continue. This can be handled on the SQL database side by changing the user's privileges to 'localhost' or the dns entry of the machine where the SQL MA is installed.
SQL MA - store functionality does not validate the store request thoroughly. Although proper requests succeed, improper ones could end up being stored as well
The collection names in exist is pretty much fixed (see default values in interactive questions section).

RRD Measurement Archive (Java)

2007-03-21 Version 2.0
- New: Lookup Service registration
- New: pre-install, configure, deploy, test steps in installation process
- New: echoRequest functionality
- New: 64-bit Linux support for building the rrdjtool library
- New: result codes
- New: support for mulitple service in one Tomcat instance
- New: removing whitespaces such as newline, tabs, etc that are present in the request messages
- Change: support for new utilization evenType value naming scheme
- Change: log4J configuration in log4j.properties
- Fixed Bug #108: installation process
- Fixed Bug #109: installation process

SQL Measurement Archive

2007-03-22 Version 2.0
- New: support for relational database data storage
- New: Support for utilization and L2 path status
- New: Lookup Service registration
- New: echoRequest functionality
- New: result codes
- New: pre-install, configure, deploy, test steps in installation process
- New: support for new utilization evenType value naming scheme
- New: support for both new (http://ggf.org/ns/nmwg/topology/l2/3.0/link/status) and old (Path.Status) link status evenType value naming scheme
- Fixed Bug #50: More descriptive debug information in log
- Fixed Bug #83: Installation process
- Fixed Bug #127: Installation process
- Fixed Bug #133: Installation process
- Fixed Bug #135: Installation process
- Fixed Bug #154: Error code generated if eventType is missing or its value is unknown

Lookup Service

2007-03-26 XML LS 1.1
- New Message Handler
- Exist HTTP access
- Result codes
- Performance improvements, bugs fixes
- Echo Request (with LS-echo functionality for testing DB connection and configuration)
- LS Cleanup rewritten
- New installation/configuration (ant targets)

SSH/Telnet Measurement Point

2007-03-14: Version 1.0 (first release)
- show-like information exposure
- symbolic command names are used
- transparent naming across devices from multiple-vendors
- multiple devices in one request supported
- regular expressions can be specified for parameter checking
- token-bucket algorithm for limiting the number of request that are allowed
- finegrained configuration of commands possible
- extra information concerning commands can be specified
- minimum/maximum number of parameters can be specified
- caching period of results can be configured
- supports basic Lookup Service registration
- supports Echo-request functionality

2007-05-27: Version 1.1
- minor fixes

Command Line Measurement Point

2007-03-15: Version 1.0 (first release)
- on-demand measurements using command-line tools
- tested extensively in FreeBSD and Linux
- should work in any JAVA compatible OS
- supported tools:
	- ping
	- traceroute
	- OWAMP (3.0b and prior)
	- BWCTL (1.2a and prior)
- configurable resource protection for limiting the number of simultaneous requests allowed for a particular tool	
- supports basic Lookup Service registration
- supports Echo-request functionality

BWCTL Measurement Point

2007-03-15: Version 1.0 (first release)
- allows the user to launch BWCTL measurements using the BWCTL tool
- can handle SetupDataRequests and MetadataKeyRequests
- supports basic Lookup Service registration
- implemented as generic service that can handle different service types in parallel
- new types can easily be added
- other service types available (not thoroughly tested or even expected to work properly): Hades MA, RIPE MA, and OWAMP MP
- implemented like a typical UNIX daemon

perfSONAR 1.0

First Release
Two Java services in one product - RRD MA and Lookup Service
Perl installer
Automatic installation of rrdjtool
RRD MA can register with Lookup Service

Known Issues

Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/PerfSONAR-Bundle-Release-Notes"

Views

Personal tools

Log in

Search

Toolbox