Main Menu

Project Life Cycle

perfSONAR 2.2

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.
Skip to end of metadata
Go to start of metadata
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.