EMI 2 (Matterhorn) - 21.05.2012
- Release Notes:
- Installation:
- Software
- Documentation
- AMGA v.2.3.0, task #23299
- APEL parsers v. 1.1.0, task #23300
- APEL publisher v. 3.3.0, task #23301
- ARC CE v. 2.0.0, task #23302
- ARC Clients v. 2.0.0, task #23303
- ARC Core v. 2.0.0, task #23304
- ARC GridFtp server v.2.0.0, task #23305
- ARC InfoSys v.0.0, task #23306
- ARGUS v. 1.5.0, task #23307
- ARGUS-EES v. 0.1.3, task #23308
- BDII core v. 1.3.0 task #23309
- BDII site v. 1.1.0, task #23310[
- BDII top v. 1.0.1, task #23311
- BLAH v. 1.18.0 task #23312
- CANL v. 1.0, task # 24865
- CEMon v. 1.14.0, task #23313
- CREAM LSF module v. 2.0.0 task #23314
- CREAM SGE module v. 2.0.0, task #23315
- CREAM Torque module v. 2.0.0, task #23316
- CREAM v. 1.14.0. task #21059
- dCache v. 2.1.2, task #23318
- Delegation Java v. 2.2.0, task #23319
- DPM v. 1.8.3, task #23321
- EMIR v. 1.1.1, task #24845
- EMI-NAGIOS v. 1.0.0, task #24872
- EMI-UI v. 2.0.0, task #23322
- EMI-WN v. 2.0.0, task #23323
- FTS v. 2.2.8, task #23324
- GFAL/lcg_util v. 1.12.1, task #23325
- gLExec-wn v. 1.1.1, task #23326
- gLite CLUSTER v. 2.0.0, task #23327
- gLite-gsoap/gss v. 3.1.3, task #23328
- gLite-proxyrenewal v. 1.3.25, task #23329
- gLite-MPI v. 1.3.0, task #23330
- gLite-yaim-core v. 5.1.0, task #23331
- gridsite v. 1.7.21, task #23332
- L&B v. 3.2.6, task #23334
- lcg-info-clients v. 1.0.1, task #23335
- LFC v. 1.8.3, task #23336
- Pseudonymity v. 1.1.0, task #24867
- RAL-SAGA-SD v. 1.0.0-4, task #23337
- StoRM SE v. 1.9.0, task #23338
- TORQUE server config v. 1.0.0-2, task #23339
- TORQUE WN config v. 1.0.0-2, task #23340
- Trustmanager v. 3.1.3, task #23341
- UNICORE Client6 v. 5.0.0, task #23342
- UNICORE Gateway6 v. 4.3.0, task #23344
- UNICORE HILA v. 2.3.0, task #]23343
- UNICORE TSI6 v. 5.0.0, task #24801
- UNICORE UVOS v. 1.5.1-1, task #24901
- UNICORE XUUDB v. 1.3.2-4, task #23345
- UNICORE Registry6 v. 5.0.0, task #24900
- UNICORE/X6v. 5.0.0, task #24800
- VOMS v. 2.0.8, task #24846
- VOMS-Admin v. 2.7.0, task #24847
- WNoDES v. 2.0.0-2, task #26124
Release Notes:
The EMI 2 release consists in
56 products
that meet the
EMI 2 Acceptance Criteria
- 454 (SL5), 447 (SL6), 60 (Deb6) EMI packages
- 37 (SL5), 28 (SL6), 18 (Deb6) external dependencies managed by EMI
- 2 (SL5) external contributions
- All components are fully supported on Scientific Linux 5 / 64 bit & Scientific Linux 6 /64 bit
- supported package formats, list available here.:
- tar.gz, src.tar.gz, rpm, src.rpm
- deb, dsc, orig.tar.gz, debian.tar.gz, tar.gz
- the upgrade path from the EMI 1 products to EMI 2 on SL5 is supported and it is described in the products documentation. For EMI 2/SL6 products versions only clean installations are recommended. Please refer to individual products Release Notes for more information.
- one single EMI repository for all components
Find
here the full list of EMI 2 products, with detailed
release notes and instructions for their
installation/configuration.
Installation:
All EMI products are distributed from a
single repository having the following structure:
- EMI production (stable): dist/EMI/2/{sl5,sl6,debian}
- stable and signed, well tested software components, recommended to be installed on production-sites
- EMI testing: dist/EMI/testing/2//
- packages that will become part of the next stable distribution; in the certification and validation phase and available for beta-testing & technical-previews
- Third-party: dist/EMI/2///third-party
- packages that are not part of EMI, but are currently not part of the base OS or EPEL
can be currently i386, x86_64, SRPMS, tgz
All EMI packages are signed with the EMI gpg key. The public key can be downloaded from http://emisoft.web.cern.ch/emisoft/dist/EMI/2/RPM-GPG-KEY-emi, and the fingerprint from http://emisoft.web.cern.ch/emisoft/dist/EMI/2/EMI_key_fingerprint.asc.
It is strongly recommended the use of the lastest version of the emi-release package containing the public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL & Debian:
To understand how to install and configure EMI products either refer to the EMI 2 Generic Installation & Configuration Guide or to each individual product documentation.
Software
EMI 2 software can be downloaded from EMI 2 repository.
Documentation
Please find here the EMI 2 products documentation.
Release Notes
What's new
- Added support for SL6 x86_64
- Added a Nagios probe for AMGA
- Added mdservice site option for Version Information Publish
Installation and configuration
AMGA may be installed system-wide using the rpm package.
$ yum install emi.amga.amga-server
AMGA can be configured easily as follows.
$ /etc/rc.d/init.d/mdservice init
For the detailed configuration, please refer the AMGA User's Manual.
AMGA service can be started as follows.
$ /etc/rc.d/init.d/mdservice start
Known issues
none
List of RFCs
- Features:
- Backward Incompatible:None
- Major:
Documentation
All the documentations are included in the following file.
For the details, Please refer the following Sections of the above document:
- Release Notes (mandatory): A Changelog
- Functional Description (mandatory): Section 1
- User Guide (mandatory): Section 4,5,6
- Client Installation and Configuration (mandatory): Section 2.1, 3.1
- Client Configuration Template (optional): Section 3.1
- Man Pages/Online Help (optional): man pages available
- API Documentation (optional): Section 14, 15, 16 and http://amga.web.cern.ch/amga/pages.html
- Service Interface description (optional): Section 17
- Build Documentation (optional): Section 2.4
- System Administrator Guide (mandatory): Section 2,8,9,10,11,12,13
- Service Reference Card (mandatory): https://twiki.cern.ch/twiki/bin/view/EMI/AMGAreference
Artefacts
APEL parsers v. 1.1.0, task #23300
Release Notes
What's new
- no changes, only porting to SL6/x86_64
Installation and configuration
Known issues
List of RFCs
The regression tests in the test reports correspond to the following bugs:
Documentation
Artefacts
APEL publisher v. 3.3.0, task #23301
Release Notes
What's new
Installation and configuration
Known issues
- On SL6, there is an error message raised when installing activemq as a dependency with yum:
Options:
-b, --base-dir BASE_DIR base directory for the home directory of the new account
The publisher works fine.
List of RFCs
Documentation
Artefacts
Release Notes
What's new
- Backward compatibility:
- Compatibility of ARC WS endpoints with older ARC 11.05 clients that relied on incomplete GLUE2 to communicate to pre-production WS endpoints are broken due to the more compliant GLUE2 LDAP and XML rendering introduced in this release. Upgrade to new ARC 12.05 Clients is highly recommended.
- No backward incompatibility is introduced w.r.t. the production gridftp interface.
- High priority bugs fixed:
- Medium priority bugs fixed:
Installation and configuration
- This release does not introduce any changes in the deployment procedures described in ARC CE documentation. No backwards incompatible changes w.r.t. EMI1 are introduced. Upgrade path from EMI1 to EMI2 is straightforward via binary updates.
- A new comprehensive system administration guide has been provided.
Known issues
List of RFCs
- Features:
- Backward incompatible:
- Major:
- Other:
Documentation
Artefacts
Release Notes
What's new
- Backward compatibility:
- Compute client library is completely rewritten, making client API backward incompatible. This requires re-writing all 3rd party tools based on the library. See Extended Release Notes for details.
- Note that older ARC clients from ARC 11.05 are not forward compatible with newer ARC 12.05 WS endpoints that use more complete GLUE2 information schema, thus an upgrade to new clients is highly recommended.
- Immediate priority bugs fixed:
- High priority bugs fixed:
- Medium priority bugs fixed:
Installation and configuration
- Upgrade path from EMI1 to EMI2 is straightforward via binary updates. Client library, however, is completely re-written. 3rd party tools developed using the library will have to be re-written using the new API.
Known issues
- EMI ES implementation is 80% complete.
- GLUE 2 support implementation is 80% complete.
List of RFCs
- Features:
- Backward Incompatible:
- Major:
- Other:
- Bug Fixes:
Documentation
Artefacts
Release Notes
- Backwards compability
- No backwards incompatible changes were introduced in ARC Core
What's new
- Feature:
- In order to support EMI-ES and ARGUS integration and other new functionality the following has been done:
- Support for EMI ADL in job parsers
- Support for GDS and EMI ES in delegation interfaces
- GFAL2 integration in DMCs
- mkdir support in data library and some DMCs
- Argus integration in SHCs
- Numerous small enhancements not reflected in RfCs
- Immediate priority bugs fixed:
- Medium priority bugs fixed:
Installation and configuration
- This release does not introduce any changes in the deployment procedures described in ARC CE documentation. No backwards incompatible changes w.r.t. EMI1 are introduced. Upgrade path from EMI1 to EMI2 is straightforward via
binary updates.
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's new
- Corresponding Nagios probe has been released.
- Immediate priority bugs fixed:
Installation and configuration
- This release does not introduce any changes in the deployment procedures described in NorduGrid GridFTP Server and ARC CE documentation. No backwards incompatible changes w.r.t. EMI1 are introduced. Upgrade path from EMI1 to EMI2 is straightforward via binary updates.
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's new
- task #21907 - Completed the GLUE2 LDAP rendering for the resource level ARC information system component
- Medium priority bugs fixed:
- Backwards compatibility: * Note that the completed GLUE2 implementation breaks backwards compatibility with ARC 11.05 clients that relied on an incomplete implementation to interact with pre-production WS interfaces.
Installation and configuration
- This release does not introduce any changes in the deployment procedures described in ARC CE documentation. No backwards incompatible changes w.r.t. EMI1 are introduced. Upgrade path from EMI1 to EMI2 is straightforward via
binary updates.
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's new
- Available for SL6/x86_64
- Argus 1.5 publish its GLUE2 information to BDII
- New Nagios probes available to monitor Argus 1.5
Installation and configuration
Known issues
- Before configuring the service with YAIM, you must run fetch-crl script at least once
/sbin/service fetch-crl start
- When upgrading from a previous (Argus 1.4) installation on SL5, you need to re-install Argus 1.5. This is due to an error in the Argus 1.4 post uninstall script
yum upgrade
# argus is upgraded...
yum reinstall argus-pap argus-pdp argus-pep-server
List of RFCs
- Features:
- Backward Incompatible: None
- Major:
- Bug Fixes:
Documentation
Artefacts
*SL5*|
Release Notes
What's new
- Version 0.1.3:
- Fixed to work on Red Hat 6.
- Creates /var/log/ees/ with root:ees and 770
- Creates /etc/ees.conf with root:ees and 640
- Now expects the libxacml to be installed, significant for the SRPM builds.
Installation and configuration
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's new
- Nothing, it is identical to EMI 1.
Installation and configuration
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's new
Installation and configuration
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's new
- The EMI 2 release of the top-level BDII by default operates in a caching mode (caching BDII). This functionality is enabled by the delayed delete option. During the refresh process, if an entry is no-longer available, rather than being deleted immediately, the DN of the entry is stored in a queue along with the timestamp. The delete operation is then delayed for a configurable length of time (by default 12 hours). If the entry reappears, the DN is removed from the queue. This functionality was requested to avoid the appearance of information volatility due to temporary infrastructure instabilities.
- The configuration parameter for the delay (in seconds) is the BDII_DELETE_DELAY variable in the bdii.conf configuration file. This can be also set using the Yaim variable of the same name. Setting this variable to 0 will disable this functionality.
Installation and configuration
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's new
- Single init script (/etc/init.d/glite-ce-blah-parser) for both the old and the new blparser.
- Possibility to pass all or some selected JDL attributes to the batch system
- Several bug fixes
- Implemented changes are backward compatible wrt EMI-1
Installation and configuration
- Since BLAH is deployed together with CREAM, please refer to the installation and configuration notes for the whole CREAM-CE
- Update from EMI-1 is supported. To do it:
- update the yum repository
- issue: yum update
- reconfigure using yaim
Known issues
List of RFCs
Documentation
Artefacts
Release Notes
What's News:
- This is the initial release of EMI's Common AuthenticatioN library. The documentation is completely new as well.
Installation & Configuration:
- N/A. caNl is a library to be used by other products.
Know issues:
- No know issues, but it is a freshly released product. Development continues.
List of RfCs:
Documentation:
Artefacts
Release Notes
What's New
- Publication in Glue 2.0 format finalized
- Now there are two different packages for client: one for api and one for cli
- Use of Axis2
- External jars are not included in the CREAM war anymore. So in case of e.g. a voms-api-java update, it is not needed anymore to also update CEMon
- Several configuration steps moved from yaim to package postinst scripts
- Implemented changes are backward compatible wrt EMI-1
Installation & Configuration
- Yaim (re)configuration is required after installation/update in the CREAM-CE
- Yaim reconfiguration is instead not needed in the UI.
- Since CEMon is deployed together with CREAM, please refer to the installation and configuration notes for the whole CREAM-CE
- CEMon log file moved in /var/log/cemonitor
- Configuration file $CATALINA_HOME/conf/Catalina/localhost/ce-monitor.xml not used anymore
- Update from EMI-1 is supported. To do it:
- update the yum repository
- issue: yum update
- reconfigure using yaim
Known issues
- there is an issue in yaim if CEMon should be configured to use ARGUS as authorization system. The workaround is to modify the file /opt/glite/yaim/functions/config_cream_cemon replacing the line:
-e "s|ARGUS_PEPD_ENDPOINTS=|${ARGUS_PEPD_ENDPOINTS=}|"\
with:
-e "s|ARGUS_PEPD_ENDPOINTS|${ARGUS_PEPD_ENDPOINTS}|" \
Documentation changes
- New system administrator guide and new service reference card wrt EMI-1
List of RfCs:
Documentation:
All the documentation relevant for CEMon is available in the CEMon web site (http://wiki.italiangrid.it/CEMon)
Artefacts
CREAM LSF module v. 2.0.0 task #23314
Release Notes:
What's New
- Glue2 support in the dynamic provider
- EPEL compliancy fixes in the dynamic provider
- Bug fixes
- Implemented changes are backward compatible wrt EMI-1
Installation & Configuration
- See CREAM sysadmin guide.
- Please note that yaim (re)configuration is required after installation/update
- Configuration file for infoprovider moved to /etc/lrms
- Update from EMI-1 is supported. To do it:
- update the yum repository
- issue: yum update
- reconfigure using yaim
Know issues
List of RfCs:
Documentation:
Artefacts
CREAM SGE module v. 2.0.0, task #23315
Release Notes
What's News:
- Glue2 support in the dynamic provider
- Bug fixes
Installation & Configuration:
- See CREAM sysadmin guide.
- Please note that yaim (re)configuration is required after installation/update
- Configuration file for infoprovider moved to /etc/lrms
- Since paths in EMI2 are changed from EMI1, for update from EMI1 please delete /etc/blah.config to renew it.
Know issues:
List of RfCs:
Documentation:
Artefacts
CREAM Torque module v. 2.0.0, task #23316
Release Notes
What's New
- Glue2 support in the dynamic provider
- Bug fixes
- Implemented changes are backward compatible wrt EMI-1
Installation & Configuration
- See CREAM sysadmin guide.
- Please note that yaim (re)configuration is required after installation/update
- Configuration file for infoprovider moved to /etc/lrms
- Update from EMI-1 is supported. To do it:
- update the yum repository
- issue: yum update
- reconfigure using yaim
Know issues
List of RfCs:
Documentation:
Artefacts
Release Notes
What's New
- First support for EMI-ES
- Publication in Glue 2.0 format finalized
- Bulk submission supported in CREAM CLI
- Support for RFC proxies
- In cluster mode possibility to map different queues to different clusters
- Possibility to use EDGI connector
- CreamCE publishes non-production state when job submission is disabled
- CREAM DB names are now configurable. This allows the use of a single mysql server to host the databases of multiple CREAM CEs
- Limiter script (glite_cream_load_monitor) now reads the thresholds from a configuration file (/etc/glite-ce-cream-utils/glite_cream_load_monitor.conf)
- Use of Axis2
- External jars are not included in the CREAM war anymore. So in case of e.g. a voms-api-java update, it is not needed anymore to also update CREAM
- Several configuration steps moved from yaim to package postinst scripts
- Several bug fixes
- Implemented changes are backward compatible wrt EMI-1
Installation & Configuration
- See CREAM sysadmin guide.
- Please note that yaim (re)configuration is required after installation/update
- Please note that there is a new CREAM Database schema wrt the EMI-1 release. This means that, in case of update, when reconfiguring the database will be scratched and recreated. So it is reccomended to drain the CE before applying the update.
- For cluster mode, the variables CE_HOST_xxx_CLUSTER_UniqueID are not used anymore. Instead the new variables QUEUE_xxx_CLUSTER_UniqueID must be used (since it is now possible to map different clusters to different queues)
- New yaim variables for EMI-ES:
- USE_EMIES (default: false)
- CREAM_ES_SANDBOX_PATH (default: /var/cream_es_sandbox)
- BLAH_JOBID_PREFIX_ES
- DEFAULT_QUEUE
- New yaim variables to set the relevant attributes of the Glue2 ComputingManager object:
- WORKING_AREA_SHARED
- WORKING_AREA_GUARANTEED
- WORKING_AREA_TOTAL
- WORKING_AREA_FREE
- WORKING_AREA_LIFETIME
- WORKING_AREA_MULTISLOT_TOTAL
- WORKING_AREA_MULTISLOT_FREE
- WORKING_AREA_MULTISLOT_LIFETIME
- New yaim variables to choose DB names:
- CREAM_DB_NAME (default: creamdb)
- DELEGATION_DB_NAME (default: delegationcreamdb)
- CREAM_ES_DB_NAME (default: esdb)
- DELEGATION_ES_DB_NAME (default: delegationesdb)
- New yaim variable CREAM_DATASOURCE_FACTORY (default: org.apache.commons.dbcp.BasicDataSourceFactory) for CREAM Datasource Factory
- New yaim variable CREAM_JAVA_OPTS_HEAP (default: "-Xms512m -Xmx2048m") for JAVA_OPTS for HEAP
- New yaim variable COMPUTING_SERVICE_ID needed for Glue2 publication
- Job wrapper template moved in /etc/glite-ce-cream
- Configuration file $CATALINA_HOME/conf/Catalina/localhost/ce-cream.xml not used anymore
- Update from EMI-1 is supported. To do it:
- update the yum repository
- issue: yum update
- reconfigure using yaim
Know issues
List of RfCs:
- Features:
- Bug Fixes: *Medium
Documentation:
All the documentation relevant for CREAM is available in the CREAM web site (http://wiki.italiangrid.it/CREAM)
Artefacts
Release Notes
What's New:
- Major additions were done to gplazma. There are two new plugins that adds support for NIS and Kerberos-based password authentication. For nfs3 and nfs41 support for RPCSEC_GSS security was added. The creation of users in the kpwd file was fixed, which was broken before. Chimera ACLs can now be queried and updated through a mounted NFS 4.1 file system. SRM supports the file:// protocol. This allows SRM to produce TURLs for this protocol.
- The webadmin service should now support (almost) all features of the older httpd service. We invite people to test the webadmin and report any problems. If no problems appear then we consider to remove the httpd service in a future dCache release.The WebAdmin interface has a SVG in the background. Note that Internet Explorer before version 9 does not support SVG and will thus not render the background image.
- dCache now publishes the EMI version for the doors in addition to publishing the EMI version of the PoolManager node. If the dCache software doesn't come from EMI then no such number is published.
- dCache 2.0 introduced configurable pool selection algorithms. dCache 2.1 adds a small pool selection algorithm for weighted random selection. The partition type of the new selection algorithm is wrandom. The weight for the write pool selection is free space / total free space. Read pool selection is random with a uniform distribution. Starting with dCache 2.1, pool manager will only generate a stage request for files with a known tape location. Sites that rely on the previous behaviour to import data stored to tape without dCache should contact support@dcacheNOSPAMPLEASE.org.
- During startup pools detect and recover lost meta data. They use various sources to reconstruct the state of the replica, such as the access latency and retention policy of the file. Until this release pools did however ignore information about whether files are already stored on tape. Thus a custodial nearline file would be marked precious even though it was flushed to tape. With this release such files will be marked as cached.
- Previous releases only supported the SSH 1 protocol. This protocol is known to be insecure. With this release we add support for the SSH 2 protocol. The two implementations are unfortunately not integrated and thus version 2 of the protocol is only supported on a separate port. The default port is 22224. Which version is supported is controlled by the sshVersion property. Rudimentary tab completion was added. The output of the help command is parsed to complete dCache shell commands. The current implementation suffers from a number of problems caused by inability to parse all help strings. This will be improved in future releases. Support for version 1 is temporarily kept in dCache. This is because the dCache GUI only supports version 1. It should however be expected that version 1 will be removed from dCache in the near future. At this point configuration properties specific to SSH 2 will likely be renamed.
- When using the billing database, the httpd service is able to generate plots from the information in the database. Support is enabled by setting the billingToDb property to yes for the httpd service. The plots are available under http://admin.example.org:2288/billingHistory/.
- The core xrootd protocol implementation has been moved to an external project called xrootd4j. This allows the code to be reused in other projects, and it serves as a simple framework for testing plugins for xrootd4j and dCache. The xrootd door in dCache and the xrootd support in pools have been updated to use the xrootd4j library. The notable change is that the interfaces for authorization and authentication plugins have changed. Third party plugins have to be updated to support dCache 2.1. For details on xrootd4j and xrootd4j plugins visit the xrootd4j homepage.
- Some changes have been done to the configuration files. Please have a look in the release notes for details.
- Starting with this release, the migration script is no longer included. A direct upgrade from 1.9.5 is not supported. We recommend that sites first upgrade to 1.9.12 and then to subsequent versions.
- Several third party libraries have been upgraded. See the following table for details about the version in dCache 2.0 vs dCache 2.1.
- Library 2.0 2.1
- Grizzly 1.9.19 2.1.8
- JNA 3.3.0 3.4.0
- SLF4J 1.6.1 1.6.4
- Milton WebDAV 1.5.10 1.6.8
- Spring Core 3.0.5 3.0.6
- AspectJ 1.6.10 1.6.12
- Logback 0.9.30 1.0.0
- Guava r09 10.0.1
- PostgreSQL JDBC 9.0-801 9.1-901
- Netty 3.2.4 3.2.7
- Berkeley DB for Java Edition 4.1.10 4.1.17
- Parboiled 1.0.0 1.0.2
- Liquibase 2.0.1 2.0.3
- ActiveMQ 5.4.2 5.4.3
Installation & Configuration:
- Please read release notes before upgrading.
- For installation just yum install dcache-server, for configuration just look at the documentation.
Know issues:
List of RfCs:
Documentation:
Artefacts
Delegation Java v. 2.2.0, task #23319
Release Notes
What's new
Installation and configuration
Known issues
List of RFCs
Documentation
Artefacts
| Binaries |
| SL5 |
| SL6 |
| Sources |
| SL5 |
| SL6 |
| Binary tarballs |
*SL5*|
Release Notes
What's new:
- Added NFS4.1/pNFS frontend
- Added SEMSG (Catalog Synchronization) daemon
Installation and Configuration:
Known issues:
List of RfCs:
Documentation:
Artefacts
Release Notes
List of RfCs:
- This is the first major release of EMIR.
- Features:
Documentation:
Artefacts
Release Notes
What's News:
- First release of the EMi-Nagios metapackage that collects the nagios-probes/plugins for almost all EMI services, like: ARC, ARGUS, CREAM & WN, DPM/LFC, EMI-EES, L&B, gLExec-wn, UNICORE, VOMS, WMS
Installation & Configuration:
# yum install emi-nagios
Known Issues:
- general configuration will be provided in a future update, after integration with SAMMonitoring framework
List of RfCs:
Documentation:
Artefacts
Release Notes
What's News:
- dCache: client:
- dcap & srm-client:
- The dCache client files of dCap and srmclient now all reside in FHS compliant locations. There is no migration script for switching form one version to another. An update deprecates the old tunnel packages and updates the old dCap package.
- In dCap overlinking and strict aliasing warnings were fixed. The -H parameter was introduced and dccp has a man page, now.
- There were no major changes in the srmclient.
- CREAM-cli:
- Bulk submission supported in CREAM CLI
- Support for RFC proxies
- Bug fixes
- WMS client:
- Backward Incompatible:
- removed option --default-jdl from the glite-wms-job-list-match command
- removed the --output option from the glite-wms-job-output command
- Major:
- added option --json and --pretty-print to glite-wms-job-status
- fixed glite-wms-job-cancel and submit's json format output
- fixed json format output of glite-wms-job-output
- added json format output and --json and --pretty-print to glite-wms-job-cancel command
- Other
- getaddrinfo loses random order
- glite-wms-job-status handles now the error of LB (EIDRM) related to purged job
Installation & Configuration:
# yum install emi-ui
# <path-to-yaim>yam -c -s <path_to_file>/site-info.def -n UI
Known issues:
List of RfCs:
-
- There are RfCs addressed by ht individual clients:
Documentation:
Artefacts
Release Notes
What's News:
- 2nd release of WN that includes major and minor updates of the middleware clients of AMGA, dCache, GFAl/lcg_utils.
Installation & Configuration:
# yum install emi-wn
- Configuration: - mainly for gLite-flavour clients, for the others please see the cpecific clients documentation
# <path-to-yaim>/yam -c -s <path_to_file>/site-info.def -n WN
Known issues:
List of RfCs:
- There are RfCs addressed by ht individual clients:
Documentation:
Artefacts
Release Notes
What's News:
Installation & Configuration:
Known issues:
- FTS nagios:
- TOM::Nagios & GridMon::sgutils must be installed separately
List of RfCs:
Documentation:
Artefacts
GFAL/lcg_util v. 1.12.1, task #23325
Release Notes
What's New:
- First release for EMI 2. No functional changes between this version and 1.12.0, released for EMI 1, all changes support the different EMI 2 packaging.
- Bugs submitted by externals (users).
- #307 correct gfal 1.0 EMI 2 RC4 packaging issue against gfalpy26, same for lcg-util.Internal changes
- Bugs submitted by developers (tracked in Trac only).
- #313 correct the problem with gfal 1.0 and LFC errnos in EMI 2
- #311 Release GFAL2 beta 1 for EMI 2
- #294 Merge the GFAL EPEL fix for EMI2RC3
Installation & Configuration:
- Using the appropriate repo files in the extended release notes, just issue:
# sudo yum install lcg_util
Mind, that it does not install all the transfer plugins that LCG_Util supports. They must also be installed if needed (dcap, lcgdm, lfc).
Known issues:
List of RfCs:
- New features:
- Backward Incompatible: None.
- Bug Fixes:
- Medium:
- LCG_Util Ticket 307: correct gfal 1.0 EMI 2 RC4 packaging issue against gfalpy26, same for lcg-util
- LCG_Util Ticket 313: correct the problem with gfal 1.0 and LFC errnos in EMI 2
- Note that this is a repackage of the 1.12.0 (EMI 1) release. All fixes are related to differences between EMI 1 and EMI 2, mainly packaging and interaction with lcgdm.
Documentation:
Artefacts
Release Notes
gLExec
What's New:
Only the default directory for LCAS and LCMAPS plugins has changed.
- If you use YAIM, you can just update and reconfigure and everything should work.
- Otherwise you have to manually update the plugin locations in the lcmaps and lcas db files in
- /etc/lcmaps/lcmaps*.db
- /etc/lcas/lcas*.db
to match the new installation directories for the plugins:
-
- /usr/lib(64)/lcas and /usr/lib(64)/lcmaps
for LCAS and LCMAPS respectively (the old location was /usr/lib(64)/modules for both). This change was necessary to satisfy Fedora/EPEL requirements.
Note that there are no problems in mixing gLite and EMI-1 and EMI-2
services such as a CREAM CE or Argus server.
List of RfCs:
Documentation:
Artefacts
gLite CLUSTER v. 2.0.0, task #23327
Release Notes
What's New
- Publication in Glue 2.0 format implemented
- Possibility to map different queues to different clusters
- Bug fixes
- Implemented changes are backward compatible wrt EMI-1
Installation & Configuration
- See CREAM CE sysadmin guide.
- Please note that yaim (re)configuration is required after installation/update
- New yaim variables QUEUE_xxx_CLUSTER_UniqueID, to map different clusters to different queues.
- New yaim variables to set the relevant attributes of theGlue2 ComputingManager object:
- WORKING_AREA_SHARED
- WORKING_AREA_GUARANTEED
- WORKING_AREA_TOTAL
- WORKING_AREA_FREE
- WORKING_AREA_LIFETIME
- WORKING_AREA_MULTISLOT_TOTAL
- WORKING_AREA_MULTISLOT_FREE
- WORKING_AREA_MULTISLOT_LIFETIME
- New yaim variable COMPUTING_SERVICE_ID needed for Glue2 publication
- Update from EMI-1 is supported. To do it:
- update the yum repository
- issue: yum update
- reconfigure using yaim
Known issues
Documentation changes
- New system administrator guide and new service reference card wrt EMI-1 release
List of RfCs:
Documentation:
Artefacts
gLite-gsoap/gss v. 3.1.3, task #23328
Release Notes
What's News:
- This is a bugfix release of GSS/gSOAP plugin, fixing DN matching and introducing support for additional platforms.
Installation & Configuration:
- There is no installation, the packages will be brought in by a depending application.
Known issues:
List of RfCs:
Documentation:
Artefacts
gLite-proxyrenewal v. 1.3.25, task #23329
Release Notes:
What's new:
- This is a bugfix release for the previous version of ProxyRenewal, fixing problems with VOMS attributes and anonymous MyProxy connections.
Deployment
- Upon update, restart the ProxyRenewal daemon by calling /etc/init.d/glite-proxy-renewald restart
Known Issues:
List of RfCs:
Documentation:
Artefacts
Release Notes:
What's New:
- MPD startup of MPICH2 jobs enabled in non-shared home directory WN (bug #49)
- MPICH2 with hydra tested with Torque/PBS and SGE (bug #51)
- General improvement of documentation.
Installation & Configuration:
- MPI execution requires the installation of additional MPI software (see manual) and may require also extra configuration of your CE and WN (e.g. passwordless SSH between nodes), check your batch system and MPI implementation for details
- No other extra special installation requirements, no need for restarting services.
- Yaim plugin available for configuration in WN and CEs.
- Proper accounting of MPI jobs requires a MPI implementation that provides tight integration with the batch system: OpenMPI in SGE and Torque/PBS (may require recompilation of packages) or MPICH/MPICH2 with OSC mpiexec in Torque/PBS. Newer versions of MPICH2 with Hydra also provide integration with Torque and SGE.
Known Issues:
List of RfCs:
- Bug Fixes:
- Medium:
- MPD start with MPICH2 fails (#49)
- mpich2 with hydra requires passwordless ssh login (#51)
Documentation:
Artefacts
gLite-yaim-core v. 5.1.0, task #23331
Release Notes:
What's News:
- glite-yaim-core is availavle on SL5/SL6 and Deb6
- New features:
- syntax checking of VOMSES lines
- make gLite start/stop script compatible w/ RHEL5 clones
- added comments on site-info.def explaining that the presence of HEPSPEC value is mandatory
- hostname is logged on yaimlog
- new utility function to detect the tomcat version
- Bug fixes
- make grid-env.sh compatible with zsh 4.2.6
- added support for emi-* configuration target
- added warning message when asked to run an unexpected function
Installation & Configuration:
- Installation - the yaim-core module is normally installed as dependency of the EMI products metapackages using this tool
- Configuration - detals about configuring each EMI product using this configuration tools are given in the respective products configuration guides. General information is available also at: https://twiki.cern.ch/twiki/bin/view/EMI/GenericInstallationConfigurationEMI2
Known issues:
List of RfCs:
Documentation:
Artefacts
Release Notes:
What's News:
- This is a bugfix release for GridSite, addressing several bugs (VOMS attribute handling, httpd module loading priorities etc.) and harmonizing gridsite's modules tructure with that used in EPEL..
Installation & Configuration:
- To deploy, update your installation and restart the Web-server.
Known issues:
List of RfCs:
Documentation:
Artefacts
Release Notes:
What's News:
- L&B 3.2 implements extended messaging capabilities (job history, anonymization), server-side statistics, finalized CREAM support, and provides fixes for multiple bugs identified in various stages of the product's life cycle. Documentation was updated to reflect the changes.
Installation & Configuration:
- emi-lb metapackage is installed by yum. yaim configuration requires, at the very least, setting MYSQL_PASSWORD, SITE_NAME and SITE_EMAIL in the site-info.def file. Reconfiguration is required. reconfiguration by YAIM will restart the service automatically.
- The emi-lb metapackage does not install the Nagios plugin. It (package emi-lb-nagios-plugins) can be installed separately.
Known issues:
- glite-lb-load (Loading from dump files) is currently broken.
List of RfCs:
Documentation:
- Package glite-lb-doc is the authoritative source of documentation
Artefacts
lcg-info-clients v. 1.0.1, task #23335
Release Notes:
What's New:
- This is a repackage of EMI 1
Installation & Configuration:
Know issues:
List of RfCs:
Documentation:
Artefacts
Release Notes:
What's News:
- Added SEMSG (Catalog Synchronization) daemon
Installation & Configuration:
Known issues:
List of RfCs:
Documentation:
Artefacts
Pseudonymity v. 1.1.0, task #24867
Release Notes:
What's New:
- This is the initial EMI version
Installation & Configuration:
Known issues:
List of RfCs:
- (No RfCs related to this, as this is the initial EMI version.)
Documentation:
Artefacts
RAL-SAGA-SD v. 1.0.0-4, task #23337
Release Notes
What's new
- The API has not changed, but we are using a later SAGA Engine. There are no backaward incomplatible changes between EMI1 and EMI 2 versions.
Installation & Configuration:
- Just install rmps, no other configuration is nessecary
Known issues:
List of RFCs
Documentation
- Functional Description:
- Software Requirement Specification:
- Software Design Description:
- User Guide:
- Client Installation and Configuration:
- Man Pages/Online Help:
# man saga-sd
# saga-sd --help
# man saga-isn
#saga-isn --help
- API Documentation: /usr/share/doc/glite-saga-adapters-cpp/html/
- Build Documentation:
- Error Code Documentation:
- System Administrator Guide:
- Other Documentation: http://hepunx.rl.ac.uk/egee/sa3-uk/sd/
Artefacts
Release Notes:
StoRM-SE (v1.9.0) Release Notes
The StoRM product team is pleased to announce the release of StoRM v1.9.0 available for SL5 and SL6 platform (x86_64).
StoRM service is composed by 5 sub-components (4 servers: BE, FE, GridFTP, GridHTTPS and 1 client: clientSRM), which can be installed on distinguished hosts.
This release adds some new functionalities and includes some refactoring to improve the maintainability and performance. Among the new features a worth mentioning on ARGUS integration to enable the black-listing and the availability of T-StoRM, a test-suite used for the sanity check of the installation of StoRM. T-StoRM is also used as base to certify the product. Checksum service is no more supported and it is removed from release plan of StoRM in EMI.
For complete information on StoRM, including instructions on how to install and configure the service, see the StoRM website: http://storm.forge.cnaf.infn.it
What's new
- storm-frontend-server v1.8.0 (previous was v1.7.3) contains several new features and enhancements:
- Now it is possible ban users by using ARGUS mechanism. The integration is smooth, that is the callout to ARGUS can be enabled via configuration parameter.
- A monitoring log file has been added in order to enable log of what it is happen on the service in the last timeframe. The log entries show failures, error and success requests and time elapsed (min, max and average) to finish.
- Logging is enhanced. More detailed information are shown, and some other not-so-useful information are removed.
- (minor) Building mechanism has been refactored in order to improve the maintainability and portability to other platform.
- (minor) Fixed a small memory leak
Installation and configuration
- To install storm-frontend-server install its metapackage RPM: emi-storm-frontend-server-mp
- To configure storm-frontend-server use yaim on node se_storm_frontend. A good explanation of the required YAIM variable is available in /opt/glite/yaim/examples/siteinfo/services/se_storm_frontend
- The service uses ports 8444 (inbound), 8080 and 9998 (outbound to BE host), 3306 (outbound to MySQL host), so open them on your firewall.
- The service needs to be installed on a machine on which storm file system is mounted.
- To upgrade storm-frontend-server:
- stop the service,
- yum update storm-frontend-server
- service storm-frontend-server restart.
- restart all the other storm services (not required, but recommended)
* Known issues
StoRM-BackEnd-Server
What's new
- storm-backend-server v1.9.0 (previous was v1.8.2) contains several enhancements but no new features:
- Some part of code has been refactored to improve the maintainability
- A general review of all the code has been performed to solve potential bugs and to increase code quality
Installation and configuration
- To install storm-backend-server, install its metapackage RPM: emi-storm-backend-server-mp
- To configure storm-backend-server use yaim on the node se_storm_backend.
- The System Administration guide contains any useful information about installation and configuration.
- Moreover, a good explanation of the required YAIM variable is available in /opt/glite/yaim/examples/siteinfo/services/se_storm_backend
- If you configure other services with yaim on the same host always specify also se_storm_backend node
- To upgrade storm-backend-server:
- stop the backend service,
- yum update storm-backend-server
- service storm-backend-server restart.
- restart all the other storm services (not required, but recommended)
Known issues
StoRM-GridFTP-Server
What's new
- storm-gridftp-server v1.2.0 (provious was v1.1.0) contains enhancements but no new features:
- Building mechanism has been refactored in order to improve the maintainability and portability to other platform.
Installation and configuration
- To install storm-gridftp-server, install its metapackage RPM: 'emi-storm-globus-gridftp-mp'
Known issues
StoRM-GridHTTPs-Server
What's new
- First storm-gridhttps-server release.
- The storm gridhttps service is responsible to provide access to storm managed files via http and https protocol.
- It is able to manage plain requests and requests over SSL using an x509 certificate or an x509 certificate with VOMS extensions.
- For the requests providing a valid x509 certificate file access priviledges are verified in respect to the certificate owner and (if available) his FQANS.
Installation and configuration
- To install storm-gridhttps-server install its metapackage RPM: 'emi-storm-gridhttps-mp'.
- To configure storm-gridhttps-server you need to fill the requested YAIM variables as described in storm-gridhttps-server installation and configuration guide. A good explanation of the required YAIM variable is available in /opt/glite/yaim/examples/siteinfo/services/se_storm_gridhttps
- The service uses ports 8443 and (by default) 8080, so open them on your firewall.
- The service needs to be installed on a machine on which storm file system is mounted.
Known issues
StoRM-SRM-Client
What's new
- First storm-srm-client release in EMI. Previous releases are available via INFN-Grid
Installation and configuration
- To install storm-srm-client, install its metapackage RPM: 'emi-storm-srm-client-mp'
Known issues
T-StoRM
What's new
- First tstorm, tstorm-sanity and tstorm-common release in EMI.
Installation and configuration
- To install tstorm, tstorm-sanity and tstorm-common use yum install.
- Install tstorm-sanity on a storm node
- Install tstorm on a UI
Know issue:
- the test 'test_backend_gridhttps' fails on sl6 because of the presence of tomcat6 instead of tomcat5.
YAIM-STORM
What's new
- YAIM module version is 4.2.1-3.
- Fixed bugs:
Know issue:
* Specifying at YAIM configuration time "xfs" as file system type will produce an invalid namespace.xml preventing BackEnd service to boot.
-
- As workaround XFS users have to specify "posixfs" as file system type.
Documentation
What's new
List of RfCs:
- Features:
- Backward Incompatible: none
- Other:
- Bug Fixes:
Documentation:
Artefacts
TORQUE server config v. 1.0.0-2, task #23339
Release Notes:
What's News:
- support for SL5 & SL6
- new verison of maui packages redistributed from the third-party repository
Installation & Configuration:
# yum install emi-torque-server emi-torque-utils
# yum update
# <path>/yaim -c -s <site-info.def> -n TORQUE_server -n TORUQE_utils
Known issues:
List of RfCs:
- Features:
- Backward Incompatible: none
- Other:
Documentation:
Artefacts
TORQUE WN config v. 1.0.0-2, task #23340
Release Notes:
What's News:
- Added support for SL5 & SL6
Installation & Configuration:
- Installation, on an emi-wn:
# yum install emi-wn emi-torque-client
#yum update
#<path>/yaim -c -s <site-info.def> -n WN -n TORQUE_client
Known issues:
List of RfCs:
Documentation:
Artefacts
Trustmanager v. 3.1.3, task #23341
Release Notes:
What's News:
- Mock builds, SL6 support, a level of deb support, improved error messages.
Installation & Configuration:
Known issues:
- bug #94300: [Trustmanager] Trustmanager fails to read private keys that have text before the private key data
List of RFCs
Documentation
Artefacts
UNICORE Client6 v. 5.0.0, task #23342
Release Notes:
What's News:
- This is a backwards compatible release. A new version of the manual is available.
- updated to UNICORE 6.5.0 base libraries
- new feature: SAML push support (SF feature #2141970)
- improvement: support for EMI registry (SF enhancements #3438744)
- improvement: usage information ("ucc <cmd> --help") reformatted and grouped to make it easier to read
- new "list-transfers" command to list server-server transfers, which is supported by 6.5.0 and later servers (SF enhancements #3468402)
- improvement: removed unnecessary libraries (SF enhancements #3480082)
- improvement: more useful workflow-info output (show number of jobs,storage URL, tracer URL, list job URLs)
- improvement: accept common OS names ignoring case
- improvement: do not fallback to demo registry if no registry is given
- improvement: allow to skip registry connect using a preferences entry "contact-registry=false"
- fix: missing local files are detected before workflow submission (SF bug #3495229)
- improvement: better sample script "killall.groovy"
- fix: wildcard exports did not work (SF bug #3502412)
- improvement: when downloading results, create sub-dir for output files (stdout etc) instead of using job-id as prefix
- fix: re-try failed imports/exports once using the BFT protocol.If import still fails, destroy the job to prevent it staying in READY state. (SF bug #3510021)
- copy-file: support new reliable server-server file transfer mode
- new feature: RunTest command for running system tests
Installation & Configuration:
Known issues:
List of RfCs:
Documentation:
Artefacts
UNICORE Gateway6 v. 4.3.0, task #23344
Release Notes:
What's New:
- binary packages for SL6 & Debian 6 are available
- documentation was updated accordingly
- providing file:// URLs as pointers to logging configuration is now working correctly
Installation & Configuration:
- After update (as always) administrator must check for the .rpmnew and .rpmsave files in /etc/unicore/gateway directory, and merge the local settings.
- After the update a service restart is necessary.
Known issues:
List of RfCs:
Documentation:
Artefacts
UNICORE HILA v. 2.3.0, [[https://savannah.cern.ch/task/?23343][task #]23343]]
Release Notes:
What's News:
- Support for EMI Execution Services
- Support for GridFTP through gsiftp:// locations
- JobModel library and various renderings: JSDL, EMI-ADL
- RPM and deb packages through packman
- centralized executor management
Installation & Configuration:
Known issues:
List of RfCs:
Documentation:
Artefacts
*SL5*|
UNICORE TSI6 v. 5.0.0, task #24801
Release Notes:
What's New:
- This release is backward compatible.
- There is one new TSI function with retrieves job details from the BSS (for informational purposes) in case the job fails on the BSS. The associated UNICORE/X installation should be updated too, to make use of this new feature.
Installation & Configuration:
- Since upgrading from rpm/deb is not properly supported, it is suggested to remove and re-install the tsi package.
- The setup script will backup any locally modified files, so that your local changes can be easily merged with the updated files.
Known issues:
List of RfCs:
Documentation:
Artefacts
UNICORE UVOS v. 1.5.1-1, task #24901
Release Notes:
What's New:
- Bug in UVOS server was fixed, which resulted in extensive logging under server's heavy load
- Debian6 packages are available
- Documentation was updated accordingly
Installation & Configuration:
- There were no changes in configuration files so the update should install without any problems. However it is advised (as always) to double check if there are any .rpmnew or .rpmsave files in the /etc/unicore/uvos/uvos-server and /etc/unicore/uvos/uvos-clc directories.
Known issues:
List of RfCs:
Documentation:
- For UVOS server (type service):
- For UVOS client (type client):
Artefacts
UNICORE XUUDB v. 1.3.2-4, task #23345
Release Notes:
What's New:
- packages for Debian6 and SL6 are available
- documentation was updated accordingly
Installation & Configuration:
- As always it is advised to check for any .rpmnew and .rpmsave files in the '/etc/unicore/xuudb' directory and merge configuration changes if needed.
Known issues:
List of RfCs:
Documentation:
Artefacts
UNICORE Registry6 v. 5.0.0, task #24900
Release Notes
What's new
- The release is backwards compatible.
- Apart from a general update of the libraries, a bug with expiry of entries was fixed.
Installation and configuration
Known issues
List of RFCs
Documentation
Artefacts
Release Notes:
What's News:
- This release is backwards compatible. The list of changes:
- storages publish a list of server-to-server transfers (SF enhancements #3468402)
- improvement: RUS job-processor is included in the distribution
- fix: requesting a non-existent execution environment did not lead to failed a job (SF bug #3487520)
- new feature: metadata crawler (i.e. include exclude files) can be controlled using a special file in the base directory
- new feature: in case of errors, get detailed information about a job from the batch system (SF improvements #3405627)
- improvement/fix: pass on user-set job name to TSI (TSI_JOBNAME) (SF improvements #3514589)
- new feature: server-server transfer rate is published in file transfer properties (SF improvements #3474321)
- improvement: enabled file transfer protocols are update dynamically where possible (SF improvements #3462887)
- improvement: refactored Security information RP (showing client's xlogins, groups, server's accepted VOs and trusted CAs)
- improvement: assignment of requests to VOs (SF improvements #3495695)
- add support for the EMI registry (see docs/unicorex/emir.txt)
Installation & Configuration:
Known issues:
-
- EMI ES implementation is not complete.
List of RfCs:
Documentation:
Artefacts
Release Notes:
What's new
This VOMS release provides bug fixes and improvements in the VOMS MySQL and Oracle
plugins, in the Java APIs and in the YAIM configuration module.
The following issues have been solved:
- VOMS Java APIs now provides a sensible truststore refresh default (10 minutes).The truststore refresh period in minutes can be customized by setting the voms.trust-store-refresh-period
system property
- Connections are no longer aborted on every service request on MySQL.
- VOMS Oracle does not suffer anymore from crashes when put under some load.
- VOMS can now correctly issue attribute certificates to users that have an apostrophe in the certificate subject (MySQL backend)
- YAIM Voms provides a way to configure the --skipcacheck voms configuration parameter
For more information on the issues resolved in this release see: https://savannah.cern.ch/task/index.php?24846
Installation and configuration
Configuration changes
The YAIM module now provides support for the VOMS_SKIP_CA_CHECK variable. When this variable is set to true, VOMS checks only the certificate subject when assessing user membership in a VO. The default value for this variable is false, which leads to the normal VOMS behaviour (i.e., checking the certificate subject and certificate issuer when assessing user membership in a VO).
Known issues
Documentation changes
- The system administrator guide has been updated to the latest EMI approved template.
List of RfCs:
- New Features:
- Backward Incompatible : None
- Other:
- Bug Fixes:
Documentation:
Artefacts
Release Notes:
What's new
This VOMS Admin release provides bug fixes and improvements in the VOMS Admin client and server modules. Several new configuration options are now supported by the VOMS YAIM configuration module.
The following issues have been solved:
- The Sign AUP default grace period has been extended to a more sensible value
- An issue that prevented the correct sending of warning notifications before user membership expiration has been fixed.
- The voms-admin-configure script now correctly set the dbhost and dbport voms core configuration parameters (only affects non-YAIM installations).
- Spaces are now trimmed from certificates DNs edited via the VOMS admin web interface.
- Several small improvements to the VOMS Admin web interface.
- voms-admin-ping now correctly determines the list of VOMS VOs configured on a server.
- It is now possible to edit AUP url from the web interface.
- VOMS Admin doesn't depend anymore on LOCATION environment variables.
- Individual Oracle sequences are now used for the main VOMS database tables.
- VOMS Admin client now users a single separator in the output of the list-users command
- The voms-admin-configure --read-access-to-authenticated-clients flag now works as expected and is correctly triggered by YAIM.
The following new features are provided:
- It is now possible to disable the automatic membership suspension of users after membership expiration.
- VOMS Admin now allows for a configurable grace period before suspending users after their membership has expired.
- It is now possible to completely disable the membership end time. In this way users are suspended only if the fail to sign the AUP in the given time or if the VO manager explicitly requests the user suspension.
- It is now possible to restore multiple user memberships with a single click of the mouse.
- The sign AUP warning message text has been extended to better explain that users can restore their membership at any time by simply signing the AUP.
- All the membership validation service configuration options are now included and documented in the voms.service.properties file and are configurable via YAIM.
- It is now possible for users to select VO groups that they want to be part of at registration time.VO managers can then approve each group membership request independently. A new configuration parameter and YAIM variable has been provided to enable this functionality (which is switched off by default).
- VOMS Admin now provides API access to information about active, suspended and expired users. This information can be accessed using the new voms-admin-client commands:
count-users
count-suspended-users
count-expired-users
list-suspended-users
list-expired-users
list-user-stats
- The voms-admin client create-user command now supports the setting of personal information about the user (name, surname, institution,address, phoneNumber). This functionality was previously provided only by the web interface.
- New 'suspend-user' and 'restore-user' voms-admin client commands. This functionality was previously provided only by the web interface.
- Users are now sorted according to the membership expiration date in the main user search view.
- The VOMS user search functionality can now be limited to suspended users. This feature provides convenient access to the list of users that are currently suspended.
- Changing the active AUP now triggers a warning dialog.
- VOMS Admin now gives the ability of setting a description for VOMS groups at group creation time.
- The VOMS Admin user search page now clearly shows if users are suspended, expired or have a pending SIGN AUP task and other useful information (e.g., days to membership expiration, days to SIGN AUP task
expiration)
- A Nagios probe to test VOMS Admin VOs availability is now provided in the VOMS distribution.
- The voms-db-deploy.py script now implements the grant-read-only-access command, that is used to open the VO to all authenticated clients. This functionality is used by voms-admin-configure and YAIM at VO configuration time.
- The SAML endpoint implements the latest EMI SAML profile for Virtual Organization membership attributes profile http://bit.ly/emi-saml-profile
For more information on the issues resolved in this release and the new features see: https://savannah.cern.ch/task/index.php?24846
Installation and configuration
- See the VOMS System Administrator guide:https://wiki.italiangrid.it/twiki/bin/view/VOMS/VOMSSystemAdministratorGuide
- A YAIM (re)configuration is required after the installation the packages contained in this update.
Configuration changes
- Talk here about new YAIM variables supported.
Known issues
Documentation changes
- The system administrator guide has been updated to the latest EMI approved template.
List of RfCs:
Documentation:
Art\efacts
Release Notes:
What's News:
- First WNoDeS release in EMI. Please look at functional description to know more about this release.
Installation & Configuration:
- Please look at System Admin Guide to install and configure WNoDeS.
Know issues:
List of RfCs:
Documentation:
Artefacts
-- DoinaCristinaAiftimiei - 07-May-2012---+++ Release Notes
EMI Web
News
Events
Procedures and Tools
Mailing Lists
Documents
Project Structure
Create New Topic
Index
Search
Changes
Statistics
Copyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.