What's new in g-Eclipse

• g-Eclipse 1.0 RC3
  • MyProxy support has been added, allowing to fetch plain Globus or VOMS proxies from a MyProxy server.
  • Bigger updates in Benchmarking and Traceview functionality.
  • ... and several bug fixes
• g-Eclipse 1.0 RC2
  • Restructured and improved user documentation
  • Updated API documentation
  • ... and, of course, many bug fixes
• g-Eclipse 1.0 RC1
  • A framework for handling Service Level Agreements (SLAs) has been added, with initial support for NextGrid SLAs
  • Improved documentation
  • ... and, as usual, a lot of bug fixes
• g-Eclipse 1.0 RC0
  • The CA certificates handling has been replaced by a new Trusted Certificates functionality, which unifies the handling of trusted certificates among different middlewares
  • g-Eclipse now allows visualisation of SRS3D files, besides the already available VTK rendering
  • SFTP is now supported as a native Eclipse filesystem implementation, allowing to transparently transfer files between SFTP locations and Grid storage services like GridFTP, Amazon's S3, etc.
  • Memory usage was optimised to allow better scalability with high numbers of submitted jobs
  • ... and many bug fixes
• g-Eclipse 1.0 M10
  • g-Eclipse has now data-transfer resuming functionality, detecting and restarting incomplete file transfers
  • GridFTP now supports third-party transfers, copying files directly between the source and destination hosts if these are different from the local machine.
  • Support for gLite CREAM Computing Elements
  • Support is now added for benchmarks. Benchmarks are created and run as operator's jobs, and their results can be browsed using the new Benchmark View. Currently only one benchmark is provided (flops) but another one shall be implemented soon.
  • The visualisation component underwent a number of changes, allowing some developer-oriented improvements:
    • Developers can add templates for creating custom VTK visualisation pipelines
    • Developers can reuse the g-Eclipse Visualisation View for their own visualisation framework implementation that is not tied to VTK
  • The workflow components have several improvements:
    • The workflow editor can auto-connect output ports to input ports based on the data-staging URI, via a new context menu action, 'Calculate Job Dependencies' (shortcut 'ctrl-D')
    • Updating data-staging in a workflow JSDL will update workflow job ports
    • A number of UI enhancements including better error checking and an improved New Workflow wizard
  • ... and of course many bug fixes
• g-Eclipse 1.0 M9
  • This is the first g-Eclipse release based on Ganymede/Eclipse 3.4
  • Initial support for Access Control management, allowing to display the permissions of GRIA data stagers (changing them is not yet enabled)
  • g-Eclipse has now UI support for parametric jobs (parameters sweep in JSDL files). A brand new "Parameters" page is available in the JSDL editor
  • Job submission with inner sweep (nested loops of parametric jobs) for gLite as well as for GRIA was added
  • ... and of course a lot of bug fixes
• g-Eclipse 1.0 M8
  • It is now possible to associate a keystore with a GRIA VO, allowing seamless access to different servers from different projects
  • It is now possible to associate an access ID with an AmazonWS VO, allowing the use of different accounts at the same time
  • One may choose any kind of file accessible by g-Eclipse as a source in the jsdl for GRIA jobs: local files, GRIA data stagers, gridFTP, SRM, LFC, etc.
  • The workflow component in g-Eclipse has a number of improvements:
    • Each Workflow is now stored in a dedicated folder which holds the .workflow file as well as the JSDL files corresponding to each Workflow Job (Note: the .workflow extension is still explicitly required when creating the workflow)
    • To associate a Workflow Job with a JSDL file, one can either select the action via a right-click context menu on the Workflow Job or simply drag and drop a JSDL file from the Grid Projects View onto the Workflow Job in question
    • The JSDL file associated with any Workflow Job can be opened and edited in the JSDL Editor via the Workflow Job context menu, directly from the graphical workflow editor
  • The trace view was added, allowing to analyse communication traces of MPI programs. Currently it supports:
    • Reading traces in the NOPE trace file format
    • Displaying traces in a lamport and in a physical clock view
    • Setting breakpoints in traces and using them for debugging in MPI programs
    • Displaying simple trace statistics
  • ... and, as always, a lot of bug fixes!
• g-Eclipse 1.0 M7
  • First implementation of parametric jobs (sweep extension of jsdl): it is possible to submit such parametric jobs both to gLite and GRIA
  • GRIA data stagers are now represented as files
  • It is possible to open Output Data Stagers for GRIA jobs
  • As source for the input stager in GRIA jobs a GRIA stager can now also be specified
  • Online help now also contains Concepts from the middleware's point of view
  • ... and of course a lot of bug fixes
• g-Eclipse 1.0 M6
  • First implementation of LFC filesystem is ready. Both reading and writing is possible
  • It is possible to query gLite Logging&Bookkeping information from the Job Details view
  • Improved Job Submission process: now you need less clicks to submit a job
  • Field Jsdl in Job Details view for GRIA job is opened in jsdl editor
  • It is possible to specify port in Certificate test
  • Two resource simple tests, ping and dns lookup, are implemented
  • ... and of course a lot of bug fixes
• g-Eclipse 1.0 M5
  • Possibility to choose the job name and target folder when submitting a job
  • Deleting a job from the local workspace gives the user the possibility of also removing it from the Grid
  • GRIA job submission can now deal directly with local input files
  • Job Details view shows now GRIA specific information
  • Improved GRIA Site Administrator editor
  • Test framework for grid resources with two implemented tests: certificate lifetime and gLite version
  • New GUI for the Batch System editor
  • ... and of course a lot of bug fixes
• g-Eclipse 1.0 M4 This release is thought to be a maintenance release containing mainly quality work.
  • Already submitted jobs can now be resubmitted in case of failure
  • UI enhancements and improvements
  • Code cleanup
  • User documentation improvements
  • Cheatsheets fixed and improved
  • ... and of course a lot of bug fixes
• g-Eclipse 1.0 M3
  • First support for Amazon's S3
  • All components use now the new problem reporting mechanism, allowing a very user-friendly problem notification and solving
  • ... and of course a lot of bug fixes
• g-Eclipse 1.0 M2
  • First support for the GRIA middleware
  • New import functionality for VOMS VOs
  • ... and of course a lot of bug fixes
• Previously available features
  • Create a job description using a simple wizard or the JSDL editor
  • Submit your job to a gLite resource from the Eclipse workbench
  • Create connections from your local machine to remote storage resources on the Grid and copy files between them
  • Easily manage your authentication tokens in the corresponding view
  • View your available Grid resources reported by the information system
  • Access your remote Grid resources from within the Eclipse workbench in a Shell-like way
  • ... and much more