, view all tags

Extended Release Notes for WMS 3.5.0

1) Supported platforms
2) Major changes
3) Known Issues

1) Supported platforms

Scientific Linux 5.x x86_64

Scientific Linux 6.x x86_64

2) Major changes

Enabled Argus-based access control using the glite-CE/WN profile

Integrated EMIR-SERP with existing service configuration and deployment on the server side. The WMS is able to register to an EMIR instance specified by configuration.

Ceased distribution of WMProxy Java API, UI C++ API, UI Java API

Support for StorageAccessProtocols has been added in the GLUE2.0 information provider


Support for glue2 must be enabled in the configuration, through the parameter EnableIsmIiGlue20Purchasing (see admin guide). The WMS appends extra requirements to the ones provided by the user in the JDL. These are specified by the configuration attribute WmsRequirements, which is in GLUE 1.3. To fully enable support for GLUE 2.0, this parameter must contain a valid GLUE2.0 expression, so the one provided with the default won't work. Here's a translation of the default WmsRequirements expression in GLUE2.0:

((ShortDeadlineJob =?= TRUE ? RegExp(".*sdj$", other.ceid) : !RegExp(".*sdj$", other.ceid)) && (other.Glue2.computing.share.MaxRunningJobs == 0 || other.Glue2.computing.share.totaljobs < other.Glue2.computing.share.MaxRunningJobs) && (EnableWmsFeedback =?= TRUE ? RegExp("cream", other.Glue2.Computing.Endpoint.ImplementationName, "i") : true) && (member(CertificateSubject,other.Glue2.Computing.Share.Policy) || member(strcat("VO:",VirtualOrganisation),other.Glue2.Computing.Share.Policy) || FQANmember(strcat("VOMS:", VOMS_FQAN), other.Glue2.Computing.Share.Policy)) is true && FQANmember(strcat("DENY:",VOMS_FQAN), other.Glue2.Computing.Share.Policy) isnt true)

Restructuring of the build structure and artefacts

A relevant number of components has been unified. This does not immediately affects performance nor introduces new features, but it greatly helps sustainability and consolidation. In particular:

* glite-wms-classad_plugin, glite-wms-ism, glite-wms-helper, glite-wms-broker, glite-wms-brokerinfo, glite-wms-matchmaking, glite-wms-manager have been unified into glite-wms-core

* glite-yaim-wms, glite-wms-configuration have been merged into glite-wms-configuration

* glite-wms-wmproxy, glite-wms-wmproxy-interface have been merged into glite-wms-interface

Nagios probes are distributed with the release. The same suggestions valid for CREAM apply:


Configuration Changes

To enable publication of service records to the EMI service registry, set in the site_info.def the following variables:


BDII_EMIR_SERP_PERIOD=1 # refresh rate in hours

BDII_EMIR_SERP_VALIDITY=2 # validity of the records in hours


and run:

/opt/glite/yaim/bin/yaim -r -f config_emir_serp -s siteinfo_/site-info.def

Already introduced with EMI WMS 3.4.0:



3) Known issues

To enable submission to the ARC CE using GRAM, a version of HTCondor >= 7.8.6 is needed. The EMI-3 release of the WMS ships with Condor-emi 7.8.0. HTCondor 7.8.6 has been verified to be binary compatible with 7.8.0. Just upgrade to 7.8.6 and submission to ARC will be enabled.

-- MarcoCecchi - 2012-06-22

Edit | Attach | PDF | History: r12 | r7 < r6 < r5 < r4 | Backlinks | Raw View | More topic actions...
Topic revision: r5 - 2013-02-15 - MarcoCecchi
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback