Releases and documentation

On this page you can find the most important improvements for each release. By selecting a release you can find the release notes, download links and manuals for all of our releases. Because every release has its own documents, please click on the 'read more' under the release you are looking for to access its documentation.

To get more comfortable with how to read the documents see our documentation how-to.

For a better understanding on version changes see our versioning policy.

gUSE 3.6.4

Released on 22 May 2014.

The main improvements in this version:

The main improvements in version 3.6.4 is to support the job submission by the SHIWA Submission Service. The web service based SHIWA Submission Service replaces the old GT4-based GEMLCA Service and enables execution of workflows based on different workflow engines. Therefore you can use in WS-PGRADE various workflows from various communities developed in various engines. All of these workflows are stored in the central workflow repository (called SHIWA Workflow Repository). Workflows have been stored in the SHIWA Workflow Repository can be explored by several ways: for example the WS-PGRADE offers for workflow browsing a runtime built-in look up tool, the SHIWA Explorer. (You find related user-level documentation in chapter 8 within Main part, in chapter 23 within the Menu-Oriented Online Help of Portal User Manual, administrative information in chapter 2.10 of DCI Bridge Manual as well as in chapter VIII of Admin Manual.)

Minor changes, bug fixes and fulfilled feature requests:

  • From this release the DCI Bridge handles HTTPS-based inputs and outputs beside HTTP-based I/O. (You can read about the Additional Settings in case of Not Trusted Certification in chapter IX within Admin Manual.)
  • From this version the CloudBroker entities (exactly: the wrapper applications that run executables) are identified by ID instead of names. This change affects the CloudBroker-based middleware setting in case of applying own wrapper.
  • Additional minor bug fixes are in CloudBroker portlet development, in error log handling (SourceForge bug report: #218) and in Data Avenue portlet development, in download function.
  • Solving the next problem: Callback functionality marks successful jobs as error jobs (SourceForge bug report: #222)
  • Improved Install Wizard tool: fixes a number of class loading issues, enables using already available databases for the deployment.

gUSE 3.6.3.1

Released on 18 March 2014.

The gUSE 3.6.3_Patch1 fixes the following bug (SourceForge bug report #216) related to the Information/Resources menu: The created HTML IFRAME element uses the internal component URL instead of the Public Component URL. The result: the WS-PGRADE Information/Resources configuration window is not visible if the portal is used outside of the local network of the portal server.

Therefore, from gUSE version 3.6.3_Patch1 introduces the next minor improvement: the "Public URL of Component" property will be always the used URL which can be set in the WS-PGRADE „Settings/Internal services” menu of „submitter” as „Component type”. If the „Public URL of Component” is not set in WS-PGRADE for submitter component, then the „URL of Component” property will be the default used URL. By this development the Information/Resources window will be visible with corresponding content when you select it.

The necessary upgrading process from v3.6.3 to v3.6.3_Patch1 is described in the Upgrade Manual 3.6.3_Patch1.

Note: Certainly, this upgrade is unnecessary to WS-PGRADE portals where the mentioned error at Information/Resources is not occurred.

gUSE 3.6.3

Released on 4 March 2014.

The release 3.6.3 of gUSE contains three main changes, first of all, there are more improvements in the file commander called Data Avenue (first released in version 3.6.0):

  • Capability of automated user ticket generation to use Data Avenue within portals
  • Admin ticket request form (see details about admin ticket request in chapter VII within the Admin Manual)
  • Support for S3 protocol
  • Changes in Favourite settings as well as minor changes in design
  • Improved file upload
  • Changes in backend (in Data Avenue blacktop service):
    • Security improvements: in-memory credentials, alias credentials are now encoded and deleted on expiration
    • Use of JSAGA version 1.0.0
    • Interface naming made conform to OGSA-DMI
    • Improved logging
    • Bug fixes

More about Data Avenue you find in chapter 21 within Menu-Oriented Online Help of Portal User Manual as well as in chapter VII of Admin Manual.

The two other developments come from the gUSE community (from Ruđer Bošković Institute, Zagreb and from Eberhard Karls University, Tübingen): the supported cluster set enriched by the development of submitters to SGE (Sun Grid Engine) and MOAB clusters. The configuration and operation of both submitters is very similar to PBS and LSF. (Details: Portal User Manual chapter 6.2.20 and chapter Public Key; DCI Bridge Manual chapter 2.7 and 2.19.)

There is a change in logging mechanism of gUSE as well: from this version the logging is possible with Apache log4j. By the application of log4j is the debugging and troubleshooting of gUSE components will be easier by the developers and administrators. (See details in chapter Logging with log4j within the Additional Enhancement of Admin manual.

Additionally, this release also includes a bug fix, solving the problem with the UNICORE jobs - these jobs did not work with XtreemFS remote ports earlier (SourceForge bug report: #211).

gUSE 3.6.2

Released on 31 January 2014.

The main improvement in this version is the solution of direct cloud access by the new cloud plugin. By this feature the user can easily submit jobs directly to an accessible cloud. This direct cloud access solution doesn’t need any third party brokering for job submission. Any clouds that implements the Amazon EC2 interface will be accessible by this DCI plugin. The user just needs a valid authentication to the selected cloud resource provider. (See details in Chapter 18 within the Menu-Oriented Online Help as well as in chapter 6. of the Portal User Manual) However additional installation steps must be taken by the administrator of the gUSE/WS-PGRADE for providing the direct cloud access. (You find details about these tasks and additional considerations in chapter VI of Admin Manual and in chapter 2.18 of DCI Bridge Manual.)

Another relevant novelty is the option for the “remote” definition of job executables within the workflows. This new feature of WS-PGRADE job configuration enables users to define job executables by references in such cases where earlier only the uploading of local files of executables was the single option. Additionally, the set of the supported protocols to define remote sources of inputs has been extended as well. (See details in chapter 14.)

An additional minor change: the unnecessary temporary files will be automatically deleted from directories of WS-PGRADE and WFI components after saving workflow configuration as well as after workflow submission.

Further bug fixes:

  • Solving the job saving problem in case of CloudBroker (SourceForge bug report: #121)
  • Adding missing messages in case of CloudBroker (SourceForge bug report: #123)
  • Solving the lost arguments problem in case of CloudBroker job configuration (SourceForge bug report: #134)
  • Bug fixing by the UNICORE gUSE community: it solves the problem of UNICORE submitter that generates incorrect number of cores (SourceForge bug report: #192)

gUSE 3.6.1

Released on 7 November 2013.

The main improvement in gUSE v3.6.1 is the solution for debugging of job submissions by applying breakpoints in WS-PGRADE workflows. By this tool the users can interact with workflows at runtime: they can directly influence and change workflow’s submission processes and results by enabling or prohibiting the progress of job instances at breakpoints (for more details see chapter 13).

From this version the Graph Editor can be used with the latest Java upgrade (Java 1.7.0_45) as well.

Additionally, a minor change in this version is a bug fixing (related bug report on SourceForge: #184): The (jobtype=single) will be set in GT5 RSL, when the property "Kind of binary:" is configured to "Sequential".

gUSE 3.6.0

Released on 9 October 2013.

The main change in this version is a developed tool called Data Avenue that integrated the function of Data Avenue core service (called Data Avenue Blacktop) as a new portlet into WS-PGRADE portal. Data Avenue is a useful file commander for data transfer, enabling easy data moving between various storages services (such as grid, cloud, cluster, supercomputers) by various protocols (HTTP, HTTPS, SFTP, GSFTP, SRM). The using of Data Avenue is similar to other well-known file commanders (e.g. Total Commander or Midnight Commander): you can use a simple two-panel (source and destination) form to copy, delete, download, upload etc. (for more details see chapter 20 within Menu-Oriented Online Help in Portal User Manual).

And one more new development: the overall billing and pricing information menu (CloudBroker Billing) in WS-PGRADE to support the CloudBroker-specific (pay-per-use) job submission (for more details see chapter 17.2 within Menu-Oriented Online Help in Portal User Manual).

gUSE 3.5.8

Released on 24 July 2013.

The major improvement in version 3.5.8 is the internal system performance optimization for job execution. This internal reorganization of exchanging information between WS-PGRADE and the various gUSE components significantly increases the performance of WS-PGRADE portal. The changes mainly concern the background processes, only two minor visual changes appears on portal user interface: in Workflow/Concrete/Details function and in Storage function (the updated description of this two parts of the portal you can see in chapter 3.1 and 5 within section Menu-Oriented Online Help).

Other changes:

  • The administrative configuration of Remote API is easier than earlier: you can set it in the WS-PGRADE portal. (See the details about the Remote API configuration and usage in RemoteAPI_Install_Manual.pdf and in RemoteAPI_Usage.pdf. You can also find some examples for using Remote API in the RemoteAPI_Usage_Examples.zip in the Documentation folder.)
  • The maximum quota size belonging to a portal user for workflow is increased to 10000 MB (the earlier limit was 5000 MB). About the quota setting see chapter The Internal Services in the Administrator Manual.
  • In the new version (v3.4.5) of ASM new features were implemented (getting/setting resource of a job; getting/setting number of input files uploaded as paramInputs.zip; setting remote output path for a given output port; getting content of an input file). The ASM v3.4.5 is compatible with gUSE from version 3.5.8, and not compatible with older versions. (For upgrading from v3.4.4 to v3.4.5 see the Portal_Upgrade_Manual_v3.5.8.pdf. You can find more details about ASM usage in the ASM_Developer_Guide_v3.4.5.pdf.)

gUSE 3.5.7

Released on 31st May 2013.

The main change in gUSE/WS-PGRADE version 3.5.7 is the fast statistical data processing and providing mechanism in Statistics function that loads the gUSE database at lower level than earlier and exploits the resources more effectively than in the previous gUSE versions (see chapter 11 in Portal User Manual to read more about Collection and Visualization of Usage Statistics).

gUSE 3.5.6

Released on 17th May 2013.

The main improvement in version 3.5.6 is the development in WS-PGRADE workflow export/import to/from Remote SHIWA Repository. From this version you can share your workflow to SHIWA project community in WS-PGRADE format and in SHIWA IWIR format as well (the latter solution is useful if you want to use your workflow by other workflow management systems than WS-PGRADE. However, for successful sharing, before in IWIR format export – unlike in WS-PGRADE format - your workflow can fit some rigorous preliminary conditions. For details see chapter 11 in Menu-Oriented Online Help.). Therefore the shared workflows can be imported from remote repository to WS-PGRADE portal environment in well-known WS-PGRADE implementation format or in IWIR format. (For details see chapter 7 and 11 in Menu-Oriented Online Help.)

Pages

Subscribe to RSS - Releases and documentation