Link to savannah patch:

 patch #3040: WMS UI 3.3 Release

Release Notes:

  • New Features:

    In the gLite WMS UI 3.2 all the commands glite-wms-job-* are now fully compliant with IPv6 technology, not breaking any backward compatibility of IPv4. This applies to WMProxy APIs Python, C++, Java as well.

    • JSDL Support within WMS

    The JSDL (Job Submission Description Language) job description file is now allowed for Job Submission within the WMS. The current support is restricted to simple jobs, and counting to add bulk submission in the next future, availability depends on JSDL specifications provided by OGF JSDL WG:

    • Delegation v 2.0

    The gLite WMS UI 3.2 now supports the Gridsite Delegation 2.0.0 new methods:

    • getNewProxyReq
    • renewProxyReq
    • destroy
    • getTerminationTime
    • getInterfaceVersion
    • getServiceMetadata
    • getProxy (already present in 1.0.0)
    • putProxy (already present in 1.0.0)

    For more informations please check the following links:

    • JSON Format output

    The following commands have now a new option --json which prints the output following JSON format specifications:

    • glite-wms-job-submit
    • glite-wms-job-output
    • glite-wms-job-cancel

    Please note that this new option does not work with --nomsg and --debug.

    • DNS Load Balance

    The WMS UI 3.2 is now able to resolve an hostname given in input from configuration file, option --endpoint or environment variable, from a DNS, Alias or IP address. This allows the DNS to balance the computing load of its WMS machine, returning the best WMS available behind it. No other operations are required to the WMS UI, being the metric problems handled by the DNS on WMProxy Server side.

    • Failover mechanism integration

    Missing failover mechanism has been added for the command:

    • glite-wms-job-list-match

    • Configuration file

    The WMS UI configuration file has been merged in a unique filename:

    • glite_wmsui.conf

    For further informations on configuration attributes and configuration file priority please check paragraph 3 and 4 at the following link:

    • JDL Grammar Checker

    In the JDL 3.2 released with the WMS UI 3.3 a new JDL grammar checker has been introduced. The checker will throw an exception to the WMS UI if the JDL is not well formed, giving the line number of the JDL where the syntax error occurs, and the error itself.

  • Bug fixes:

    • bug #17534: unexpected behavior of glite-wms-job-output
    • bug #27148: [condor-support #2036] glite-job-list-match segmentation fault on bad JDL requirements
    • bug #29635: bad error message for glite_wms.conf syntax error
    • bug #34949: Ctl-C'ed submission gives funny state
    • bug #39890: IPv6 bug: name resolving by WMclients broken under IPv6 (glite-wms-job-list-match broken by IPv6)
    • bug #41294: IPv6 bug: non compliant name resolving function in source code (gethostbyname_ex)
    • bug #41295: IPv6 bug: non compliant networking function (gethostbyaddr)
    • bug #41310: [WMS] IPv6 bug: non compliant name resolving function in source code (gethostbyname)
    • bug #41322: [WMS] IPv6 bug: non compliant address family type in source code (AF_INET)
    • bug #41324: [WMS] IPv6 bug: various non compliant functions/data structures in the wmproxy_api.cpp file
    • bug #43601: glite-wms-job-submit silently adds VO defaults to user configuration
    • bug #47134: WMS UI: glite-wms-job-{delegate-proxy,submit} fail if HOME is not set
    • bug #47677: WMS job submission aborts on non-existent endpoint
    • bug #48598: job submission fails when first WMS tried is draining !!
    • bug #48702: job-list-match fails when first WMS tried is draining
    • bug #48806: [glite-wms-job-status] glite-wms-job-status gives an error on SLC5
    • bug #50289: glite-wms-job-output
    • bug #51292: glite-wms-job-status does not load default configuration file
    • bug #51293: glite-wms-job-status does not load LBAddresses attribute
    • bug #51294: glite-wms-job-submit: ExpiryTime wrong type
    • bug #51295: glite-wms-job-output: fails creating the output directory if not present
    • bug #51296: glite-wms-job-info: does not recognize if a job is simple or DAG/Collection

What is Grid

The Grid is an emerging infrastructure that will fundamentally change the way we think about - and use - computing. The basic idea is very simple, since it is about harnessing unused resources through the Internet, or a corporate Intranet, to solve major computational problems that require far more computing power and data storage than that available at any single location

EGEE Project

The Enabling Grids for E-sciencE (EGEE) project is funded by the European Commission and aims to build on recent advances in grid technology and develop a service grid infrastructure


EGEE Home Page