GRIA Service Provider Management Release Notes

v5.0.1

This release provides performance improvements, bug fixes and documentation improvements. In particular, service performance has been improved to correctly handle higher rates of usage reporting from application services. Improvements have also been made to the processing and display of usage metrics in web interface for the SLA service. A detailed list of changes is provided below.

• [GRIAS-524] - Out-of-memory after running a few jobs
• [GRIAS-559] - bar charts don't display properly in IE
• [GRIAS-572] - In the SLA details page we should be able to click through to the account page if the services are co-hosted
• [GRIAS-583] - SLA service blows up when adding a constraints xml file
• [GRIAS-618] - The data in some tables in the web-app appear in random order
• [GRIAS-619] - Need more info in the tables that list the SLAs, such as the SLA start time
• [GRIAS-637] - Storing an EPR in a Postgres database does not work
• [GRIAS-642] - Apache documentation still refers to client authentication
• [GRIAS-656] - First event on account statement is wrong
• [GRIAS-659] - logging goes to wrong location
• [GRIAS-663] - The links created for PBAC groups in the Atom feed do not take into account the current name of the web app.
• [GRIAS-664] - Uploading a new capacity file does not properly override the old capacity
• [GRIAS-666] - Upgrade to latest hibernate JAR (3.1.3) and dependencies
• [GRIAS-667] - Closing an SLA with a job activity in it does not clean up the job properly
• [GRIAS-670] - Incorrect link in Configuring Apache 2.0 for Tomcat
• [GRIAS-673] - If the keystore doesn't contain the CA, tomcat HTTPS doesn't work
• [GRIAS-674] - CLONE -Elements in EPRs in database have the wrong namespace
• [GRIAS-675] - ArrayIndexOutOfBoundsException when signing a message
• [GRIAS-677] - try to generate keystore without typing in a keystore password gives a page with stack trace
• [GRIAS-678] - If you try to upload nothing in the capacity or SLA template form then you get a big stavck trace and the error "Unexpected error: Your file is not correct."
• [GRIAS-685] - Default to certificate CN as hostname
• [GRIAS-687] - Minor Fedora 5 documentation issues
• [GRIAS-688] - Data input validation issues when creating self-signed keystore
• [GRIAS-718] - SLA manager incorrectly refuses activities and loses track of usage
• [GRIAS-719] - Adding constraints to SLA manager causes exception

v5.0

Initial Release