https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Bschulle&feedformat=atomEGIWiki - User contributions [en]2024-03-28T15:22:38ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=Agenda-05-01-2015&diff=80389Agenda-05-01-20152015-06-15T10:26:39Z<p>Bschulle: /* UNICORE */</p>
<hr />
<div>{|<br />
|-<br />
| [http://connect.ct.infn.it/egi-inspire-sa1-ter/ '''Adobe connect''' direct link]<br />
| ''Conference system is on adobe connect, no password required. <br />
|}<br />
<br />
{{TOC right}}<br />
<br />
= UMD releases status =<br />
<br />
== Status of the products verification/staged rollout ==<br />
<br />
<br />
=== Released ===<br />
* Last release UMD<br />
<br />
=== Under Staged Rollout ===<br />
<br />
<br />
* cream-torque v. 2.1.4<br />
<br />
* glexec-wn v. 1.3.0<br />
<br />
=== In Verification ===<br />
<br />
* cream-ge v. 2.3.0<br />
* qcg-computing-3.4.0 (only SL6)<br />
* qcg-notifications-3.4.0 (only SL6)<br />
* squid v. 2.7.19<br />
* fts3 v. 3.2.27<br />
* voms-clients v. 3.0.5<br />
* voms-admin v. 2.0.12<br />
* apel v. 1.3.1<br />
* px v. 1.3.36<br />
* DPM 1.8.9 <br />
* wms-ice v. 3.5.4<br />
* Globus 6.0.0 products: Gridftp, Globus-Default-Security, Gram5, MyProxy;<br />
<br />
'''Ready to be released:'''<br />
<br />
* cream v. 1.16.4<br />
<br />
=== Rejected ===<br />
<br />
* -----<br />
<br />
== Timeline for the next UMD updates ==<br />
* Mid December<br />
<br />
= Updates from the product teams =<br />
This section is directly contributed by the product teams. Please, add under your section the scheduled releases with a short comment about the updates introduced and where they are going to be released (EMI repositories, EPEL, private repositories ecc), linking external pages with these information is ok, but please add at least the expected date of the next release. It is important to discuss, within the URT, changes that may affect directly or indirectly other products. The text will be copied into the agenda of the next URT meeting, PT will just need to check that all the information are up to date.<br />
Please, feel free to alter the template if it doesn't feet with your needs.<br />
<br />
== APEL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== ARC ==<br />
* Release version 5.0.0 Expected: 2015-01-yy<br />
** Main changes: (including other products affected)<br />
*** Removal of old components:<br />
**** arc-ur-logger (replaced with Jura)<br />
**** LFC DMC<br />
**** DQ2 DMC<br />
**** old data staging<br />
**** Confusa (abandoned prototype)<br />
**** arcmigrate cli tool<br />
**** arcslcs<br />
**** SAML service<br />
**** gridsite dependency<br />
** Other information:<br />
<br />
== Argus ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
<br />
== dCache ==<br />
* Release version 2.6.38 Expected: next UMD release<br />
** Main changes: see appdb<br />
** Other information:<br />
<br />
== BDII ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== DPM/LFC ==<br />
* DPM <br />
** DPM/LFC 1.8.9 are in epel stable since last week<br />
** https://svnweb.cern.ch/trac/lcgdm/blog/dpm_1.8.9_relnotes<br />
** a fix for a bug on the latest dmlite component part of DPM 1.8.9 has been released and and it's already in EPEL stable<br />
** https://svnweb.cern.ch/trac/lcgdm/attachment/wiki/Dpm/dmlite0.7.2-relnotes.txt<br />
** First tests with CentOS7 using components from EPEL7, some issues found, but most of the components are working out of the box<br />
<br />
== GFAL/lcg_utils ==<br />
* The CERN Data Management Clients publish their releases here: http://dmc.web.cern.ch/releases<br />
* A new page with all releases and they status is available at https://dmc-docs.web.cern.ch/dmc-docs/<br />
* New in EPEL<br />
** gfal2 2.7.8 <br />
** gfal2-python 1.6.0 <br />
** gfal2-util 1.1.0 <br />
** srm-ifce 1.20.14<br />
** CGSI-gSOAP 1.3.7<br />
<br />
* CERN-PROD is available for staged rollout<br />
<br />
== FTS ==<br />
* FTS3 EPEL update released, v 3.2.26<br />
* new FTS3 v. 3.2.30 in Epel-testing<br />
<br />
== Frontier-Squid == <br />
* Release version: 2.7STABLE9-21.1; Released: 2014-12-03 - <br />
** Main changes: http://frontier.cern.ch/dist/rpms/frontier-squidRELEASE_NOTES<br />
*** Mainly improves multiple squid support, increasing max from 4 to 16 squids and limiting each squid to a share of available file descriptors<br />
** Other information (repository): http://frontier.cern.ch/dist/rpms<br />
<br />
== EMIR ==<br />
* Release version: ; Expected:<br />
** Main changes: <br />
** Other information:<br />
<br />
== UNICORE ==<br />
(expected) in the course of 2015 that we will publish packages for UMD <br />
probably via AppDB at https://appdb.egi.eu/store/software/unicore<br />
<br />
For now, packages for UNICORE 7.2.0 can be downloaded from<br />
<br />
Debian:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/deb<br />
<br />
RPM:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/rpm<br />
<br />
RPM packages were tested on Centos 6, so SL6 will be fine. SL5 is NOT supported <br />
any more<br />
<br />
* UCC 7.x Expected on: TBD<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== LB ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Gridsite ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Proxyrenewal ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CANL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLite-security ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLExec-wn ==<br />
<br />
* LCMAPS-plugins-C-PEP & EES(+xacml library) <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CREAM ==<br />
* BLAH <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
<br />
* CREAM<br />
* Release version 1.16.5 Expected: 2015-01-30<br />
** Main changes: (including other products affected)<br />
*** [https://issues.infn.it/jira/browse/CREAM/fixforversion/11910 CREAM 1.16.5 fixes & new features]<br />
** Other information:<br />
<br />
== STORM ==<br />
* Release version 1.11.5 - emergency <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11819 Fixes in 1.11.5]<br />
** Other information:<br />
*** fixes important issue affecting T1/GPFS 3.5<br />
<br />
<br />
* Release version 1.11.6 <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11815 Fixes in 1.11.6]<br />
** Other information:<br />
*** improvements in STORM Glue2 info-provider<br />
*** yaim-storm asks for a mandatory variable even if it's been defined<br />
<br />
== CREAM GE utils ==<br />
* Release version 2.3.1 Expected: 2014-11-25<br />
** Main changes:<br />
*** Fixes:<br />
**** Sanity checks for memory values<br />
*** New features: <br />
**** UNIVA milisecond precision support<br />
**** Support for both HH:MM:SS and number time formats<br />
** Other information:<br />
*** No other products are affected.<br />
*** [http://ge-utils.github.io/emi-cream-ge-v231.html Release notes]<br />
<br />
== VOMS ==<br />
* Release versions: <br />
** VOMS Admin server <br />
** VOMS Clients v. , VOMS API Java v. <br />
** VOMS C APIs, native clients and server v. <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== WMS ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Globus ==<br />
* Globus Toolkit version 6.0 was released 11 September.<br />
** Updates in Fedora updates testing/EPEL testing:<br />
*** EPEL5: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2812/<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2799/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2843/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-11457/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11364/<br />
*** F21: https://admin.fedoraproject.org/updates/FEDORA-2014-11226/<br />
** Please provide feedback in the tickets above.<br />
** Main changes: Backwards compatible, no soname changes.<br />
** Other information: The Grid Packaging Tools (GPT) will be dropped in favour of standard autotools. If you are relying on GPT tools or GPT metadata files, now is the time to migrate. The pkg-config support has been the preferred way to find Globus Toolkit dependencies a long time. The globus-makefile-header command will be replaced with a wrapper around pkg-config calls to provide some backward compatibility, but its use is not recommended. No GPT metadata files will be installed with the new release.<br />
** Fixes for reported issues: The updates above have been edited to include fixes for the following issues:<br />
***GGUS 106665 - Bad logging of IPv6 addresses in the gridftp server logs. Reported by STORM. Tested by STORM and DPM. https://github.com/globus/globus-toolkit/pull/8. Updated package: globus-gridftp-server-7.11-2<br />
*** Memory leaks in ftp client control library. Reported and tested by FTS. https://github.com/globus/globus-toolkit/pull/9. Updated package: globus-ftp-control-5.11-2<br />
* jGlobus 2.1.0 was released 26 September.<br />
** Updates in Fedora 19+, EPEL 6+ testing and Debian unstable/Debian testing:<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3072/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3087/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-12019/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11982/<br />
*** F21; https://admin.fedoraproject.org/updates/FEDORA-2014-12020/<br />
<br />
== QCG ==<br />
* Version 3.4.0 was released for SL5 and partialy (qcg-Broker) for SL6.<br />
<br />
* Support for SL6 is planned together with new functionality for first update of 2015, curently in validation <br />
* In preparation for the seame udpate (2015) also:<br />
** several updates of the packages, including a new versions of the QCG-Broker (support for voms) and QCG-Computing services.<br />
<br />
= Report from WLCG MW Officer =<br />
<br />
** open verifications are available at https://its.cern.ch/jira/secure/Dashboard.jspa?selectPageId=15100<br />
<br />
= Other topics =<br />
<br />
== XROOTD v.3 vs XROOTD v. 4 ==<br />
<br />
<br />
* Status: xrootd-compat package created and awaiting review:<br />
** https://bugzilla.redhat.com/show_bug.cgi?id=1168914<br />
<br />
== SL5 & MySQL 5.0 vs. MySQL 5.X, x>=1 ==<br />
<br />
* For more details see [[URT:SupportMysql5X|Middleware support of MySQL v. 5.x, x>=1]]<br />
<br />
= Actions =<br />
== Java 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:Java7 Java 7 - as dependency of released products/components ] - Please have a look and send comments, especially TP missing<br />
<br />
== EPEL 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:EPEL7 Status of support of EPEL 7, together with SL7 or CentOS7] - Please have a look and send comments, especially TP missing<br />
<br />
= AOB =<br />
<br />
* Next meeting '''19 Jan. 2015, 15:00 CET'''<br />
<br />
= Minutes =<br />
<br />
* [Minutes 05-01-2014]<br />
<br />
= Audio conference details =<br />
<i><br />
Room link: http://connect.ct.infn.it/egi-inspire-sa1-ter/<br />
<br />
Please provide you Name and product team/affiliation as Guest Name.<br />
<br />
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.<br />
<br />
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm<br />
<br />
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/<br />
<br />
Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.<br />
</i><br />
<br />
''Back to the URT agendas list page: [[URT_meetings_agendas]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:Java7&diff=78474URT:Java72015-04-14T06:26:20Z<p>Bschulle: /* Status of UMD services & components */</p>
<hr />
<div>{{TOC right}}<br />
<br />
= Java 7 - as dependency of released products/components =<br />
<br />
== Description of Issue ==<br />
<br />
*SL5.9:<br />
**JAVA 7<br />
*** The closed-source Java 6 packages are end of life as of Feb 2013. They are not included in SL5 starting with SL5.9 . Openjdk 1.6 and 1.7 are included by TUV. It is believed that openjdk is an acceptable replacement. The closed-source packages can still be downloaded from http://java.sun.com/<br />
<br />
* [http://www.oracle.com/technetwork/java/eol-135779.html Oracle Java SE Support Roadmap]<br />
* [https://www.java.com/en/download/faq/java_6.xml Oracle Java 6 - Java SE 6 End of Public Updates Notice]<br />
* [http://linux.web.cern.ch/linux/news.shtml#java6eol SLC announcement - Oracle (Sun) Java 6 (1.6) End of Life notice: February 2013]<br />
<br />
* [https://blogs.oracle.com/henrik/entry/moving_to_openjdk_as_the Moving to OpenJDK as the official Java SE 7 Reference Implementation]<br />
<br />
* [http://openjdk.java.net/faq/ OpenJDK]<br />
<br />
<br />
== Status of UMD services & components ==<br />
<br />
This table lists tests answers received from the TP regading the use of Java 7.<br />
<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
! Technology Provider<br />
! Service/Component <br />
! Comments<br />
! Java7 Package to be provided?<br />
|-<br />
|'''AMGA'''<br />
| - <br />
|<br />
|-<br />
|APEL<br />
|APEL server & client<br />
|(python) don't depend on Java<br />
|-<br />
|ARC<br />
| <br />
| - a dependency on java for the java API. <br />
- use whatever is in the distribution, without any particular recommendations.<br />
|-<br />
|'''ARGUS Collaboration'''<br />
|ZZZZ<br />
|<br />
|-<br />
|Grid Information System<br />
| <br />
|don't depend on Java<br />
|-<br />
|CREAM<br />
|cream-api-java, cream-common, cream, cream-job-plugin<br />
|works with Java 7 (tested)<br />
|-<br />
|CREAM (S)GE module<br />
| <br />
|don't depend on Java<br />
|-<br />
|'''CVMFS'''<br />
|ZZZZ<br />
|<br />
|-<br />
|CERN Data Management<br />
| DPM/LFC <br />
FTS3<br />
<br />
DMC clients<br />
|no dependency on Java<br />
|-<br />
|dCache<br />
|server & srm-client<br />
|all supported versions of dCache *require* Java 7 or newer. It is still avaialable a srmclient version that supports the Java 6.<br />
|-<br />
|'''UI/WN'''<br />
|ZZZZ<br />
|<br />
|-<br />
|'''EMIR'''<br />
|ZZZZ<br />
|<br />
|-<br />
|Frontier Squid<br />
|<br />
|doesn't depend on Java<br />
|-<br />
|gLExec-wn<br />
|ees-pepd-oh<br />
|ees-pepd-oh - runs within an Argus-PEPd service) using java-1.7.0-openjdk-1.7.0.65-2.5.1.2.el5_10 on a RedHat5, without any obvious problems, but no endurance testing<br />
|-<br />
|CESNET<br />
|canl-java<br />
L&B - java client and examples<br />
|canl-java - it is in Fedora (with java 1.8) and EPEL 7 (java 1.7)- so Java 7 is well supported<br />
L&B java client can also work with java 1.7. We don't have<br />
testsuite for java client, but there are no known issues.<br />
|Java 7 packages to be provided (canl-java and L&B)<br />
|-<br />
|MPI<br />
|mpi<br />
|doesn't depend on Java<br />
|-<br />
|QosCosGrid [QCG]<br />
|qcg-broker, qcg-broker-client<br />
|working with Java version "1.7.0_65", OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-4ubuntu1~0.14.04.2), OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) <br />
|-<br />
|VOMS/STORM<br />
|VOMS<br />
STORM<br />
|VOMS - can use Java 7 at runtime<br />
STORM - works with Java 7<br />
|voms-client Java 7 package to be provided<br />
|-<br />
|UNICORE<br />
|unicore-unicorex, unicore-registry, unicore-gateway, unicore-xuudb<br />
|works with Java 7 <br />
|<br />
|-<br />
|UNICORE<br />
|unicore-ucc, unicore-hila<br />
|Java 7 is recommended. The versions of the products that are in UMD<br />
still depend (via RPM manifest) on Java 6, our new releases (which are<br />
not yet in UMD) all require Java 7<br />
|for unicore-ucc: Java 7 packages to be provided, for unicore-hila: can be removed from UMD<br />
|-<br />
|WMS<br />
| WMS<br />
| doesn't depend on Java<br />
|-<br />
|Globus<br />
|<br />
| doesn't depend on Java<br />
|}</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:UMD_products_ID_cards&diff=75488URT:UMD products ID cards2015-01-12T08:08:07Z<p>Bschulle: /* UNICORE TSI6 */</p>
<hr />
<div> {{TOC_right}} <br />
This page reports the main information about the products currently released in UMD: <br />
<br />
*Support calendar for the major releases currently supported <br />
*Preferred release channels to get the future updates<br />
<br />
For every product all the versions released in UMD-2 and UMD-3 are listed, and grouped by the UMD major release. The list of versions is here for the convenience of user and site managers. Only the latest version of a product within an UMD major release is supposed to be updated with bug fixes and security updates. UMD team suggests the resource centres administrators to deploy the latest version of a product available within the UMD major release used in their sites. <br />
<br />
= Products ID cards =<br />
<br />
== AMGA ==<br />
<br />
*UMD-2&nbsp;: 2.3.0 <br />
**End of security support 2014-04-30 <br />
* Planning to continue to take care of maintaining the code in the medium-long term with updates to the current major release.<br />
* Intend to provide standard support.<br />
* No plan for a new major release<br />
<br />
== APEL ==<br />
<br />
*UMD-2&nbsp;: 3.3.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: <br />
** Packages are available on github page: http://apel.github.io/<br />
** Latest version of APEL software is '''1.1.3''' (lib, parsers, client, server) and the SSM messaging software is '''2.1.1'''.<br />
* Planning to continue to support the current version by maintaining the code in the medium to long term. <br />
** There are no major updates planned. New features will be added only as part of our funded work to extend the client to new accounting types. This should not impact the CPU accounting client which we intend to continue to support in its current form.<br />
* We are committing to running the accounting repository service for the '''next 2 years'''. <br />
** In that time, don't expect to make any compatibility-breaking changes to the CPU accounting client. We will be using it as a platform to develop accounting for other usage types. So the main development effort will be in other areas. We will continue to maintain the code as it is the basis for this development in other areas and the accounting repository service that we are providing.<br />
<br />
== ARC ==<br />
<br />
*UMD-2&nbsp;: 2.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.0.1 <br />
**End of security support 2014-04-30 <br />
* The policy of NorduGrid is to have one major release per year. <br />
** We support the current release until the next major release is out. <br />
** Users are then advised to move to the new major release. <br />
** Feature requests are treated in the same way as bugfixes. <br />
* Next major release is planned for '''November 2014''' so 13.11 will be supported until then.<br />
** Backward incompatibilities should always be expected in any ARC major release, but we can't guarantee that we will break backward compatibility in the next major release.<br />
** It will be supported until the next major release, so most likely until end of 2015.<br />
<br />
== ARGUS ==<br />
<br />
*UMD-2&nbsp;: 1.5.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.6.0 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== BDII core ==<br />
<br />
*UMD-2&nbsp;: 1.4.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.5.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Site ==<br />
<br />
*UMD-2&nbsp;: 1.1.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.2.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Top ==<br />
<br />
*UMD-2&nbsp;: 1.0.1; 1.0.2 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.1.X <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BLAH ==<br />
<br />
*UMD-2&nbsp;: 1.18.3 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.20.x <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CANl ==<br />
<br />
*UMD-3&nbsp;: 2.0.7 <br />
** canl-c++ - is part of ARC<br />
=== canl-c ===<br />
*Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
*There are currently no plans to retire EMI-3 products<br />
*No tangible plans for other major releases<br />
<br />
=== canl-java ===<br />
* currently there are two parallel canl-java major releases: <br />
** 1.?.?: in EMI repos and Maven central <br />
** 2.?.?: in Maven central only, i.e. no RPMs/debs.<br />
* Differences: <br />
** 2.x depends on latest BouncyCastle, 1.x on 1.46. <br />
** So far the branches are pretty similar (most of 2.x features and all bugfixes were backported to 1.x). <br />
** No plans nor time to think about moving 2.x to EMI repositories (due to problems with BC - packaging and compatibility).<br />
* Updates to the current major release - yes new major releases - no plans so far (besides 2.x which is already available). The problem is that maintaining a matrix of different canl versions compatible with different BC versions is not possible for me.<br />
* minor features - to the end of 2014. Bigger developments won't be included.<br />
* standard support - to the end of 2014, but if needed it can be prolonged.<br />
* security support - to the end of 2014<br />
* no major release planned (besides 2.x which are different wrt to BC dependency).<br />
** 2.x are backwards incompatible due to conflicting dependency usage.<br />
<br />
== Cluster ==<br />
<br />
*UMD-2&nbsp;: 2.0.0 <br />
**End of security support 2014-04-30 <br />
* UMD-3: v. 1.15.1<br />
* Product '''NO LONGER SUPPORTED'''<br />
<br />
== CREAM ==<br />
<br />
*UMD-2&nbsp;: 1.14.4 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 1.16.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
**Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM LSF module ==<br />
<br />
* EMI-3&nbsp;: 2.2.1 <br />
* The current release of 2.2.1 is out of date and should be updated to 2.3.7-1 in UMD-3 as soon as possible. This is the latest version which is available in github. <br />
* After that - only provide bug fix releases.<br />
* The info-dynamic-scheduler-lsf is supported at best effort basis. We will continue to do so as long as we need it ourselves, that is as long as we run CREAM CEs with LSF. Currently, there is no plan to retire these CEs yet.<br />
* No major release planned.<br />
<br />
== CREAM (S)GE module ==<br />
<br />
*UMD-3&nbsp;: 2.1.0 <br />
** best effort support<br />
** End of Full Support: 2014-04-30<br />
** End of Standard Updates: 2014-10-30<br />
** End of Security Updates & EOL: 2015-04-30<br />
* New major release:<br />
**Probably in 2015<br />
<br />
== CREAM SLURM module ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM Torque module ==<br />
<br />
*UMD-2&nbsp;: 2.0.2 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 2.1.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== dCache-srmclient ==<br />
<br />
*UMD-3&nbsp;: 2.2.22<br />
**The client will be supported as long as needed and have no new version. However, there is available a 2.6.12-1 srm-client release, which however needs Java 7 on runtime.<br />
<br />
== DCACHE ==<br />
<br />
*UMD-3: 2.2.22 <br />
** support the dCache server 2.6 branch until at least end of April 2015<br />
* new golden release 2.10 in July, this, as always will then be supported for two years<br />
* golden releases are often backward incompatible<br />
** Within golden releases we try not to implement new features to keep them stable<br />
** do not differentiate between standard support and security support only, if it is supported, it is supported.<br />
* support calendar: http://www.dcache.org/downloads/1.9/index.shtml<br />
<br />
== DPM/LFC ==<br />
<br />
*UMD-3&nbsp;: 1.8.8<br />
*Support for DPM/LFC and gfal2 is indefinite.<br />
** LFC:<br />
*** Atlas and LHCb both intend to stop using LFC by the end of 2014<br />
*** LFC will still be supported for other VOs, albeit at best-effort.<br />
** GFAL/lcg_util will not be supported after October 2014<br />
* Not planning a major release - in the "major=backward incompatible" sense<br />
<br />
== EMI UI ==<br />
<br />
*UMD-3&nbsp;: 3.0.0 <br />
*EMI-3: 3.0.3 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-ui-2<br />
<br />
== EMI WN ==<br />
<br />
*UMD-3: 3.0.0 <br />
*EMI-3: 3.0.1 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-wn-2<br />
<br />
== EMIR ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**End of security support '''2014-12-31'''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EMI, UMD<br />
** https://github.com/eu-emi/emiregistry<br />
** https://github.com/eu-emi/emir-serp<br />
** https://github.com/eu-emi/emir-web<br />
*Product main web page:<br />
**http://eu-emi.github.io/emiregistry/documentation/registry-1.2.1/emir-manual.html<br />
<br />
== Frontier-Squid == <br />
* UMD-3 : TO-BE-RELEASED - v. 2.7STABLE9-21.1<br />
* Support <br />
** for squid-2.7STABLE9 - end of 2015<br />
** for squid-3.5 to start beginning of 2015<br />
* Release channel:<br />
** cern-frontier: http://frontier.cern.ch/dist/rpms<br />
* Product main web page:<br />
** https://twiki.cern.ch/twiki/bin/view/Frontier/WebHome<br />
** [https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid Installing a Frontier squid cache server]<br />
** [http://frontier.cern.ch/dist/rpms-debug/frontier-squidRELEASE_NOTES Release Notes]<br />
<br />
== FTS3 ==<br />
<br />
*UMD-3&nbsp;: TO-BE-INCLUDED v. 3.2.26<br />
**End of security support ''''''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EPEL, UMD<br />
** http://fts3-service.web.cern.ch/content/downloads<br />
*Product main web page:<br />
**http://fts3-service.web.cern.ch/<br />
<br />
== GFAL/lcg_util ==<br />
<br />
<br />
*UMD-3&nbsp;: 1.16.0 <br />
** will '''not be supported after October 2014'''. It will be replaced by gfal2-util.<br />
<br />
== gLExec-wn ==<br />
<br />
*UMD-3&nbsp;: 1.2.0 <br />
**continued support till at least mid-2015 for gLexec and directly dependencies like LCMAPS, LCAS, SCAS and their modules such as the Argus C-PEP plugin<br />
** we move to a rolling-update model, but do not plan to introduce backward incompatible changes to the ABI or API without officially deprecating the interface at least 11 months in advance<br />
** security bug fixes will not be rolled in with standard updates, but will always be available as individual fixes<br />
** we are willing to coordinate API and ABI interface deprecation time lines with EGI UMD and in coordination with other EMI partners. <br />
<br />
* We are supporting our other components (ARGUS-EES) under the same conditions. <br />
<br />
* All support and maintenance will continue under the Nikhef PDP reference conditions: <br />
** security and critical bug fix support is included,<br />
** any feature requests and any pro-active maintenance needed, provided such a feature or enhancement is also of interest to either the NL-NGI, EGI.eu or a community which is supported by the NL-NGI or Nikhef itself, <br />
** the necessary software distribution and integration services based on standard OS platform distribution mechanisms and packaging formats,<br />
** the regular support scope (documentation, 3rd level incident handling, &c) extends to all communities and users that are affiliated or associated with the NL-NGI, EGI.eu, OSG, or Nikhef itself, and for those communities that also use other "EMI" products or products endorsed by the EGCF. Support also extended to any users that obtain software from EPEL or Debian but only insofar as it concerns security and critical bug fixes. <br />
<br />
* The continued maintenance and support is co-supported by the Dutch National e-Infrastructure, coordinated by SURFsara b.v. Although SURFsara expectes support for the national e-Infrastructure to be sustained through government funding, no formal guarantees can be given. In the unlikely case our support commitment has to change, we will inform EGI and our partners as soon as possible.<br />
<br />
== GridSite ==<br />
<br />
*UMD-3&nbsp;: 2.2.2<br />
** Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== gsoap-gss ==<br />
<br />
*UMD-3&nbsp;: 3.2.0 <br />
** Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== ''jclassads'' ==<br />
<br />
''*UMD-2&nbsp;: 2.4.3 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
''<br />
<br />
== L&amp;B ==<br />
<br />
*UMD-3&nbsp;: 4.0.12<br />
** Maintenance with minor improvements. <br />
** it is currently only used in the Community platform<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== lcg-info-clients ==<br />
<br />
*UMD-3&nbsp;: 1.0.1 <br />
** minor fixes if they are really needed. No new features or major releases for sure. If one day we manage to move to GLUE 2, we will have '''ginfo''' and we would be able to decommission lcg-info-clients. <br />
** lcg-infosites - bug fixes, but won´t implement new features nor publish GLUE 2. <br />
** lcg-info - not supported<br />
* Just as a reminder, both commands can be used for GLUE 1 only. In both cases there haven´t been any modifications in the past two years, I would say. So we shouldn´t expect many changes in any case.<br />
<br />
== MPI ==<br />
<br />
*UMD-3&nbsp;: 1.5.0 <br />
** support is going to be provided. <br />
** Both adding features as requested by users and maintaining the code. <br />
*** In principle it will be done by updating the current major release.<br />
* No plan for retiring the current version. New features will be implemented on this release if no major changes are needed for supporting them.<br />
* will be supported during this year, 2014, for sure. Probably the support will continue next year, but that is still undefined.<br />
* No plan for a new major release<br />
<br />
== ProxyRenewal ==<br />
<br />
*UMD-3&nbsp;: 2.1.3 <br />
**Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== QosCosGrid [QCG] ==<br />
<br />
*UMD-3: 3.2.0 <br />
**Support model: last revision of a released major release <br />
**full support: at least to the end of the year 2015, hopefully longer<br />
**(security) bug fixes: at least to the end of the year 2018, hopefully longer <br />
**new major release (incompatible with the current one) will be released only if it is necessary for some reason. We will try to keep the backwards compatibility of new releases as long as possible.<br />
*Release channels (QCG repository): <br />
*Product main web page: www.qoscosgrid.org<br />
<br />
== SLURM WN config ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== STORM ==<br />
<br />
*UMD-2&nbsp;: 1.10.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.11.x <br />
**End of security support 2015-04-30 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/storm/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/storm/index.html<br />
<br />
== TORQUE server config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0; 1.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.1 <br />
**End of security support 2014-04-30 <br />
* '''NOT supported'''<br />
<br />
== TORQUE WN config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*'''NOT supported'''<br />
<br />
== UNICORE Client6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE Gateway ==<br />
<br />
*UMD-3&nbsp;: UNICORE Gateway6 5.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE HILA ==<br />
<br />
*UMD-3&nbsp;: 2.4.1 <br />
** '''NOT supported'''<br />
<br />
== UNICORE Registry ==<br />
<br />
*UMD-3&nbsp;: UNICORE Registry6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE TSI ==<br />
<br />
*UMD-3&nbsp;: UNICORE TSI6 5.1.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** Individual packages for batch systems (nobatch, torque, slurm, sge, lsf)<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE UVOS ==<br />
<br />
*UMD-3&nbsp;: 1.6.0 <br />
** '''NOT supported'''<br />
<br />
== UNICORE XUUDB ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 2.1.2 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE/X ==<br />
<br />
*UMD-3&nbsp;: UNICORE UNICOREX6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== VOMS admin ==<br />
<br />
*UMD-2: 2.7.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: 3.2.0 (2.0.19) <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== VOMS ==<br />
<br />
*UMD-2&nbsp;: 2.0.10 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: Core - 2.0.11 &amp; Clients 3.0.4 <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== WMS ==<br />
<br />
*UMD-2&nbsp;: 3.4.1 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 3.6.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/wms-2<br />
<br />
== yaim-core ==<br />
<br />
*UMD-3&nbsp;: 5.1.1 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== SAGA ==<br />
<br />
*UMD-2&nbsp;: 1.6.1; 1.6.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
== ''Security-Integration'' ==<br />
<br />
''*UMD-2&nbsp;: 2.2.0; 2.2.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:''<br />
<br />
<br />
<br />
== Globus products ==<br />
<br />
=== globus-32-bit ===<br />
<br />
*UMD-3&nbsp;: 5.2.4 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-default-security ===<br />
<br />
*UMD-2&nbsp;: 5.2.1; 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== Globus GRAM5 ===<br />
<br />
*UMD-3&nbsp;: 5.2.5 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GridFTP ===<br />
<br />
*UMD-3&nbsp;: 5.2.5<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GSISSH ===<br />
<br />
*UMD-3&nbsp;: 5.3.10<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-myproxy ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.6.3; 5.9.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== globus-rls ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== GridWay ===<br />
<br />
*UMD-3&nbsp;: 5.14.0 <br />
** is no longer actively maintained. There will be security fixes but no major new release is planned. Therefore, it will NOT be in EGCF release V4.<br />
<br />
=== GridSAFE ===<br />
<br />
* UMD-3&nbsp;: 1.3.1<br />
** is being actively maintained and will be included in the EGCF V4 release. However, user support is only available with limited effort.<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4.<br />
<br />
=== GSI-SSHTerm ===<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**will be maintained in EGCF release 4! <br />
** Maintenance for at least 1 year, however, we assume a much longer maintenance with new features being integrated constantly.<br />
<br />
== NOT in UMD ==<br />
<br />
=== STS & Pseudonymity ===<br />
*Henri Mikkonen (henri.mikkonen@nimbleidm.com)<br />
** can still provide security/bug -fixing support for STS and Pseudonymity, but it should be noted that I'm not funded for this activity<br />
<br />
=== Hydra === <br />
* John White (john.white@cern.ch)<br />
** if there are requests for Hydra I'm happy to fix them. Haven't received anything lately though. I've been adding a Java client to the suite. Once the Java client is tested I'll make a new release.<br />
<br />
<br />
<br />
[[Category:Middleware]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:UMD_products_ID_cards&diff=75487URT:UMD products ID cards2015-01-12T08:07:09Z<p>Bschulle: /* UNICORE XUUDB */</p>
<hr />
<div> {{TOC_right}} <br />
This page reports the main information about the products currently released in UMD: <br />
<br />
*Support calendar for the major releases currently supported <br />
*Preferred release channels to get the future updates<br />
<br />
For every product all the versions released in UMD-2 and UMD-3 are listed, and grouped by the UMD major release. The list of versions is here for the convenience of user and site managers. Only the latest version of a product within an UMD major release is supposed to be updated with bug fixes and security updates. UMD team suggests the resource centres administrators to deploy the latest version of a product available within the UMD major release used in their sites. <br />
<br />
= Products ID cards =<br />
<br />
== AMGA ==<br />
<br />
*UMD-2&nbsp;: 2.3.0 <br />
**End of security support 2014-04-30 <br />
* Planning to continue to take care of maintaining the code in the medium-long term with updates to the current major release.<br />
* Intend to provide standard support.<br />
* No plan for a new major release<br />
<br />
== APEL ==<br />
<br />
*UMD-2&nbsp;: 3.3.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: <br />
** Packages are available on github page: http://apel.github.io/<br />
** Latest version of APEL software is '''1.1.3''' (lib, parsers, client, server) and the SSM messaging software is '''2.1.1'''.<br />
* Planning to continue to support the current version by maintaining the code in the medium to long term. <br />
** There are no major updates planned. New features will be added only as part of our funded work to extend the client to new accounting types. This should not impact the CPU accounting client which we intend to continue to support in its current form.<br />
* We are committing to running the accounting repository service for the '''next 2 years'''. <br />
** In that time, don't expect to make any compatibility-breaking changes to the CPU accounting client. We will be using it as a platform to develop accounting for other usage types. So the main development effort will be in other areas. We will continue to maintain the code as it is the basis for this development in other areas and the accounting repository service that we are providing.<br />
<br />
== ARC ==<br />
<br />
*UMD-2&nbsp;: 2.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.0.1 <br />
**End of security support 2014-04-30 <br />
* The policy of NorduGrid is to have one major release per year. <br />
** We support the current release until the next major release is out. <br />
** Users are then advised to move to the new major release. <br />
** Feature requests are treated in the same way as bugfixes. <br />
* Next major release is planned for '''November 2014''' so 13.11 will be supported until then.<br />
** Backward incompatibilities should always be expected in any ARC major release, but we can't guarantee that we will break backward compatibility in the next major release.<br />
** It will be supported until the next major release, so most likely until end of 2015.<br />
<br />
== ARGUS ==<br />
<br />
*UMD-2&nbsp;: 1.5.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.6.0 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== BDII core ==<br />
<br />
*UMD-2&nbsp;: 1.4.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.5.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Site ==<br />
<br />
*UMD-2&nbsp;: 1.1.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.2.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Top ==<br />
<br />
*UMD-2&nbsp;: 1.0.1; 1.0.2 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.1.X <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BLAH ==<br />
<br />
*UMD-2&nbsp;: 1.18.3 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.20.x <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CANl ==<br />
<br />
*UMD-3&nbsp;: 2.0.7 <br />
** canl-c++ - is part of ARC<br />
=== canl-c ===<br />
*Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
*There are currently no plans to retire EMI-3 products<br />
*No tangible plans for other major releases<br />
<br />
=== canl-java ===<br />
* currently there are two parallel canl-java major releases: <br />
** 1.?.?: in EMI repos and Maven central <br />
** 2.?.?: in Maven central only, i.e. no RPMs/debs.<br />
* Differences: <br />
** 2.x depends on latest BouncyCastle, 1.x on 1.46. <br />
** So far the branches are pretty similar (most of 2.x features and all bugfixes were backported to 1.x). <br />
** No plans nor time to think about moving 2.x to EMI repositories (due to problems with BC - packaging and compatibility).<br />
* Updates to the current major release - yes new major releases - no plans so far (besides 2.x which is already available). The problem is that maintaining a matrix of different canl versions compatible with different BC versions is not possible for me.<br />
* minor features - to the end of 2014. Bigger developments won't be included.<br />
* standard support - to the end of 2014, but if needed it can be prolonged.<br />
* security support - to the end of 2014<br />
* no major release planned (besides 2.x which are different wrt to BC dependency).<br />
** 2.x are backwards incompatible due to conflicting dependency usage.<br />
<br />
== Cluster ==<br />
<br />
*UMD-2&nbsp;: 2.0.0 <br />
**End of security support 2014-04-30 <br />
* UMD-3: v. 1.15.1<br />
* Product '''NO LONGER SUPPORTED'''<br />
<br />
== CREAM ==<br />
<br />
*UMD-2&nbsp;: 1.14.4 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 1.16.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
**Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM LSF module ==<br />
<br />
* EMI-3&nbsp;: 2.2.1 <br />
* The current release of 2.2.1 is out of date and should be updated to 2.3.7-1 in UMD-3 as soon as possible. This is the latest version which is available in github. <br />
* After that - only provide bug fix releases.<br />
* The info-dynamic-scheduler-lsf is supported at best effort basis. We will continue to do so as long as we need it ourselves, that is as long as we run CREAM CEs with LSF. Currently, there is no plan to retire these CEs yet.<br />
* No major release planned.<br />
<br />
== CREAM (S)GE module ==<br />
<br />
*UMD-3&nbsp;: 2.1.0 <br />
** best effort support<br />
** End of Full Support: 2014-04-30<br />
** End of Standard Updates: 2014-10-30<br />
** End of Security Updates & EOL: 2015-04-30<br />
* New major release:<br />
**Probably in 2015<br />
<br />
== CREAM SLURM module ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM Torque module ==<br />
<br />
*UMD-2&nbsp;: 2.0.2 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 2.1.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== dCache-srmclient ==<br />
<br />
*UMD-3&nbsp;: 2.2.22<br />
**The client will be supported as long as needed and have no new version. However, there is available a 2.6.12-1 srm-client release, which however needs Java 7 on runtime.<br />
<br />
== DCACHE ==<br />
<br />
*UMD-3: 2.2.22 <br />
** support the dCache server 2.6 branch until at least end of April 2015<br />
* new golden release 2.10 in July, this, as always will then be supported for two years<br />
* golden releases are often backward incompatible<br />
** Within golden releases we try not to implement new features to keep them stable<br />
** do not differentiate between standard support and security support only, if it is supported, it is supported.<br />
* support calendar: http://www.dcache.org/downloads/1.9/index.shtml<br />
<br />
== DPM/LFC ==<br />
<br />
*UMD-3&nbsp;: 1.8.8<br />
*Support for DPM/LFC and gfal2 is indefinite.<br />
** LFC:<br />
*** Atlas and LHCb both intend to stop using LFC by the end of 2014<br />
*** LFC will still be supported for other VOs, albeit at best-effort.<br />
** GFAL/lcg_util will not be supported after October 2014<br />
* Not planning a major release - in the "major=backward incompatible" sense<br />
<br />
== EMI UI ==<br />
<br />
*UMD-3&nbsp;: 3.0.0 <br />
*EMI-3: 3.0.3 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-ui-2<br />
<br />
== EMI WN ==<br />
<br />
*UMD-3: 3.0.0 <br />
*EMI-3: 3.0.1 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-wn-2<br />
<br />
== EMIR ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**End of security support '''2014-12-31'''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EMI, UMD<br />
** https://github.com/eu-emi/emiregistry<br />
** https://github.com/eu-emi/emir-serp<br />
** https://github.com/eu-emi/emir-web<br />
*Product main web page:<br />
**http://eu-emi.github.io/emiregistry/documentation/registry-1.2.1/emir-manual.html<br />
<br />
== Frontier-Squid == <br />
* UMD-3 : TO-BE-RELEASED - v. 2.7STABLE9-21.1<br />
* Support <br />
** for squid-2.7STABLE9 - end of 2015<br />
** for squid-3.5 to start beginning of 2015<br />
* Release channel:<br />
** cern-frontier: http://frontier.cern.ch/dist/rpms<br />
* Product main web page:<br />
** https://twiki.cern.ch/twiki/bin/view/Frontier/WebHome<br />
** [https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid Installing a Frontier squid cache server]<br />
** [http://frontier.cern.ch/dist/rpms-debug/frontier-squidRELEASE_NOTES Release Notes]<br />
<br />
== FTS3 ==<br />
<br />
*UMD-3&nbsp;: TO-BE-INCLUDED v. 3.2.26<br />
**End of security support ''''''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EPEL, UMD<br />
** http://fts3-service.web.cern.ch/content/downloads<br />
*Product main web page:<br />
**http://fts3-service.web.cern.ch/<br />
<br />
== GFAL/lcg_util ==<br />
<br />
<br />
*UMD-3&nbsp;: 1.16.0 <br />
** will '''not be supported after October 2014'''. It will be replaced by gfal2-util.<br />
<br />
== gLExec-wn ==<br />
<br />
*UMD-3&nbsp;: 1.2.0 <br />
**continued support till at least mid-2015 for gLexec and directly dependencies like LCMAPS, LCAS, SCAS and their modules such as the Argus C-PEP plugin<br />
** we move to a rolling-update model, but do not plan to introduce backward incompatible changes to the ABI or API without officially deprecating the interface at least 11 months in advance<br />
** security bug fixes will not be rolled in with standard updates, but will always be available as individual fixes<br />
** we are willing to coordinate API and ABI interface deprecation time lines with EGI UMD and in coordination with other EMI partners. <br />
<br />
* We are supporting our other components (ARGUS-EES) under the same conditions. <br />
<br />
* All support and maintenance will continue under the Nikhef PDP reference conditions: <br />
** security and critical bug fix support is included,<br />
** any feature requests and any pro-active maintenance needed, provided such a feature or enhancement is also of interest to either the NL-NGI, EGI.eu or a community which is supported by the NL-NGI or Nikhef itself, <br />
** the necessary software distribution and integration services based on standard OS platform distribution mechanisms and packaging formats,<br />
** the regular support scope (documentation, 3rd level incident handling, &c) extends to all communities and users that are affiliated or associated with the NL-NGI, EGI.eu, OSG, or Nikhef itself, and for those communities that also use other "EMI" products or products endorsed by the EGCF. Support also extended to any users that obtain software from EPEL or Debian but only insofar as it concerns security and critical bug fixes. <br />
<br />
* The continued maintenance and support is co-supported by the Dutch National e-Infrastructure, coordinated by SURFsara b.v. Although SURFsara expectes support for the national e-Infrastructure to be sustained through government funding, no formal guarantees can be given. In the unlikely case our support commitment has to change, we will inform EGI and our partners as soon as possible.<br />
<br />
== GridSite ==<br />
<br />
*UMD-3&nbsp;: 2.2.2<br />
** Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== gsoap-gss ==<br />
<br />
*UMD-3&nbsp;: 3.2.0 <br />
** Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== ''jclassads'' ==<br />
<br />
''*UMD-2&nbsp;: 2.4.3 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
''<br />
<br />
== L&amp;B ==<br />
<br />
*UMD-3&nbsp;: 4.0.12<br />
** Maintenance with minor improvements. <br />
** it is currently only used in the Community platform<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== lcg-info-clients ==<br />
<br />
*UMD-3&nbsp;: 1.0.1 <br />
** minor fixes if they are really needed. No new features or major releases for sure. If one day we manage to move to GLUE 2, we will have '''ginfo''' and we would be able to decommission lcg-info-clients. <br />
** lcg-infosites - bug fixes, but won´t implement new features nor publish GLUE 2. <br />
** lcg-info - not supported<br />
* Just as a reminder, both commands can be used for GLUE 1 only. In both cases there haven´t been any modifications in the past two years, I would say. So we shouldn´t expect many changes in any case.<br />
<br />
== MPI ==<br />
<br />
*UMD-3&nbsp;: 1.5.0 <br />
** support is going to be provided. <br />
** Both adding features as requested by users and maintaining the code. <br />
*** In principle it will be done by updating the current major release.<br />
* No plan for retiring the current version. New features will be implemented on this release if no major changes are needed for supporting them.<br />
* will be supported during this year, 2014, for sure. Probably the support will continue next year, but that is still undefined.<br />
* No plan for a new major release<br />
<br />
== ProxyRenewal ==<br />
<br />
*UMD-3&nbsp;: 2.1.3 <br />
**Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== QosCosGrid [QCG] ==<br />
<br />
*UMD-3: 3.2.0 <br />
**Support model: last revision of a released major release <br />
**full support: at least to the end of the year 2015, hopefully longer<br />
**(security) bug fixes: at least to the end of the year 2018, hopefully longer <br />
**new major release (incompatible with the current one) will be released only if it is necessary for some reason. We will try to keep the backwards compatibility of new releases as long as possible.<br />
*Release channels (QCG repository): <br />
*Product main web page: www.qoscosgrid.org<br />
<br />
== SLURM WN config ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== STORM ==<br />
<br />
*UMD-2&nbsp;: 1.10.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.11.x <br />
**End of security support 2015-04-30 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/storm/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/storm/index.html<br />
<br />
== TORQUE server config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0; 1.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.1 <br />
**End of security support 2014-04-30 <br />
* '''NOT supported'''<br />
<br />
== TORQUE WN config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*'''NOT supported'''<br />
<br />
== UNICORE Client6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE Gateway ==<br />
<br />
*UMD-3&nbsp;: UNICORE Gateway6 5.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE HILA ==<br />
<br />
*UMD-3&nbsp;: 2.4.1 <br />
** '''NOT supported'''<br />
<br />
== UNICORE Registry ==<br />
<br />
*UMD-3&nbsp;: UNICORE Registry6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE TSI6 ==<br />
<br />
*UMD-3&nbsp;: 5.1.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE UVOS ==<br />
<br />
*UMD-3&nbsp;: 1.6.0 <br />
** '''NOT supported'''<br />
<br />
== UNICORE XUUDB ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 2.1.2 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE/X ==<br />
<br />
*UMD-3&nbsp;: UNICORE UNICOREX6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== VOMS admin ==<br />
<br />
*UMD-2: 2.7.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: 3.2.0 (2.0.19) <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== VOMS ==<br />
<br />
*UMD-2&nbsp;: 2.0.10 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: Core - 2.0.11 &amp; Clients 3.0.4 <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== WMS ==<br />
<br />
*UMD-2&nbsp;: 3.4.1 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 3.6.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/wms-2<br />
<br />
== yaim-core ==<br />
<br />
*UMD-3&nbsp;: 5.1.1 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== SAGA ==<br />
<br />
*UMD-2&nbsp;: 1.6.1; 1.6.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
== ''Security-Integration'' ==<br />
<br />
''*UMD-2&nbsp;: 2.2.0; 2.2.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:''<br />
<br />
<br />
<br />
== Globus products ==<br />
<br />
=== globus-32-bit ===<br />
<br />
*UMD-3&nbsp;: 5.2.4 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-default-security ===<br />
<br />
*UMD-2&nbsp;: 5.2.1; 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== Globus GRAM5 ===<br />
<br />
*UMD-3&nbsp;: 5.2.5 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GridFTP ===<br />
<br />
*UMD-3&nbsp;: 5.2.5<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GSISSH ===<br />
<br />
*UMD-3&nbsp;: 5.3.10<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-myproxy ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.6.3; 5.9.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== globus-rls ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== GridWay ===<br />
<br />
*UMD-3&nbsp;: 5.14.0 <br />
** is no longer actively maintained. There will be security fixes but no major new release is planned. Therefore, it will NOT be in EGCF release V4.<br />
<br />
=== GridSAFE ===<br />
<br />
* UMD-3&nbsp;: 1.3.1<br />
** is being actively maintained and will be included in the EGCF V4 release. However, user support is only available with limited effort.<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4.<br />
<br />
=== GSI-SSHTerm ===<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**will be maintained in EGCF release 4! <br />
** Maintenance for at least 1 year, however, we assume a much longer maintenance with new features being integrated constantly.<br />
<br />
== NOT in UMD ==<br />
<br />
=== STS & Pseudonymity ===<br />
*Henri Mikkonen (henri.mikkonen@nimbleidm.com)<br />
** can still provide security/bug -fixing support for STS and Pseudonymity, but it should be noted that I'm not funded for this activity<br />
<br />
=== Hydra === <br />
* John White (john.white@cern.ch)<br />
** if there are requests for Hydra I'm happy to fix them. Haven't received anything lately though. I've been adding a Java client to the suite. Once the Java client is tested I'll make a new release.<br />
<br />
<br />
<br />
[[Category:Middleware]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:UMD_products_ID_cards&diff=75486URT:UMD products ID cards2015-01-12T08:06:34Z<p>Bschulle: /* UNICORE/X6 */</p>
<hr />
<div> {{TOC_right}} <br />
This page reports the main information about the products currently released in UMD: <br />
<br />
*Support calendar for the major releases currently supported <br />
*Preferred release channels to get the future updates<br />
<br />
For every product all the versions released in UMD-2 and UMD-3 are listed, and grouped by the UMD major release. The list of versions is here for the convenience of user and site managers. Only the latest version of a product within an UMD major release is supposed to be updated with bug fixes and security updates. UMD team suggests the resource centres administrators to deploy the latest version of a product available within the UMD major release used in their sites. <br />
<br />
= Products ID cards =<br />
<br />
== AMGA ==<br />
<br />
*UMD-2&nbsp;: 2.3.0 <br />
**End of security support 2014-04-30 <br />
* Planning to continue to take care of maintaining the code in the medium-long term with updates to the current major release.<br />
* Intend to provide standard support.<br />
* No plan for a new major release<br />
<br />
== APEL ==<br />
<br />
*UMD-2&nbsp;: 3.3.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: <br />
** Packages are available on github page: http://apel.github.io/<br />
** Latest version of APEL software is '''1.1.3''' (lib, parsers, client, server) and the SSM messaging software is '''2.1.1'''.<br />
* Planning to continue to support the current version by maintaining the code in the medium to long term. <br />
** There are no major updates planned. New features will be added only as part of our funded work to extend the client to new accounting types. This should not impact the CPU accounting client which we intend to continue to support in its current form.<br />
* We are committing to running the accounting repository service for the '''next 2 years'''. <br />
** In that time, don't expect to make any compatibility-breaking changes to the CPU accounting client. We will be using it as a platform to develop accounting for other usage types. So the main development effort will be in other areas. We will continue to maintain the code as it is the basis for this development in other areas and the accounting repository service that we are providing.<br />
<br />
== ARC ==<br />
<br />
*UMD-2&nbsp;: 2.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.0.1 <br />
**End of security support 2014-04-30 <br />
* The policy of NorduGrid is to have one major release per year. <br />
** We support the current release until the next major release is out. <br />
** Users are then advised to move to the new major release. <br />
** Feature requests are treated in the same way as bugfixes. <br />
* Next major release is planned for '''November 2014''' so 13.11 will be supported until then.<br />
** Backward incompatibilities should always be expected in any ARC major release, but we can't guarantee that we will break backward compatibility in the next major release.<br />
** It will be supported until the next major release, so most likely until end of 2015.<br />
<br />
== ARGUS ==<br />
<br />
*UMD-2&nbsp;: 1.5.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.6.0 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== BDII core ==<br />
<br />
*UMD-2&nbsp;: 1.4.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.5.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Site ==<br />
<br />
*UMD-2&nbsp;: 1.1.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.2.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Top ==<br />
<br />
*UMD-2&nbsp;: 1.0.1; 1.0.2 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.1.X <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BLAH ==<br />
<br />
*UMD-2&nbsp;: 1.18.3 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.20.x <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CANl ==<br />
<br />
*UMD-3&nbsp;: 2.0.7 <br />
** canl-c++ - is part of ARC<br />
=== canl-c ===<br />
*Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
*There are currently no plans to retire EMI-3 products<br />
*No tangible plans for other major releases<br />
<br />
=== canl-java ===<br />
* currently there are two parallel canl-java major releases: <br />
** 1.?.?: in EMI repos and Maven central <br />
** 2.?.?: in Maven central only, i.e. no RPMs/debs.<br />
* Differences: <br />
** 2.x depends on latest BouncyCastle, 1.x on 1.46. <br />
** So far the branches are pretty similar (most of 2.x features and all bugfixes were backported to 1.x). <br />
** No plans nor time to think about moving 2.x to EMI repositories (due to problems with BC - packaging and compatibility).<br />
* Updates to the current major release - yes new major releases - no plans so far (besides 2.x which is already available). The problem is that maintaining a matrix of different canl versions compatible with different BC versions is not possible for me.<br />
* minor features - to the end of 2014. Bigger developments won't be included.<br />
* standard support - to the end of 2014, but if needed it can be prolonged.<br />
* security support - to the end of 2014<br />
* no major release planned (besides 2.x which are different wrt to BC dependency).<br />
** 2.x are backwards incompatible due to conflicting dependency usage.<br />
<br />
== Cluster ==<br />
<br />
*UMD-2&nbsp;: 2.0.0 <br />
**End of security support 2014-04-30 <br />
* UMD-3: v. 1.15.1<br />
* Product '''NO LONGER SUPPORTED'''<br />
<br />
== CREAM ==<br />
<br />
*UMD-2&nbsp;: 1.14.4 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 1.16.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
**Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM LSF module ==<br />
<br />
* EMI-3&nbsp;: 2.2.1 <br />
* The current release of 2.2.1 is out of date and should be updated to 2.3.7-1 in UMD-3 as soon as possible. This is the latest version which is available in github. <br />
* After that - only provide bug fix releases.<br />
* The info-dynamic-scheduler-lsf is supported at best effort basis. We will continue to do so as long as we need it ourselves, that is as long as we run CREAM CEs with LSF. Currently, there is no plan to retire these CEs yet.<br />
* No major release planned.<br />
<br />
== CREAM (S)GE module ==<br />
<br />
*UMD-3&nbsp;: 2.1.0 <br />
** best effort support<br />
** End of Full Support: 2014-04-30<br />
** End of Standard Updates: 2014-10-30<br />
** End of Security Updates & EOL: 2015-04-30<br />
* New major release:<br />
**Probably in 2015<br />
<br />
== CREAM SLURM module ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM Torque module ==<br />
<br />
*UMD-2&nbsp;: 2.0.2 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 2.1.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== dCache-srmclient ==<br />
<br />
*UMD-3&nbsp;: 2.2.22<br />
**The client will be supported as long as needed and have no new version. However, there is available a 2.6.12-1 srm-client release, which however needs Java 7 on runtime.<br />
<br />
== DCACHE ==<br />
<br />
*UMD-3: 2.2.22 <br />
** support the dCache server 2.6 branch until at least end of April 2015<br />
* new golden release 2.10 in July, this, as always will then be supported for two years<br />
* golden releases are often backward incompatible<br />
** Within golden releases we try not to implement new features to keep them stable<br />
** do not differentiate between standard support and security support only, if it is supported, it is supported.<br />
* support calendar: http://www.dcache.org/downloads/1.9/index.shtml<br />
<br />
== DPM/LFC ==<br />
<br />
*UMD-3&nbsp;: 1.8.8<br />
*Support for DPM/LFC and gfal2 is indefinite.<br />
** LFC:<br />
*** Atlas and LHCb both intend to stop using LFC by the end of 2014<br />
*** LFC will still be supported for other VOs, albeit at best-effort.<br />
** GFAL/lcg_util will not be supported after October 2014<br />
* Not planning a major release - in the "major=backward incompatible" sense<br />
<br />
== EMI UI ==<br />
<br />
*UMD-3&nbsp;: 3.0.0 <br />
*EMI-3: 3.0.3 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-ui-2<br />
<br />
== EMI WN ==<br />
<br />
*UMD-3: 3.0.0 <br />
*EMI-3: 3.0.1 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-wn-2<br />
<br />
== EMIR ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**End of security support '''2014-12-31'''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EMI, UMD<br />
** https://github.com/eu-emi/emiregistry<br />
** https://github.com/eu-emi/emir-serp<br />
** https://github.com/eu-emi/emir-web<br />
*Product main web page:<br />
**http://eu-emi.github.io/emiregistry/documentation/registry-1.2.1/emir-manual.html<br />
<br />
== Frontier-Squid == <br />
* UMD-3 : TO-BE-RELEASED - v. 2.7STABLE9-21.1<br />
* Support <br />
** for squid-2.7STABLE9 - end of 2015<br />
** for squid-3.5 to start beginning of 2015<br />
* Release channel:<br />
** cern-frontier: http://frontier.cern.ch/dist/rpms<br />
* Product main web page:<br />
** https://twiki.cern.ch/twiki/bin/view/Frontier/WebHome<br />
** [https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid Installing a Frontier squid cache server]<br />
** [http://frontier.cern.ch/dist/rpms-debug/frontier-squidRELEASE_NOTES Release Notes]<br />
<br />
== FTS3 ==<br />
<br />
*UMD-3&nbsp;: TO-BE-INCLUDED v. 3.2.26<br />
**End of security support ''''''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EPEL, UMD<br />
** http://fts3-service.web.cern.ch/content/downloads<br />
*Product main web page:<br />
**http://fts3-service.web.cern.ch/<br />
<br />
== GFAL/lcg_util ==<br />
<br />
<br />
*UMD-3&nbsp;: 1.16.0 <br />
** will '''not be supported after October 2014'''. It will be replaced by gfal2-util.<br />
<br />
== gLExec-wn ==<br />
<br />
*UMD-3&nbsp;: 1.2.0 <br />
**continued support till at least mid-2015 for gLexec and directly dependencies like LCMAPS, LCAS, SCAS and their modules such as the Argus C-PEP plugin<br />
** we move to a rolling-update model, but do not plan to introduce backward incompatible changes to the ABI or API without officially deprecating the interface at least 11 months in advance<br />
** security bug fixes will not be rolled in with standard updates, but will always be available as individual fixes<br />
** we are willing to coordinate API and ABI interface deprecation time lines with EGI UMD and in coordination with other EMI partners. <br />
<br />
* We are supporting our other components (ARGUS-EES) under the same conditions. <br />
<br />
* All support and maintenance will continue under the Nikhef PDP reference conditions: <br />
** security and critical bug fix support is included,<br />
** any feature requests and any pro-active maintenance needed, provided such a feature or enhancement is also of interest to either the NL-NGI, EGI.eu or a community which is supported by the NL-NGI or Nikhef itself, <br />
** the necessary software distribution and integration services based on standard OS platform distribution mechanisms and packaging formats,<br />
** the regular support scope (documentation, 3rd level incident handling, &c) extends to all communities and users that are affiliated or associated with the NL-NGI, EGI.eu, OSG, or Nikhef itself, and for those communities that also use other "EMI" products or products endorsed by the EGCF. Support also extended to any users that obtain software from EPEL or Debian but only insofar as it concerns security and critical bug fixes. <br />
<br />
* The continued maintenance and support is co-supported by the Dutch National e-Infrastructure, coordinated by SURFsara b.v. Although SURFsara expectes support for the national e-Infrastructure to be sustained through government funding, no formal guarantees can be given. In the unlikely case our support commitment has to change, we will inform EGI and our partners as soon as possible.<br />
<br />
== GridSite ==<br />
<br />
*UMD-3&nbsp;: 2.2.2<br />
** Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== gsoap-gss ==<br />
<br />
*UMD-3&nbsp;: 3.2.0 <br />
** Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== ''jclassads'' ==<br />
<br />
''*UMD-2&nbsp;: 2.4.3 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
''<br />
<br />
== L&amp;B ==<br />
<br />
*UMD-3&nbsp;: 4.0.12<br />
** Maintenance with minor improvements. <br />
** it is currently only used in the Community platform<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== lcg-info-clients ==<br />
<br />
*UMD-3&nbsp;: 1.0.1 <br />
** minor fixes if they are really needed. No new features or major releases for sure. If one day we manage to move to GLUE 2, we will have '''ginfo''' and we would be able to decommission lcg-info-clients. <br />
** lcg-infosites - bug fixes, but won´t implement new features nor publish GLUE 2. <br />
** lcg-info - not supported<br />
* Just as a reminder, both commands can be used for GLUE 1 only. In both cases there haven´t been any modifications in the past two years, I would say. So we shouldn´t expect many changes in any case.<br />
<br />
== MPI ==<br />
<br />
*UMD-3&nbsp;: 1.5.0 <br />
** support is going to be provided. <br />
** Both adding features as requested by users and maintaining the code. <br />
*** In principle it will be done by updating the current major release.<br />
* No plan for retiring the current version. New features will be implemented on this release if no major changes are needed for supporting them.<br />
* will be supported during this year, 2014, for sure. Probably the support will continue next year, but that is still undefined.<br />
* No plan for a new major release<br />
<br />
== ProxyRenewal ==<br />
<br />
*UMD-3&nbsp;: 2.1.3 <br />
**Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== QosCosGrid [QCG] ==<br />
<br />
*UMD-3: 3.2.0 <br />
**Support model: last revision of a released major release <br />
**full support: at least to the end of the year 2015, hopefully longer<br />
**(security) bug fixes: at least to the end of the year 2018, hopefully longer <br />
**new major release (incompatible with the current one) will be released only if it is necessary for some reason. We will try to keep the backwards compatibility of new releases as long as possible.<br />
*Release channels (QCG repository): <br />
*Product main web page: www.qoscosgrid.org<br />
<br />
== SLURM WN config ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== STORM ==<br />
<br />
*UMD-2&nbsp;: 1.10.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.11.x <br />
**End of security support 2015-04-30 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/storm/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/storm/index.html<br />
<br />
== TORQUE server config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0; 1.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.1 <br />
**End of security support 2014-04-30 <br />
* '''NOT supported'''<br />
<br />
== TORQUE WN config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*'''NOT supported'''<br />
<br />
== UNICORE Client6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE Gateway ==<br />
<br />
*UMD-3&nbsp;: UNICORE Gateway6 5.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE HILA ==<br />
<br />
*UMD-3&nbsp;: 2.4.1 <br />
** '''NOT supported'''<br />
<br />
== UNICORE Registry ==<br />
<br />
*UMD-3&nbsp;: UNICORE Registry6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE TSI6 ==<br />
<br />
*UMD-3&nbsp;: 5.1.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE UVOS ==<br />
<br />
*UMD-3&nbsp;: 1.6.0 <br />
** '''NOT supported'''<br />
<br />
== UNICORE XUUDB ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE/X ==<br />
<br />
*UMD-3&nbsp;: UNICORE UNICOREX6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== VOMS admin ==<br />
<br />
*UMD-2: 2.7.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: 3.2.0 (2.0.19) <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== VOMS ==<br />
<br />
*UMD-2&nbsp;: 2.0.10 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: Core - 2.0.11 &amp; Clients 3.0.4 <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== WMS ==<br />
<br />
*UMD-2&nbsp;: 3.4.1 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 3.6.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/wms-2<br />
<br />
== yaim-core ==<br />
<br />
*UMD-3&nbsp;: 5.1.1 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== SAGA ==<br />
<br />
*UMD-2&nbsp;: 1.6.1; 1.6.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
== ''Security-Integration'' ==<br />
<br />
''*UMD-2&nbsp;: 2.2.0; 2.2.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:''<br />
<br />
<br />
<br />
== Globus products ==<br />
<br />
=== globus-32-bit ===<br />
<br />
*UMD-3&nbsp;: 5.2.4 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-default-security ===<br />
<br />
*UMD-2&nbsp;: 5.2.1; 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== Globus GRAM5 ===<br />
<br />
*UMD-3&nbsp;: 5.2.5 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GridFTP ===<br />
<br />
*UMD-3&nbsp;: 5.2.5<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GSISSH ===<br />
<br />
*UMD-3&nbsp;: 5.3.10<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-myproxy ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.6.3; 5.9.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== globus-rls ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== GridWay ===<br />
<br />
*UMD-3&nbsp;: 5.14.0 <br />
** is no longer actively maintained. There will be security fixes but no major new release is planned. Therefore, it will NOT be in EGCF release V4.<br />
<br />
=== GridSAFE ===<br />
<br />
* UMD-3&nbsp;: 1.3.1<br />
** is being actively maintained and will be included in the EGCF V4 release. However, user support is only available with limited effort.<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4.<br />
<br />
=== GSI-SSHTerm ===<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**will be maintained in EGCF release 4! <br />
** Maintenance for at least 1 year, however, we assume a much longer maintenance with new features being integrated constantly.<br />
<br />
== NOT in UMD ==<br />
<br />
=== STS & Pseudonymity ===<br />
*Henri Mikkonen (henri.mikkonen@nimbleidm.com)<br />
** can still provide security/bug -fixing support for STS and Pseudonymity, but it should be noted that I'm not funded for this activity<br />
<br />
=== Hydra === <br />
* John White (john.white@cern.ch)<br />
** if there are requests for Hydra I'm happy to fix them. Haven't received anything lately though. I've been adding a Java client to the suite. Once the Java client is tested I'll make a new release.<br />
<br />
<br />
<br />
[[Category:Middleware]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:UMD_products_ID_cards&diff=75485URT:UMD products ID cards2015-01-12T08:05:55Z<p>Bschulle: /* UNICORE Gateway */</p>
<hr />
<div> {{TOC_right}} <br />
This page reports the main information about the products currently released in UMD: <br />
<br />
*Support calendar for the major releases currently supported <br />
*Preferred release channels to get the future updates<br />
<br />
For every product all the versions released in UMD-2 and UMD-3 are listed, and grouped by the UMD major release. The list of versions is here for the convenience of user and site managers. Only the latest version of a product within an UMD major release is supposed to be updated with bug fixes and security updates. UMD team suggests the resource centres administrators to deploy the latest version of a product available within the UMD major release used in their sites. <br />
<br />
= Products ID cards =<br />
<br />
== AMGA ==<br />
<br />
*UMD-2&nbsp;: 2.3.0 <br />
**End of security support 2014-04-30 <br />
* Planning to continue to take care of maintaining the code in the medium-long term with updates to the current major release.<br />
* Intend to provide standard support.<br />
* No plan for a new major release<br />
<br />
== APEL ==<br />
<br />
*UMD-2&nbsp;: 3.3.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: <br />
** Packages are available on github page: http://apel.github.io/<br />
** Latest version of APEL software is '''1.1.3''' (lib, parsers, client, server) and the SSM messaging software is '''2.1.1'''.<br />
* Planning to continue to support the current version by maintaining the code in the medium to long term. <br />
** There are no major updates planned. New features will be added only as part of our funded work to extend the client to new accounting types. This should not impact the CPU accounting client which we intend to continue to support in its current form.<br />
* We are committing to running the accounting repository service for the '''next 2 years'''. <br />
** In that time, don't expect to make any compatibility-breaking changes to the CPU accounting client. We will be using it as a platform to develop accounting for other usage types. So the main development effort will be in other areas. We will continue to maintain the code as it is the basis for this development in other areas and the accounting repository service that we are providing.<br />
<br />
== ARC ==<br />
<br />
*UMD-2&nbsp;: 2.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.0.1 <br />
**End of security support 2014-04-30 <br />
* The policy of NorduGrid is to have one major release per year. <br />
** We support the current release until the next major release is out. <br />
** Users are then advised to move to the new major release. <br />
** Feature requests are treated in the same way as bugfixes. <br />
* Next major release is planned for '''November 2014''' so 13.11 will be supported until then.<br />
** Backward incompatibilities should always be expected in any ARC major release, but we can't guarantee that we will break backward compatibility in the next major release.<br />
** It will be supported until the next major release, so most likely until end of 2015.<br />
<br />
== ARGUS ==<br />
<br />
*UMD-2&nbsp;: 1.5.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.6.0 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== BDII core ==<br />
<br />
*UMD-2&nbsp;: 1.4.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.5.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Site ==<br />
<br />
*UMD-2&nbsp;: 1.1.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.2.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Top ==<br />
<br />
*UMD-2&nbsp;: 1.0.1; 1.0.2 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.1.X <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BLAH ==<br />
<br />
*UMD-2&nbsp;: 1.18.3 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.20.x <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CANl ==<br />
<br />
*UMD-3&nbsp;: 2.0.7 <br />
** canl-c++ - is part of ARC<br />
=== canl-c ===<br />
*Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
*There are currently no plans to retire EMI-3 products<br />
*No tangible plans for other major releases<br />
<br />
=== canl-java ===<br />
* currently there are two parallel canl-java major releases: <br />
** 1.?.?: in EMI repos and Maven central <br />
** 2.?.?: in Maven central only, i.e. no RPMs/debs.<br />
* Differences: <br />
** 2.x depends on latest BouncyCastle, 1.x on 1.46. <br />
** So far the branches are pretty similar (most of 2.x features and all bugfixes were backported to 1.x). <br />
** No plans nor time to think about moving 2.x to EMI repositories (due to problems with BC - packaging and compatibility).<br />
* Updates to the current major release - yes new major releases - no plans so far (besides 2.x which is already available). The problem is that maintaining a matrix of different canl versions compatible with different BC versions is not possible for me.<br />
* minor features - to the end of 2014. Bigger developments won't be included.<br />
* standard support - to the end of 2014, but if needed it can be prolonged.<br />
* security support - to the end of 2014<br />
* no major release planned (besides 2.x which are different wrt to BC dependency).<br />
** 2.x are backwards incompatible due to conflicting dependency usage.<br />
<br />
== Cluster ==<br />
<br />
*UMD-2&nbsp;: 2.0.0 <br />
**End of security support 2014-04-30 <br />
* UMD-3: v. 1.15.1<br />
* Product '''NO LONGER SUPPORTED'''<br />
<br />
== CREAM ==<br />
<br />
*UMD-2&nbsp;: 1.14.4 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 1.16.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
**Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM LSF module ==<br />
<br />
* EMI-3&nbsp;: 2.2.1 <br />
* The current release of 2.2.1 is out of date and should be updated to 2.3.7-1 in UMD-3 as soon as possible. This is the latest version which is available in github. <br />
* After that - only provide bug fix releases.<br />
* The info-dynamic-scheduler-lsf is supported at best effort basis. We will continue to do so as long as we need it ourselves, that is as long as we run CREAM CEs with LSF. Currently, there is no plan to retire these CEs yet.<br />
* No major release planned.<br />
<br />
== CREAM (S)GE module ==<br />
<br />
*UMD-3&nbsp;: 2.1.0 <br />
** best effort support<br />
** End of Full Support: 2014-04-30<br />
** End of Standard Updates: 2014-10-30<br />
** End of Security Updates & EOL: 2015-04-30<br />
* New major release:<br />
**Probably in 2015<br />
<br />
== CREAM SLURM module ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM Torque module ==<br />
<br />
*UMD-2&nbsp;: 2.0.2 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 2.1.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== dCache-srmclient ==<br />
<br />
*UMD-3&nbsp;: 2.2.22<br />
**The client will be supported as long as needed and have no new version. However, there is available a 2.6.12-1 srm-client release, which however needs Java 7 on runtime.<br />
<br />
== DCACHE ==<br />
<br />
*UMD-3: 2.2.22 <br />
** support the dCache server 2.6 branch until at least end of April 2015<br />
* new golden release 2.10 in July, this, as always will then be supported for two years<br />
* golden releases are often backward incompatible<br />
** Within golden releases we try not to implement new features to keep them stable<br />
** do not differentiate between standard support and security support only, if it is supported, it is supported.<br />
* support calendar: http://www.dcache.org/downloads/1.9/index.shtml<br />
<br />
== DPM/LFC ==<br />
<br />
*UMD-3&nbsp;: 1.8.8<br />
*Support for DPM/LFC and gfal2 is indefinite.<br />
** LFC:<br />
*** Atlas and LHCb both intend to stop using LFC by the end of 2014<br />
*** LFC will still be supported for other VOs, albeit at best-effort.<br />
** GFAL/lcg_util will not be supported after October 2014<br />
* Not planning a major release - in the "major=backward incompatible" sense<br />
<br />
== EMI UI ==<br />
<br />
*UMD-3&nbsp;: 3.0.0 <br />
*EMI-3: 3.0.3 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-ui-2<br />
<br />
== EMI WN ==<br />
<br />
*UMD-3: 3.0.0 <br />
*EMI-3: 3.0.1 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-wn-2<br />
<br />
== EMIR ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**End of security support '''2014-12-31'''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EMI, UMD<br />
** https://github.com/eu-emi/emiregistry<br />
** https://github.com/eu-emi/emir-serp<br />
** https://github.com/eu-emi/emir-web<br />
*Product main web page:<br />
**http://eu-emi.github.io/emiregistry/documentation/registry-1.2.1/emir-manual.html<br />
<br />
== Frontier-Squid == <br />
* UMD-3 : TO-BE-RELEASED - v. 2.7STABLE9-21.1<br />
* Support <br />
** for squid-2.7STABLE9 - end of 2015<br />
** for squid-3.5 to start beginning of 2015<br />
* Release channel:<br />
** cern-frontier: http://frontier.cern.ch/dist/rpms<br />
* Product main web page:<br />
** https://twiki.cern.ch/twiki/bin/view/Frontier/WebHome<br />
** [https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid Installing a Frontier squid cache server]<br />
** [http://frontier.cern.ch/dist/rpms-debug/frontier-squidRELEASE_NOTES Release Notes]<br />
<br />
== FTS3 ==<br />
<br />
*UMD-3&nbsp;: TO-BE-INCLUDED v. 3.2.26<br />
**End of security support ''''''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EPEL, UMD<br />
** http://fts3-service.web.cern.ch/content/downloads<br />
*Product main web page:<br />
**http://fts3-service.web.cern.ch/<br />
<br />
== GFAL/lcg_util ==<br />
<br />
<br />
*UMD-3&nbsp;: 1.16.0 <br />
** will '''not be supported after October 2014'''. It will be replaced by gfal2-util.<br />
<br />
== gLExec-wn ==<br />
<br />
*UMD-3&nbsp;: 1.2.0 <br />
**continued support till at least mid-2015 for gLexec and directly dependencies like LCMAPS, LCAS, SCAS and their modules such as the Argus C-PEP plugin<br />
** we move to a rolling-update model, but do not plan to introduce backward incompatible changes to the ABI or API without officially deprecating the interface at least 11 months in advance<br />
** security bug fixes will not be rolled in with standard updates, but will always be available as individual fixes<br />
** we are willing to coordinate API and ABI interface deprecation time lines with EGI UMD and in coordination with other EMI partners. <br />
<br />
* We are supporting our other components (ARGUS-EES) under the same conditions. <br />
<br />
* All support and maintenance will continue under the Nikhef PDP reference conditions: <br />
** security and critical bug fix support is included,<br />
** any feature requests and any pro-active maintenance needed, provided such a feature or enhancement is also of interest to either the NL-NGI, EGI.eu or a community which is supported by the NL-NGI or Nikhef itself, <br />
** the necessary software distribution and integration services based on standard OS platform distribution mechanisms and packaging formats,<br />
** the regular support scope (documentation, 3rd level incident handling, &c) extends to all communities and users that are affiliated or associated with the NL-NGI, EGI.eu, OSG, or Nikhef itself, and for those communities that also use other "EMI" products or products endorsed by the EGCF. Support also extended to any users that obtain software from EPEL or Debian but only insofar as it concerns security and critical bug fixes. <br />
<br />
* The continued maintenance and support is co-supported by the Dutch National e-Infrastructure, coordinated by SURFsara b.v. Although SURFsara expectes support for the national e-Infrastructure to be sustained through government funding, no formal guarantees can be given. In the unlikely case our support commitment has to change, we will inform EGI and our partners as soon as possible.<br />
<br />
== GridSite ==<br />
<br />
*UMD-3&nbsp;: 2.2.2<br />
** Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== gsoap-gss ==<br />
<br />
*UMD-3&nbsp;: 3.2.0 <br />
** Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== ''jclassads'' ==<br />
<br />
''*UMD-2&nbsp;: 2.4.3 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
''<br />
<br />
== L&amp;B ==<br />
<br />
*UMD-3&nbsp;: 4.0.12<br />
** Maintenance with minor improvements. <br />
** it is currently only used in the Community platform<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== lcg-info-clients ==<br />
<br />
*UMD-3&nbsp;: 1.0.1 <br />
** minor fixes if they are really needed. No new features or major releases for sure. If one day we manage to move to GLUE 2, we will have '''ginfo''' and we would be able to decommission lcg-info-clients. <br />
** lcg-infosites - bug fixes, but won´t implement new features nor publish GLUE 2. <br />
** lcg-info - not supported<br />
* Just as a reminder, both commands can be used for GLUE 1 only. In both cases there haven´t been any modifications in the past two years, I would say. So we shouldn´t expect many changes in any case.<br />
<br />
== MPI ==<br />
<br />
*UMD-3&nbsp;: 1.5.0 <br />
** support is going to be provided. <br />
** Both adding features as requested by users and maintaining the code. <br />
*** In principle it will be done by updating the current major release.<br />
* No plan for retiring the current version. New features will be implemented on this release if no major changes are needed for supporting them.<br />
* will be supported during this year, 2014, for sure. Probably the support will continue next year, but that is still undefined.<br />
* No plan for a new major release<br />
<br />
== ProxyRenewal ==<br />
<br />
*UMD-3&nbsp;: 2.1.3 <br />
**Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== QosCosGrid [QCG] ==<br />
<br />
*UMD-3: 3.2.0 <br />
**Support model: last revision of a released major release <br />
**full support: at least to the end of the year 2015, hopefully longer<br />
**(security) bug fixes: at least to the end of the year 2018, hopefully longer <br />
**new major release (incompatible with the current one) will be released only if it is necessary for some reason. We will try to keep the backwards compatibility of new releases as long as possible.<br />
*Release channels (QCG repository): <br />
*Product main web page: www.qoscosgrid.org<br />
<br />
== SLURM WN config ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== STORM ==<br />
<br />
*UMD-2&nbsp;: 1.10.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.11.x <br />
**End of security support 2015-04-30 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/storm/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/storm/index.html<br />
<br />
== TORQUE server config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0; 1.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.1 <br />
**End of security support 2014-04-30 <br />
* '''NOT supported'''<br />
<br />
== TORQUE WN config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*'''NOT supported'''<br />
<br />
== UNICORE Client6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE Gateway ==<br />
<br />
*UMD-3&nbsp;: UNICORE Gateway6 5.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE HILA ==<br />
<br />
*UMD-3&nbsp;: 2.4.1 <br />
** '''NOT supported'''<br />
<br />
== UNICORE Registry ==<br />
<br />
*UMD-3&nbsp;: UNICORE Registry6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE TSI6 ==<br />
<br />
*UMD-3&nbsp;: 5.1.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE UVOS ==<br />
<br />
*UMD-3&nbsp;: 1.6.0 <br />
** '''NOT supported'''<br />
<br />
== UNICORE XUUDB ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE/X6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== VOMS admin ==<br />
<br />
*UMD-2: 2.7.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: 3.2.0 (2.0.19) <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== VOMS ==<br />
<br />
*UMD-2&nbsp;: 2.0.10 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: Core - 2.0.11 &amp; Clients 3.0.4 <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== WMS ==<br />
<br />
*UMD-2&nbsp;: 3.4.1 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 3.6.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/wms-2<br />
<br />
== yaim-core ==<br />
<br />
*UMD-3&nbsp;: 5.1.1 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== SAGA ==<br />
<br />
*UMD-2&nbsp;: 1.6.1; 1.6.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
== ''Security-Integration'' ==<br />
<br />
''*UMD-2&nbsp;: 2.2.0; 2.2.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:''<br />
<br />
<br />
<br />
== Globus products ==<br />
<br />
=== globus-32-bit ===<br />
<br />
*UMD-3&nbsp;: 5.2.4 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-default-security ===<br />
<br />
*UMD-2&nbsp;: 5.2.1; 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== Globus GRAM5 ===<br />
<br />
*UMD-3&nbsp;: 5.2.5 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GridFTP ===<br />
<br />
*UMD-3&nbsp;: 5.2.5<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GSISSH ===<br />
<br />
*UMD-3&nbsp;: 5.3.10<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-myproxy ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.6.3; 5.9.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== globus-rls ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== GridWay ===<br />
<br />
*UMD-3&nbsp;: 5.14.0 <br />
** is no longer actively maintained. There will be security fixes but no major new release is planned. Therefore, it will NOT be in EGCF release V4.<br />
<br />
=== GridSAFE ===<br />
<br />
* UMD-3&nbsp;: 1.3.1<br />
** is being actively maintained and will be included in the EGCF V4 release. However, user support is only available with limited effort.<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4.<br />
<br />
=== GSI-SSHTerm ===<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**will be maintained in EGCF release 4! <br />
** Maintenance for at least 1 year, however, we assume a much longer maintenance with new features being integrated constantly.<br />
<br />
== NOT in UMD ==<br />
<br />
=== STS & Pseudonymity ===<br />
*Henri Mikkonen (henri.mikkonen@nimbleidm.com)<br />
** can still provide security/bug -fixing support for STS and Pseudonymity, but it should be noted that I'm not funded for this activity<br />
<br />
=== Hydra === <br />
* John White (john.white@cern.ch)<br />
** if there are requests for Hydra I'm happy to fix them. Haven't received anything lately though. I've been adding a Java client to the suite. Once the Java client is tested I'll make a new release.<br />
<br />
<br />
<br />
[[Category:Middleware]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:UMD_products_ID_cards&diff=75484URT:UMD products ID cards2015-01-12T08:05:16Z<p>Bschulle: /* UNICORE Registry6 */</p>
<hr />
<div> {{TOC_right}} <br />
This page reports the main information about the products currently released in UMD: <br />
<br />
*Support calendar for the major releases currently supported <br />
*Preferred release channels to get the future updates<br />
<br />
For every product all the versions released in UMD-2 and UMD-3 are listed, and grouped by the UMD major release. The list of versions is here for the convenience of user and site managers. Only the latest version of a product within an UMD major release is supposed to be updated with bug fixes and security updates. UMD team suggests the resource centres administrators to deploy the latest version of a product available within the UMD major release used in their sites. <br />
<br />
= Products ID cards =<br />
<br />
== AMGA ==<br />
<br />
*UMD-2&nbsp;: 2.3.0 <br />
**End of security support 2014-04-30 <br />
* Planning to continue to take care of maintaining the code in the medium-long term with updates to the current major release.<br />
* Intend to provide standard support.<br />
* No plan for a new major release<br />
<br />
== APEL ==<br />
<br />
*UMD-2&nbsp;: 3.3.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: <br />
** Packages are available on github page: http://apel.github.io/<br />
** Latest version of APEL software is '''1.1.3''' (lib, parsers, client, server) and the SSM messaging software is '''2.1.1'''.<br />
* Planning to continue to support the current version by maintaining the code in the medium to long term. <br />
** There are no major updates planned. New features will be added only as part of our funded work to extend the client to new accounting types. This should not impact the CPU accounting client which we intend to continue to support in its current form.<br />
* We are committing to running the accounting repository service for the '''next 2 years'''. <br />
** In that time, don't expect to make any compatibility-breaking changes to the CPU accounting client. We will be using it as a platform to develop accounting for other usage types. So the main development effort will be in other areas. We will continue to maintain the code as it is the basis for this development in other areas and the accounting repository service that we are providing.<br />
<br />
== ARC ==<br />
<br />
*UMD-2&nbsp;: 2.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.0.1 <br />
**End of security support 2014-04-30 <br />
* The policy of NorduGrid is to have one major release per year. <br />
** We support the current release until the next major release is out. <br />
** Users are then advised to move to the new major release. <br />
** Feature requests are treated in the same way as bugfixes. <br />
* Next major release is planned for '''November 2014''' so 13.11 will be supported until then.<br />
** Backward incompatibilities should always be expected in any ARC major release, but we can't guarantee that we will break backward compatibility in the next major release.<br />
** It will be supported until the next major release, so most likely until end of 2015.<br />
<br />
== ARGUS ==<br />
<br />
*UMD-2&nbsp;: 1.5.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.6.0 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== BDII core ==<br />
<br />
*UMD-2&nbsp;: 1.4.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.5.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Site ==<br />
<br />
*UMD-2&nbsp;: 1.1.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.2.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Top ==<br />
<br />
*UMD-2&nbsp;: 1.0.1; 1.0.2 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.1.X <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BLAH ==<br />
<br />
*UMD-2&nbsp;: 1.18.3 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.20.x <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CANl ==<br />
<br />
*UMD-3&nbsp;: 2.0.7 <br />
** canl-c++ - is part of ARC<br />
=== canl-c ===<br />
*Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
*There are currently no plans to retire EMI-3 products<br />
*No tangible plans for other major releases<br />
<br />
=== canl-java ===<br />
* currently there are two parallel canl-java major releases: <br />
** 1.?.?: in EMI repos and Maven central <br />
** 2.?.?: in Maven central only, i.e. no RPMs/debs.<br />
* Differences: <br />
** 2.x depends on latest BouncyCastle, 1.x on 1.46. <br />
** So far the branches are pretty similar (most of 2.x features and all bugfixes were backported to 1.x). <br />
** No plans nor time to think about moving 2.x to EMI repositories (due to problems with BC - packaging and compatibility).<br />
* Updates to the current major release - yes new major releases - no plans so far (besides 2.x which is already available). The problem is that maintaining a matrix of different canl versions compatible with different BC versions is not possible for me.<br />
* minor features - to the end of 2014. Bigger developments won't be included.<br />
* standard support - to the end of 2014, but if needed it can be prolonged.<br />
* security support - to the end of 2014<br />
* no major release planned (besides 2.x which are different wrt to BC dependency).<br />
** 2.x are backwards incompatible due to conflicting dependency usage.<br />
<br />
== Cluster ==<br />
<br />
*UMD-2&nbsp;: 2.0.0 <br />
**End of security support 2014-04-30 <br />
* UMD-3: v. 1.15.1<br />
* Product '''NO LONGER SUPPORTED'''<br />
<br />
== CREAM ==<br />
<br />
*UMD-2&nbsp;: 1.14.4 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 1.16.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
**Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM LSF module ==<br />
<br />
* EMI-3&nbsp;: 2.2.1 <br />
* The current release of 2.2.1 is out of date and should be updated to 2.3.7-1 in UMD-3 as soon as possible. This is the latest version which is available in github. <br />
* After that - only provide bug fix releases.<br />
* The info-dynamic-scheduler-lsf is supported at best effort basis. We will continue to do so as long as we need it ourselves, that is as long as we run CREAM CEs with LSF. Currently, there is no plan to retire these CEs yet.<br />
* No major release planned.<br />
<br />
== CREAM (S)GE module ==<br />
<br />
*UMD-3&nbsp;: 2.1.0 <br />
** best effort support<br />
** End of Full Support: 2014-04-30<br />
** End of Standard Updates: 2014-10-30<br />
** End of Security Updates & EOL: 2015-04-30<br />
* New major release:<br />
**Probably in 2015<br />
<br />
== CREAM SLURM module ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM Torque module ==<br />
<br />
*UMD-2&nbsp;: 2.0.2 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 2.1.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== dCache-srmclient ==<br />
<br />
*UMD-3&nbsp;: 2.2.22<br />
**The client will be supported as long as needed and have no new version. However, there is available a 2.6.12-1 srm-client release, which however needs Java 7 on runtime.<br />
<br />
== DCACHE ==<br />
<br />
*UMD-3: 2.2.22 <br />
** support the dCache server 2.6 branch until at least end of April 2015<br />
* new golden release 2.10 in July, this, as always will then be supported for two years<br />
* golden releases are often backward incompatible<br />
** Within golden releases we try not to implement new features to keep them stable<br />
** do not differentiate between standard support and security support only, if it is supported, it is supported.<br />
* support calendar: http://www.dcache.org/downloads/1.9/index.shtml<br />
<br />
== DPM/LFC ==<br />
<br />
*UMD-3&nbsp;: 1.8.8<br />
*Support for DPM/LFC and gfal2 is indefinite.<br />
** LFC:<br />
*** Atlas and LHCb both intend to stop using LFC by the end of 2014<br />
*** LFC will still be supported for other VOs, albeit at best-effort.<br />
** GFAL/lcg_util will not be supported after October 2014<br />
* Not planning a major release - in the "major=backward incompatible" sense<br />
<br />
== EMI UI ==<br />
<br />
*UMD-3&nbsp;: 3.0.0 <br />
*EMI-3: 3.0.3 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-ui-2<br />
<br />
== EMI WN ==<br />
<br />
*UMD-3: 3.0.0 <br />
*EMI-3: 3.0.1 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-wn-2<br />
<br />
== EMIR ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**End of security support '''2014-12-31'''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EMI, UMD<br />
** https://github.com/eu-emi/emiregistry<br />
** https://github.com/eu-emi/emir-serp<br />
** https://github.com/eu-emi/emir-web<br />
*Product main web page:<br />
**http://eu-emi.github.io/emiregistry/documentation/registry-1.2.1/emir-manual.html<br />
<br />
== Frontier-Squid == <br />
* UMD-3 : TO-BE-RELEASED - v. 2.7STABLE9-21.1<br />
* Support <br />
** for squid-2.7STABLE9 - end of 2015<br />
** for squid-3.5 to start beginning of 2015<br />
* Release channel:<br />
** cern-frontier: http://frontier.cern.ch/dist/rpms<br />
* Product main web page:<br />
** https://twiki.cern.ch/twiki/bin/view/Frontier/WebHome<br />
** [https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid Installing a Frontier squid cache server]<br />
** [http://frontier.cern.ch/dist/rpms-debug/frontier-squidRELEASE_NOTES Release Notes]<br />
<br />
== FTS3 ==<br />
<br />
*UMD-3&nbsp;: TO-BE-INCLUDED v. 3.2.26<br />
**End of security support ''''''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EPEL, UMD<br />
** http://fts3-service.web.cern.ch/content/downloads<br />
*Product main web page:<br />
**http://fts3-service.web.cern.ch/<br />
<br />
== GFAL/lcg_util ==<br />
<br />
<br />
*UMD-3&nbsp;: 1.16.0 <br />
** will '''not be supported after October 2014'''. It will be replaced by gfal2-util.<br />
<br />
== gLExec-wn ==<br />
<br />
*UMD-3&nbsp;: 1.2.0 <br />
**continued support till at least mid-2015 for gLexec and directly dependencies like LCMAPS, LCAS, SCAS and their modules such as the Argus C-PEP plugin<br />
** we move to a rolling-update model, but do not plan to introduce backward incompatible changes to the ABI or API without officially deprecating the interface at least 11 months in advance<br />
** security bug fixes will not be rolled in with standard updates, but will always be available as individual fixes<br />
** we are willing to coordinate API and ABI interface deprecation time lines with EGI UMD and in coordination with other EMI partners. <br />
<br />
* We are supporting our other components (ARGUS-EES) under the same conditions. <br />
<br />
* All support and maintenance will continue under the Nikhef PDP reference conditions: <br />
** security and critical bug fix support is included,<br />
** any feature requests and any pro-active maintenance needed, provided such a feature or enhancement is also of interest to either the NL-NGI, EGI.eu or a community which is supported by the NL-NGI or Nikhef itself, <br />
** the necessary software distribution and integration services based on standard OS platform distribution mechanisms and packaging formats,<br />
** the regular support scope (documentation, 3rd level incident handling, &c) extends to all communities and users that are affiliated or associated with the NL-NGI, EGI.eu, OSG, or Nikhef itself, and for those communities that also use other "EMI" products or products endorsed by the EGCF. Support also extended to any users that obtain software from EPEL or Debian but only insofar as it concerns security and critical bug fixes. <br />
<br />
* The continued maintenance and support is co-supported by the Dutch National e-Infrastructure, coordinated by SURFsara b.v. Although SURFsara expectes support for the national e-Infrastructure to be sustained through government funding, no formal guarantees can be given. In the unlikely case our support commitment has to change, we will inform EGI and our partners as soon as possible.<br />
<br />
== GridSite ==<br />
<br />
*UMD-3&nbsp;: 2.2.2<br />
** Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== gsoap-gss ==<br />
<br />
*UMD-3&nbsp;: 3.2.0 <br />
** Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== ''jclassads'' ==<br />
<br />
''*UMD-2&nbsp;: 2.4.3 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
''<br />
<br />
== L&amp;B ==<br />
<br />
*UMD-3&nbsp;: 4.0.12<br />
** Maintenance with minor improvements. <br />
** it is currently only used in the Community platform<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== lcg-info-clients ==<br />
<br />
*UMD-3&nbsp;: 1.0.1 <br />
** minor fixes if they are really needed. No new features or major releases for sure. If one day we manage to move to GLUE 2, we will have '''ginfo''' and we would be able to decommission lcg-info-clients. <br />
** lcg-infosites - bug fixes, but won´t implement new features nor publish GLUE 2. <br />
** lcg-info - not supported<br />
* Just as a reminder, both commands can be used for GLUE 1 only. In both cases there haven´t been any modifications in the past two years, I would say. So we shouldn´t expect many changes in any case.<br />
<br />
== MPI ==<br />
<br />
*UMD-3&nbsp;: 1.5.0 <br />
** support is going to be provided. <br />
** Both adding features as requested by users and maintaining the code. <br />
*** In principle it will be done by updating the current major release.<br />
* No plan for retiring the current version. New features will be implemented on this release if no major changes are needed for supporting them.<br />
* will be supported during this year, 2014, for sure. Probably the support will continue next year, but that is still undefined.<br />
* No plan for a new major release<br />
<br />
== ProxyRenewal ==<br />
<br />
*UMD-3&nbsp;: 2.1.3 <br />
**Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== QosCosGrid [QCG] ==<br />
<br />
*UMD-3: 3.2.0 <br />
**Support model: last revision of a released major release <br />
**full support: at least to the end of the year 2015, hopefully longer<br />
**(security) bug fixes: at least to the end of the year 2018, hopefully longer <br />
**new major release (incompatible with the current one) will be released only if it is necessary for some reason. We will try to keep the backwards compatibility of new releases as long as possible.<br />
*Release channels (QCG repository): <br />
*Product main web page: www.qoscosgrid.org<br />
<br />
== SLURM WN config ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== STORM ==<br />
<br />
*UMD-2&nbsp;: 1.10.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.11.x <br />
**End of security support 2015-04-30 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/storm/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/storm/index.html<br />
<br />
== TORQUE server config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0; 1.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.1 <br />
**End of security support 2014-04-30 <br />
* '''NOT supported'''<br />
<br />
== TORQUE WN config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*'''NOT supported'''<br />
<br />
== UNICORE Client6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE Gateway ==<br />
<br />
*UMD-3&nbsp;: 5.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE HILA ==<br />
<br />
*UMD-3&nbsp;: 2.4.1 <br />
** '''NOT supported'''<br />
<br />
== UNICORE Registry ==<br />
<br />
*UMD-3&nbsp;: UNICORE Registry6 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE TSI6 ==<br />
<br />
*UMD-3&nbsp;: 5.1.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE UVOS ==<br />
<br />
*UMD-3&nbsp;: 1.6.0 <br />
** '''NOT supported'''<br />
<br />
== UNICORE XUUDB ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE/X6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== VOMS admin ==<br />
<br />
*UMD-2: 2.7.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: 3.2.0 (2.0.19) <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== VOMS ==<br />
<br />
*UMD-2&nbsp;: 2.0.10 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: Core - 2.0.11 &amp; Clients 3.0.4 <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== WMS ==<br />
<br />
*UMD-2&nbsp;: 3.4.1 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 3.6.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/wms-2<br />
<br />
== yaim-core ==<br />
<br />
*UMD-3&nbsp;: 5.1.1 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== SAGA ==<br />
<br />
*UMD-2&nbsp;: 1.6.1; 1.6.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
== ''Security-Integration'' ==<br />
<br />
''*UMD-2&nbsp;: 2.2.0; 2.2.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:''<br />
<br />
<br />
<br />
== Globus products ==<br />
<br />
=== globus-32-bit ===<br />
<br />
*UMD-3&nbsp;: 5.2.4 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-default-security ===<br />
<br />
*UMD-2&nbsp;: 5.2.1; 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== Globus GRAM5 ===<br />
<br />
*UMD-3&nbsp;: 5.2.5 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GridFTP ===<br />
<br />
*UMD-3&nbsp;: 5.2.5<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GSISSH ===<br />
<br />
*UMD-3&nbsp;: 5.3.10<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-myproxy ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.6.3; 5.9.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== globus-rls ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== GridWay ===<br />
<br />
*UMD-3&nbsp;: 5.14.0 <br />
** is no longer actively maintained. There will be security fixes but no major new release is planned. Therefore, it will NOT be in EGCF release V4.<br />
<br />
=== GridSAFE ===<br />
<br />
* UMD-3&nbsp;: 1.3.1<br />
** is being actively maintained and will be included in the EGCF V4 release. However, user support is only available with limited effort.<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4.<br />
<br />
=== GSI-SSHTerm ===<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**will be maintained in EGCF release 4! <br />
** Maintenance for at least 1 year, however, we assume a much longer maintenance with new features being integrated constantly.<br />
<br />
== NOT in UMD ==<br />
<br />
=== STS & Pseudonymity ===<br />
*Henri Mikkonen (henri.mikkonen@nimbleidm.com)<br />
** can still provide security/bug -fixing support for STS and Pseudonymity, but it should be noted that I'm not funded for this activity<br />
<br />
=== Hydra === <br />
* John White (john.white@cern.ch)<br />
** if there are requests for Hydra I'm happy to fix them. Haven't received anything lately though. I've been adding a Java client to the suite. Once the Java client is tested I'll make a new release.<br />
<br />
<br />
<br />
[[Category:Middleware]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:UMD_products_ID_cards&diff=75483URT:UMD products ID cards2015-01-12T08:04:03Z<p>Bschulle: /* UNICORE Gateway */</p>
<hr />
<div> {{TOC_right}} <br />
This page reports the main information about the products currently released in UMD: <br />
<br />
*Support calendar for the major releases currently supported <br />
*Preferred release channels to get the future updates<br />
<br />
For every product all the versions released in UMD-2 and UMD-3 are listed, and grouped by the UMD major release. The list of versions is here for the convenience of user and site managers. Only the latest version of a product within an UMD major release is supposed to be updated with bug fixes and security updates. UMD team suggests the resource centres administrators to deploy the latest version of a product available within the UMD major release used in their sites. <br />
<br />
= Products ID cards =<br />
<br />
== AMGA ==<br />
<br />
*UMD-2&nbsp;: 2.3.0 <br />
**End of security support 2014-04-30 <br />
* Planning to continue to take care of maintaining the code in the medium-long term with updates to the current major release.<br />
* Intend to provide standard support.<br />
* No plan for a new major release<br />
<br />
== APEL ==<br />
<br />
*UMD-2&nbsp;: 3.3.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: <br />
** Packages are available on github page: http://apel.github.io/<br />
** Latest version of APEL software is '''1.1.3''' (lib, parsers, client, server) and the SSM messaging software is '''2.1.1'''.<br />
* Planning to continue to support the current version by maintaining the code in the medium to long term. <br />
** There are no major updates planned. New features will be added only as part of our funded work to extend the client to new accounting types. This should not impact the CPU accounting client which we intend to continue to support in its current form.<br />
* We are committing to running the accounting repository service for the '''next 2 years'''. <br />
** In that time, don't expect to make any compatibility-breaking changes to the CPU accounting client. We will be using it as a platform to develop accounting for other usage types. So the main development effort will be in other areas. We will continue to maintain the code as it is the basis for this development in other areas and the accounting repository service that we are providing.<br />
<br />
== ARC ==<br />
<br />
*UMD-2&nbsp;: 2.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.0.1 <br />
**End of security support 2014-04-30 <br />
* The policy of NorduGrid is to have one major release per year. <br />
** We support the current release until the next major release is out. <br />
** Users are then advised to move to the new major release. <br />
** Feature requests are treated in the same way as bugfixes. <br />
* Next major release is planned for '''November 2014''' so 13.11 will be supported until then.<br />
** Backward incompatibilities should always be expected in any ARC major release, but we can't guarantee that we will break backward compatibility in the next major release.<br />
** It will be supported until the next major release, so most likely until end of 2015.<br />
<br />
== ARGUS ==<br />
<br />
*UMD-2&nbsp;: 1.5.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.6.0 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== BDII core ==<br />
<br />
*UMD-2&nbsp;: 1.4.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.5.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Site ==<br />
<br />
*UMD-2&nbsp;: 1.1.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.2.0 <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BDII Top ==<br />
<br />
*UMD-2&nbsp;: 1.0.1; 1.0.2 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.1.X <br />
* Support for the BDII is guaranteed. <br />
* For the time being, there aren't any plans for a new major release. If bug fixes or security vulnerabilities are discovered, they will be fixed.<br />
* BDII codebase has been the same for EMI 2 and EMI 3, and as there are no new features planned, we can expect a long support of the existing versions.<br />
<br />
== BLAH ==<br />
<br />
*UMD-2&nbsp;: 1.18.3 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.20.x <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CANl ==<br />
<br />
*UMD-3&nbsp;: 2.0.7 <br />
** canl-c++ - is part of ARC<br />
=== canl-c ===<br />
*Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
*There are currently no plans to retire EMI-3 products<br />
*No tangible plans for other major releases<br />
<br />
=== canl-java ===<br />
* currently there are two parallel canl-java major releases: <br />
** 1.?.?: in EMI repos and Maven central <br />
** 2.?.?: in Maven central only, i.e. no RPMs/debs.<br />
* Differences: <br />
** 2.x depends on latest BouncyCastle, 1.x on 1.46. <br />
** So far the branches are pretty similar (most of 2.x features and all bugfixes were backported to 1.x). <br />
** No plans nor time to think about moving 2.x to EMI repositories (due to problems with BC - packaging and compatibility).<br />
* Updates to the current major release - yes new major releases - no plans so far (besides 2.x which is already available). The problem is that maintaining a matrix of different canl versions compatible with different BC versions is not possible for me.<br />
* minor features - to the end of 2014. Bigger developments won't be included.<br />
* standard support - to the end of 2014, but if needed it can be prolonged.<br />
* security support - to the end of 2014<br />
* no major release planned (besides 2.x which are different wrt to BC dependency).<br />
** 2.x are backwards incompatible due to conflicting dependency usage.<br />
<br />
== Cluster ==<br />
<br />
*UMD-2&nbsp;: 2.0.0 <br />
**End of security support 2014-04-30 <br />
* UMD-3: v. 1.15.1<br />
* Product '''NO LONGER SUPPORTED'''<br />
<br />
== CREAM ==<br />
<br />
*UMD-2&nbsp;: 1.14.4 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 1.16.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
**Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM LSF module ==<br />
<br />
* EMI-3&nbsp;: 2.2.1 <br />
* The current release of 2.2.1 is out of date and should be updated to 2.3.7-1 in UMD-3 as soon as possible. This is the latest version which is available in github. <br />
* After that - only provide bug fix releases.<br />
* The info-dynamic-scheduler-lsf is supported at best effort basis. We will continue to do so as long as we need it ourselves, that is as long as we run CREAM CEs with LSF. Currently, there is no plan to retire these CEs yet.<br />
* No major release planned.<br />
<br />
== CREAM (S)GE module ==<br />
<br />
*UMD-3&nbsp;: 2.1.0 <br />
** best effort support<br />
** End of Full Support: 2014-04-30<br />
** End of Standard Updates: 2014-10-30<br />
** End of Security Updates & EOL: 2015-04-30<br />
* New major release:<br />
**Probably in 2015<br />
<br />
== CREAM SLURM module ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== CREAM Torque module ==<br />
<br />
*UMD-2&nbsp;: 2.0.2 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 2.1.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== dCache-srmclient ==<br />
<br />
*UMD-3&nbsp;: 2.2.22<br />
**The client will be supported as long as needed and have no new version. However, there is available a 2.6.12-1 srm-client release, which however needs Java 7 on runtime.<br />
<br />
== DCACHE ==<br />
<br />
*UMD-3: 2.2.22 <br />
** support the dCache server 2.6 branch until at least end of April 2015<br />
* new golden release 2.10 in July, this, as always will then be supported for two years<br />
* golden releases are often backward incompatible<br />
** Within golden releases we try not to implement new features to keep them stable<br />
** do not differentiate between standard support and security support only, if it is supported, it is supported.<br />
* support calendar: http://www.dcache.org/downloads/1.9/index.shtml<br />
<br />
== DPM/LFC ==<br />
<br />
*UMD-3&nbsp;: 1.8.8<br />
*Support for DPM/LFC and gfal2 is indefinite.<br />
** LFC:<br />
*** Atlas and LHCb both intend to stop using LFC by the end of 2014<br />
*** LFC will still be supported for other VOs, albeit at best-effort.<br />
** GFAL/lcg_util will not be supported after October 2014<br />
* Not planning a major release - in the "major=backward incompatible" sense<br />
<br />
== EMI UI ==<br />
<br />
*UMD-3&nbsp;: 3.0.0 <br />
*EMI-3: 3.0.3 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-ui-2<br />
<br />
== EMI WN ==<br />
<br />
*UMD-3: 3.0.0 <br />
*EMI-3: 3.0.1 <br />
**End of security support 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/emi-wn-2<br />
<br />
== EMIR ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**End of security support '''2014-12-31'''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EMI, UMD<br />
** https://github.com/eu-emi/emiregistry<br />
** https://github.com/eu-emi/emir-serp<br />
** https://github.com/eu-emi/emir-web<br />
*Product main web page:<br />
**http://eu-emi.github.io/emiregistry/documentation/registry-1.2.1/emir-manual.html<br />
<br />
== Frontier-Squid == <br />
* UMD-3 : TO-BE-RELEASED - v. 2.7STABLE9-21.1<br />
* Support <br />
** for squid-2.7STABLE9 - end of 2015<br />
** for squid-3.5 to start beginning of 2015<br />
* Release channel:<br />
** cern-frontier: http://frontier.cern.ch/dist/rpms<br />
* Product main web page:<br />
** https://twiki.cern.ch/twiki/bin/view/Frontier/WebHome<br />
** [https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid Installing a Frontier squid cache server]<br />
** [http://frontier.cern.ch/dist/rpms-debug/frontier-squidRELEASE_NOTES Release Notes]<br />
<br />
== FTS3 ==<br />
<br />
*UMD-3&nbsp;: TO-BE-INCLUDED v. 3.2.26<br />
**End of security support ''''''<br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
** EPEL, UMD<br />
** http://fts3-service.web.cern.ch/content/downloads<br />
*Product main web page:<br />
**http://fts3-service.web.cern.ch/<br />
<br />
== GFAL/lcg_util ==<br />
<br />
<br />
*UMD-3&nbsp;: 1.16.0 <br />
** will '''not be supported after October 2014'''. It will be replaced by gfal2-util.<br />
<br />
== gLExec-wn ==<br />
<br />
*UMD-3&nbsp;: 1.2.0 <br />
**continued support till at least mid-2015 for gLexec and directly dependencies like LCMAPS, LCAS, SCAS and their modules such as the Argus C-PEP plugin<br />
** we move to a rolling-update model, but do not plan to introduce backward incompatible changes to the ABI or API without officially deprecating the interface at least 11 months in advance<br />
** security bug fixes will not be rolled in with standard updates, but will always be available as individual fixes<br />
** we are willing to coordinate API and ABI interface deprecation time lines with EGI UMD and in coordination with other EMI partners. <br />
<br />
* We are supporting our other components (ARGUS-EES) under the same conditions. <br />
<br />
* All support and maintenance will continue under the Nikhef PDP reference conditions: <br />
** security and critical bug fix support is included,<br />
** any feature requests and any pro-active maintenance needed, provided such a feature or enhancement is also of interest to either the NL-NGI, EGI.eu or a community which is supported by the NL-NGI or Nikhef itself, <br />
** the necessary software distribution and integration services based on standard OS platform distribution mechanisms and packaging formats,<br />
** the regular support scope (documentation, 3rd level incident handling, &c) extends to all communities and users that are affiliated or associated with the NL-NGI, EGI.eu, OSG, or Nikhef itself, and for those communities that also use other "EMI" products or products endorsed by the EGCF. Support also extended to any users that obtain software from EPEL or Debian but only insofar as it concerns security and critical bug fixes. <br />
<br />
* The continued maintenance and support is co-supported by the Dutch National e-Infrastructure, coordinated by SURFsara b.v. Although SURFsara expectes support for the national e-Infrastructure to be sustained through government funding, no formal guarantees can be given. In the unlikely case our support commitment has to change, we will inform EGI and our partners as soon as possible.<br />
<br />
== GridSite ==<br />
<br />
*UMD-3&nbsp;: 2.2.2<br />
** Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform. <br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== gsoap-gss ==<br />
<br />
*UMD-3&nbsp;: 3.2.0 <br />
** Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
* Backaward incompatible changes:<br />
** As far as we can foresee, there would be no incompatibilities at protocol level. There could be incompatibilities at binary level. By that, I mean that products using our *libraries* would have to be rebuilt with the new major version, but old clients communicating with new servers, or vice versa, would have no issues.<br />
<br />
== ''jclassads'' ==<br />
<br />
''*UMD-2&nbsp;: 2.4.3 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
''<br />
<br />
== L&amp;B ==<br />
<br />
*UMD-3&nbsp;: 4.0.12<br />
** Maintenance with minor improvements. <br />
** it is currently only used in the Community platform<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== lcg-info-clients ==<br />
<br />
*UMD-3&nbsp;: 1.0.1 <br />
** minor fixes if they are really needed. No new features or major releases for sure. If one day we manage to move to GLUE 2, we will have '''ginfo''' and we would be able to decommission lcg-info-clients. <br />
** lcg-infosites - bug fixes, but won´t implement new features nor publish GLUE 2. <br />
** lcg-info - not supported<br />
* Just as a reminder, both commands can be used for GLUE 1 only. In both cases there haven´t been any modifications in the past two years, I would say. So we shouldn´t expect many changes in any case.<br />
<br />
== MPI ==<br />
<br />
*UMD-3&nbsp;: 1.5.0 <br />
** support is going to be provided. <br />
** Both adding features as requested by users and maintaining the code. <br />
*** In principle it will be done by updating the current major release.<br />
* No plan for retiring the current version. New features will be implemented on this release if no major changes are needed for supporting them.<br />
* will be supported during this year, 2014, for sure. Probably the support will continue next year, but that is still undefined.<br />
* No plan for a new major release<br />
<br />
== ProxyRenewal ==<br />
<br />
*UMD-3&nbsp;: 2.1.3 <br />
**Reactive maintenance<br />
* There are currently no plans to retire EMI-3 products<br />
* No tangible plans for other major releases<br />
<br />
== QosCosGrid [QCG] ==<br />
<br />
*UMD-3: 3.2.0 <br />
**Support model: last revision of a released major release <br />
**full support: at least to the end of the year 2015, hopefully longer<br />
**(security) bug fixes: at least to the end of the year 2018, hopefully longer <br />
**new major release (incompatible with the current one) will be released only if it is necessary for some reason. We will try to keep the backwards compatibility of new releases as long as possible.<br />
*Release channels (QCG repository): <br />
*Product main web page: www.qoscosgrid.org<br />
<br />
== SLURM WN config ==<br />
<br />
*EMI-3&nbsp;: 1.0.0 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI3<br />
<br />
== STORM ==<br />
<br />
*UMD-2&nbsp;: 1.10.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.11.x <br />
**End of security support 2015-04-30 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/storm/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/storm/index.html<br />
<br />
== TORQUE server config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0; 1.0.1 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.1 <br />
**End of security support 2014-04-30 <br />
* '''NOT supported'''<br />
<br />
== TORQUE WN config ==<br />
<br />
*UMD-2&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 1.0.0 <br />
**End of security support 2014-04-30 <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*'''NOT supported'''<br />
<br />
== UNICORE Client6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE Gateway ==<br />
<br />
*UMD-3&nbsp;: 5.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** Version 7.2.0 (released via UMD)<br />
** No backward incompatibilities<br />
** To be released in January 2015<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE HILA ==<br />
<br />
*UMD-3&nbsp;: 2.4.1 <br />
** '''NOT supported'''<br />
<br />
== UNICORE Registry6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE TSI6 ==<br />
<br />
*UMD-3&nbsp;: 5.1.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE UVOS ==<br />
<br />
*UMD-3&nbsp;: 1.6.0 <br />
** '''NOT supported'''<br />
<br />
== UNICORE XUUDB ==<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== UNICORE/X6 ==<br />
<br />
*UMD-3&nbsp;: 6.0.0 <br />
** Full support (new features) – by April 2014<br />
** Standard support (bug fixes) & Security support (security vulberability fixes) – until the end of 2014<br />
* New major release:<br />
** we already are working on releasing the next major release (UNICORE 7) in EGI / UMD.<br />
** No backward incompatibilities<br />
** To be released in July 2014<br />
** we plan to fully support UNICORE 7 at least until end of 2015, by which time the next major release should be available. Critical security fixes will be provided after that date, if required.<br />
<br />
== VOMS admin ==<br />
<br />
*UMD-2: 2.7.0 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: 3.2.0 (2.0.19) <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== VOMS ==<br />
<br />
*UMD-2&nbsp;: 2.0.10 <br />
**End of security support 2014-04-30 <br />
*UMD-3&nbsp;: 3.1.0 (2.0.11) <br />
*EMI-3: Core - 2.0.11 &amp; Clients 3.0.4 <br />
*Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**PT repos: http://italiangrid.github.io/voms/download.html <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://italiangrid.github.io/voms/index.html<br />
<br />
== WMS ==<br />
<br />
*UMD-2&nbsp;: 3.4.1 <br />
**End of security support 2014-04-30 <br />
*EMI-3&nbsp;: 3.6.2 <br />
**Support calendar: <br />
***End of Full Support: 2014-04-30 <br />
***End of Standard Updates: 2014-10-30 <br />
***End of Security Updates &amp; EOL: 2015-04-30 <br />
*'''Next major release will be supported after 2015''' <br />
*Support model: last revision of a released major release <br />
*Release channels: <br />
**EMI repos: http://emisoft.web.cern.ch/emisoft/ <br />
*Product main web page: <br />
**http://www.eu-emi.eu/releases/emi-3-montebianco/products/-/asset_publisher/5dKm/content/wms-2<br />
<br />
== yaim-core ==<br />
<br />
*UMD-3&nbsp;: 5.1.1 <br />
**End of security support 2014-04-30 <br />
*Release channels (e.g. EMI repos, EPEL repos..): <br />
*Product main web page:<br />
<br />
== SAGA ==<br />
<br />
*UMD-2&nbsp;: 1.6.1; 1.6.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
== ''Security-Integration'' ==<br />
<br />
''*UMD-2&nbsp;: 2.2.0; 2.2.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:''<br />
<br />
<br />
<br />
== Globus products ==<br />
<br />
=== globus-32-bit ===<br />
<br />
*UMD-3&nbsp;: 5.2.4 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-default-security ===<br />
<br />
*UMD-2&nbsp;: 5.2.1; 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== Globus GRAM5 ===<br />
<br />
*UMD-3&nbsp;: 5.2.5 <br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GridFTP ===<br />
<br />
*UMD-3&nbsp;: 5.2.5<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== Globus GSISSH ===<br />
<br />
*UMD-3&nbsp;: 5.3.10<br />
** will all be maintained in EGCF release 4!<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4<br />
<br />
=== globus-myproxy ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.6.3; 5.9.1 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== globus-rls ===<br />
TOREMOVE<br />
*UMD-2&nbsp;: 5.2.2 <br />
**End of security support&nbsp;????-??-?? <br />
*Reelase channels (e.g. EPEL repos, IGE repos..): <br />
*Product main web page:<br />
<br />
=== GridWay ===<br />
<br />
*UMD-3&nbsp;: 5.14.0 <br />
** is no longer actively maintained. There will be security fixes but no major new release is planned. Therefore, it will NOT be in EGCF release V4.<br />
<br />
=== GridSAFE ===<br />
<br />
* UMD-3&nbsp;: 1.3.1<br />
** is being actively maintained and will be included in the EGCF V4 release. However, user support is only available with limited effort.<br />
* A new major release of the Globus tools, GT6, will be coming out within a month or two. EGCF will package this new release as 4.0 to reflect this change from upstream. <br />
** HOWEVER: the GT6 release WILL be backwards compatible with GT5! Therefore, we will NOT continue to add new features to EGCF release V3 but instead go with EGCF release V4.<br />
<br />
=== GSI-SSHTerm ===<br />
<br />
*UMD-3&nbsp;: 2.0.0 <br />
**will be maintained in EGCF release 4! <br />
** Maintenance for at least 1 year, however, we assume a much longer maintenance with new features being integrated constantly.<br />
<br />
== NOT in UMD ==<br />
<br />
=== STS & Pseudonymity ===<br />
*Henri Mikkonen (henri.mikkonen@nimbleidm.com)<br />
** can still provide security/bug -fixing support for STS and Pseudonymity, but it should be noted that I'm not funded for this activity<br />
<br />
=== Hydra === <br />
* John White (john.white@cern.ch)<br />
** if there are requests for Hydra I'm happy to fix them. Haven't received anything lately though. I've been adding a Java client to the suite. Once the Java client is tested I'll make a new release.<br />
<br />
<br />
<br />
[[Category:Middleware]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=Agenda-05-01-2015&diff=75264Agenda-05-01-20152015-01-09T11:50:54Z<p>Bschulle: /* UNICORE */</p>
<hr />
<div>{|<br />
|-<br />
| [http://connect.ct.infn.it/egi-inspire-sa1-ter/ '''Adobe connect''' direct link]<br />
| ''Conference system is on adobe connect, no password required. <br />
|}<br />
<br />
{{TOC right}}<br />
<br />
= UMD releases status =<br />
<br />
== Status of the products verification/staged rollout ==<br />
<br />
<br />
=== Released ===<br />
* Last release UMD<br />
<br />
=== Under Staged Rollout ===<br />
<br />
<br />
* cream-torque v. 2.1.4<br />
<br />
* glexec-wn v. 1.3.0<br />
<br />
=== In Verification ===<br />
<br />
* cream-ge v. 2.3.0<br />
* qcg-computing-3.4.0 (only SL6)<br />
* qcg-notifications-3.4.0 (only SL6)<br />
* squid v. 2.7.19<br />
* fts3 v. 3.2.27<br />
* voms-clients v. 3.0.5<br />
* voms-admin v. 2.0.12<br />
* apel v. 1.3.1<br />
* px v. 1.3.36<br />
* DPM 1.8.9 <br />
* wms-ice v. 3.5.4<br />
* Globus 6.0.0 products: Gridftp, Globus-Default-Security, Gram5, MyProxy;<br />
<br />
'''Ready to be released:'''<br />
<br />
* cream v. 1.16.4<br />
<br />
=== Rejected ===<br />
<br />
* -----<br />
<br />
== Timeline for the next UMD updates ==<br />
* Mid December<br />
<br />
= Updates from the product teams =<br />
This section is directly contributed by the product teams. Please, add under your section the scheduled releases with a short comment about the updates introduced and where they are going to be released (EMI repositories, EPEL, private repositories ecc), linking external pages with these information is ok, but please add at least the expected date of the next release. It is important to discuss, within the URT, changes that may affect directly or indirectly other products. The text will be copied into the agenda of the next URT meeting, PT will just need to check that all the information are up to date.<br />
Please, feel free to alter the template if it doesn't feet with your needs.<br />
<br />
== APEL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== ARC ==<br />
* Release version 5.0.0 Expected: 2015-01-yy<br />
** Main changes: (including other products affected)<br />
*** Removal of old components:<br />
**** arc-ur-logger (replaced with Jura)<br />
**** LFC DMC<br />
**** DQ2 DMC<br />
**** old data staging<br />
**** Confusa (abandoned prototype)<br />
**** arcmigrate cli tool<br />
**** arcslcs<br />
**** SAML service<br />
**** gridsite dependency<br />
** Other information:<br />
<br />
== Argus ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
<br />
== dCache ==<br />
* Release version 2.6.38 Expected: next UMD release<br />
** Main changes: see appdb<br />
** Other information:<br />
<br />
== BDII ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== DPM/LFC ==<br />
* DPM <br />
** DPM/LFC 1.8.9 are in epel stable since last week<br />
** https://svnweb.cern.ch/trac/lcgdm/blog/dpm_1.8.9_relnotes<br />
** a fix for a bug on the latest dmlite component part of DPM 1.8.9 has been released and and it's already in EPEL stable<br />
** https://svnweb.cern.ch/trac/lcgdm/attachment/wiki/Dpm/dmlite0.7.2-relnotes.txt<br />
** First tests with CentOS7 using components from EPEL7, some issues found, but most of the components are working out of the box<br />
<br />
== GFAL/lcg_utils ==<br />
* The CERN Data Management Clients publish their releases here: http://dmc.web.cern.ch/releases<br />
* A new page with all releases and they status is available at https://dmc-docs.web.cern.ch/dmc-docs/<br />
* New in EPEL<br />
** gfal2 2.7.8 <br />
** gfal2-python 1.6.0 <br />
** gfal2-util 1.1.0 <br />
** srm-ifce 1.20.14<br />
** CGSI-gSOAP 1.3.7<br />
<br />
* CERN-PROD is available for staged rollout<br />
<br />
== FTS ==<br />
* FTS3 EPEL update released, v 3.2.26<br />
* new FTS3 v. 3.2.30 in Epel-testing<br />
<br />
== Frontier-Squid == <br />
* Release version: 2.7STABLE9-21.1; Released: 2014-12-03 - <br />
** Main changes: http://frontier.cern.ch/dist/rpms/frontier-squidRELEASE_NOTES<br />
*** Mainly improves multiple squid support, increasing max from 4 to 16 squids and limiting each squid to a share of available file descriptors<br />
** Other information (repository): http://frontier.cern.ch/dist/rpms<br />
<br />
== EMIR ==<br />
* Release version: ; Expected:<br />
** Main changes: <br />
** Other information:<br />
<br />
== UNICORE ==<br />
(expected in the course of 2015 that we will publish packages for UMD via AppDB at https://appdb.egi.eu/store/software/unicore<br />
<br />
For now, packages for UNICORE 7.2.0 can be downloaded from<br />
<br />
Debian:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/deb<br />
<br />
RPM:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/rpm<br />
<br />
RPM packages were tested on Centos 6, so SL6 will be fine. SL5 is NOT supported <br />
any more.<br />
<br />
Changes are listed with respect to the last UNICORE version available in UMD <br />
which is 6.6.0<br />
<br />
* UNICORE/X 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** Product name is "unicore-unicorex"<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** RESTful API in addition to the SOAP/WS API<br />
*** Many performance improvements<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.pdf<br />
<br />
* TSI 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** There are now individual packages for the different supported batch systems<br />
*** Product names are "unicore-tsi-nobatch", "unicore-tsi-torque", "unicore-tsi-lsf", "unicore-tsi-sge" and "unicore-tsi-slurm"<br />
*** Several bug fixes<br />
*** Improved support for SSL (e.g. when using IPv6, better error messages)<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.pdf<br />
<br />
* Gateway 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** Now based on Apache HTTPClient 4<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.pdf<br />
<br />
* Registry 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** Fix for the SSL POODLE security vulnerability<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.pdf<br />
<br />
* XUUDB 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** Fix for the SSL POODLE security vulnerability<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.pdf<br />
<br />
<br />
* UCC 7.x Expected on: TBD<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== LB ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Gridsite ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Proxyrenewal ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CANL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLite-security ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLExec-wn ==<br />
<br />
* LCMAPS-plugins-C-PEP & EES(+xacml library) <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CREAM ==<br />
* BLAH <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
<br />
* CREAM<br />
* Release version 1.16.5 Expected: 2015-01-30<br />
** Main changes: (including other products affected)<br />
*** [https://issues.infn.it/jira/browse/CREAM/fixforversion/11910 CREAM 1.16.5 fixes & new features]<br />
** Other information:<br />
<br />
== STORM ==<br />
* Release version 1.11.5 - emergency <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11819 Fixes in 1.11.5]<br />
** Other information:<br />
*** fixes important issue affecting T1/GPFS 3.5<br />
<br />
<br />
* Release version 1.11.6 <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11815 Fixes in 1.11.6]<br />
** Other information:<br />
*** improvements in STORM Glue2 info-provider<br />
*** yaim-storm asks for a mandatory variable even if it's been defined<br />
<br />
== CREAM GE utils ==<br />
* Release version 2.3.1 Expected: 2014-11-25<br />
** Main changes:<br />
*** Fixes:<br />
**** Sanity checks for memory values<br />
*** New features: <br />
**** UNIVA milisecond precision support<br />
**** Support for both HH:MM:SS and number time formats<br />
** Other information:<br />
*** No other products are affected.<br />
*** [http://ge-utils.github.io/emi-cream-ge-v231.html Release notes]<br />
<br />
== VOMS ==<br />
* Release versions: <br />
** VOMS Admin server <br />
** VOMS Clients v. , VOMS API Java v. <br />
** VOMS C APIs, native clients and server v. <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== WMS ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Globus ==<br />
* Globus Toolkit version 6.0 was released 11 September.<br />
** Updates in Fedora updates testing/EPEL testing:<br />
*** EPEL5: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2812/<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2799/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2843/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-11457/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11364/<br />
*** F21: https://admin.fedoraproject.org/updates/FEDORA-2014-11226/<br />
** Please provide feedback in the tickets above.<br />
** Main changes: Backwards compatible, no soname changes.<br />
** Other information: The Grid Packaging Tools (GPT) will be dropped in favour of standard autotools. If you are relying on GPT tools or GPT metadata files, now is the time to migrate. The pkg-config support has been the preferred way to find Globus Toolkit dependencies a long time. The globus-makefile-header command will be replaced with a wrapper around pkg-config calls to provide some backward compatibility, but its use is not recommended. No GPT metadata files will be installed with the new release.<br />
** Fixes for reported issues: The updates above have been edited to include fixes for the following issues:<br />
***GGUS 106665 - Bad logging of IPv6 addresses in the gridftp server logs. Reported by STORM. Tested by STORM and DPM. https://github.com/globus/globus-toolkit/pull/8. Updated package: globus-gridftp-server-7.11-2<br />
*** Memory leaks in ftp client control library. Reported and tested by FTS. https://github.com/globus/globus-toolkit/pull/9. Updated package: globus-ftp-control-5.11-2<br />
* jGlobus 2.1.0 was released 26 September.<br />
** Updates in Fedora 19+, EPEL 6+ testing and Debian unstable/Debian testing:<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3072/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3087/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-12019/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11982/<br />
*** F21; https://admin.fedoraproject.org/updates/FEDORA-2014-12020/<br />
<br />
== QCG ==<br />
* Version 3.4.0 was released for SL5 and partialy (qcg-Broker) for SL6.<br />
<br />
* Support for SL6 is planned together with new functionality for first update of 2015, curently in validation <br />
* In preparation for the seame udpate (2015) also:<br />
** several updates of the packages, including a new versions of the QCG-Broker (support for voms) and QCG-Computing services.<br />
<br />
= Report from WLCG MW Officer =<br />
<br />
** open verifications are available at https://its.cern.ch/jira/secure/Dashboard.jspa?selectPageId=15100<br />
<br />
= Other topics =<br />
<br />
== XROOTD v.3 vs XROOTD v. 4 ==<br />
<br />
<br />
* Status: xrootd-compat package created and awaiting review:<br />
** https://bugzilla.redhat.com/show_bug.cgi?id=1168914<br />
<br />
== SL5 & MySQL 5.0 vs. MySQL 5.X, x>=1 ==<br />
<br />
* For more details see [[URT:SupportMysql5X|Middleware support of MySQL v. 5.x, x>=1]]<br />
<br />
= Actions =<br />
== Java 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:Java7 Java 7 - as dependency of released products/components ] - Please have a look and send comments, especially TP missing<br />
<br />
== EPEL 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:EPEL7 Status of support of EPEL 7, together with SL7 or CentOS7] - Please have a look and send comments, especially TP missing<br />
<br />
= AOB =<br />
<br />
* Next meeting '''19 Jan. 2015, 15:00 CET'''<br />
<br />
= Minutes =<br />
<br />
* [Minutes 05-01-2014]<br />
<br />
= Audio conference details =<br />
<i><br />
Room link: http://connect.ct.infn.it/egi-inspire-sa1-ter/<br />
<br />
Please provide you Name and product team/affiliation as Guest Name.<br />
<br />
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.<br />
<br />
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm<br />
<br />
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/<br />
<br />
Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.<br />
</i><br />
<br />
''Back to the URT agendas list page: [[URT_meetings_agendas]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=Agenda-05-01-2015&diff=75231Agenda-05-01-20152015-01-09T09:47:35Z<p>Bschulle: /* UNICORE */</p>
<hr />
<div>{|<br />
|-<br />
| [http://connect.ct.infn.it/egi-inspire-sa1-ter/ '''Adobe connect''' direct link]<br />
| ''Conference system is on adobe connect, no password required. <br />
|}<br />
<br />
{{TOC right}}<br />
<br />
= UMD releases status =<br />
<br />
== Status of the products verification/staged rollout ==<br />
<br />
<br />
=== Released ===<br />
* Last release UMD<br />
<br />
=== Under Staged Rollout ===<br />
<br />
<br />
* cream-torque v. 2.1.4<br />
<br />
* glexec-wn v. 1.3.0<br />
<br />
=== In Verification ===<br />
<br />
* cream-ge v. 2.3.0<br />
* qcg-computing-3.4.0 (only SL6)<br />
* qcg-notifications-3.4.0 (only SL6)<br />
* squid v. 2.7.19<br />
* fts3 v. 3.2.27<br />
* voms-clients v. 3.0.5<br />
* voms-admin v. 2.0.12<br />
* apel v. 1.3.1<br />
* px v. 1.3.36<br />
* DPM 1.8.9 <br />
* wms-ice v. 3.5.4<br />
* Globus 6.0.0 products: Gridftp, Globus-Default-Security, Gram5, MyProxy;<br />
<br />
'''Ready to be released:'''<br />
<br />
* cream v. 1.16.4<br />
<br />
=== Rejected ===<br />
<br />
* -----<br />
<br />
== Timeline for the next UMD updates ==<br />
* Mid December<br />
<br />
= Updates from the product teams =<br />
This section is directly contributed by the product teams. Please, add under your section the scheduled releases with a short comment about the updates introduced and where they are going to be released (EMI repositories, EPEL, private repositories ecc), linking external pages with these information is ok, but please add at least the expected date of the next release. It is important to discuss, within the URT, changes that may affect directly or indirectly other products. The text will be copied into the agenda of the next URT meeting, PT will just need to check that all the information are up to date.<br />
Please, feel free to alter the template if it doesn't feet with your needs.<br />
<br />
== APEL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== ARC ==<br />
* Release version 5.0.0 Expected: 2015-01-yy<br />
** Main changes: (including other products affected)<br />
*** Removal of old components:<br />
**** arc-ur-logger (replaced with Jura)<br />
**** LFC DMC<br />
**** DQ2 DMC<br />
**** old data staging<br />
**** Confusa (abandoned prototype)<br />
**** arcmigrate cli tool<br />
**** arcslcs<br />
**** SAML service<br />
**** gridsite dependency<br />
** Other information:<br />
<br />
== Argus ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
<br />
== dCache ==<br />
* Release version 2.6.38 Expected: next UMD release<br />
** Main changes: see appdb<br />
** Other information:<br />
<br />
== BDII ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== DPM/LFC ==<br />
* DPM <br />
** DPM/LFC 1.8.9 are in epel stable since last week<br />
** https://svnweb.cern.ch/trac/lcgdm/blog/dpm_1.8.9_relnotes<br />
** a fix for a bug on the latest dmlite component part of DPM 1.8.9 has been released and and it's already in EPEL stable<br />
** https://svnweb.cern.ch/trac/lcgdm/attachment/wiki/Dpm/dmlite0.7.2-relnotes.txt<br />
** First tests with CentOS7 using components from EPEL7, some issues found, but most of the components are working out of the box<br />
<br />
== GFAL/lcg_utils ==<br />
* The CERN Data Management Clients publish their releases here: http://dmc.web.cern.ch/releases<br />
* A new page with all releases and they status is available at https://dmc-docs.web.cern.ch/dmc-docs/<br />
* New in EPEL<br />
** gfal2 2.7.8 <br />
** gfal2-python 1.6.0 <br />
** gfal2-util 1.1.0 <br />
** srm-ifce 1.20.14<br />
** CGSI-gSOAP 1.3.7<br />
<br />
* CERN-PROD is available for staged rollout<br />
<br />
== FTS ==<br />
* FTS3 EPEL update released, v 3.2.26<br />
* new FTS3 v. 3.2.30 in Epel-testing<br />
<br />
== Frontier-Squid == <br />
* Release version: 2.7STABLE9-21.1; Released: 2014-12-03 - <br />
** Main changes: http://frontier.cern.ch/dist/rpms/frontier-squidRELEASE_NOTES<br />
*** Mainly improves multiple squid support, increasing max from 4 to 16 squids and limiting each squid to a share of available file descriptors<br />
** Other information (repository): http://frontier.cern.ch/dist/rpms<br />
<br />
== EMIR ==<br />
* Release version: ; Expected:<br />
** Main changes: <br />
** Other information:<br />
<br />
== UNICORE ==<br />
(expected in the course of 2015 that we will publish packages for UMD via AppDB at https://appdb.egi.eu/store/software/unicore<br />
<br />
For now, packages for UNICORE 7.2.0 can be downloaded from<br />
<br />
Debian:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/deb<br />
<br />
RPM:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/rpm<br />
<br />
RPM packages were tested on Centos 6, so SL6 will be fine. SL5 is NOT supported <br />
any more.<br />
<br />
Changes are listed with respect to the last UNICORE version available in UMD <br />
which is 6.6.0<br />
<br />
* UNICORE/X 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** Product name is "unicore-unicorex"<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** RESTful API in addition to the SOAP/WS API<br />
*** Many performance improvements<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.pdf<br />
<br />
* TSI 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** There are now individual packages for the different supported batch systems<br />
*** Product names are "unicore-tsi-nobatch", "unicore-tsi-torque", "unicore-tsi-lsf", "unicore-tsi-sge" and "unicore-tsi-slurm"<br />
*** Several bug fixes<br />
*** Improved support for SSL (e.g. when using IPv6, better error messages)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.pdf<br />
<br />
* Gateway 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** Now based on Apache HTTPClient 4<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.pdf<br />
<br />
* Registry 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.pdf<br />
<br />
* XUUDB 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.pdf<br />
<br />
<br />
* UCC 7.x Expected on: TBD<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== LB ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Gridsite ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Proxyrenewal ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CANL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLite-security ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLExec-wn ==<br />
<br />
* LCMAPS-plugins-C-PEP & EES(+xacml library) <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CREAM ==<br />
* BLAH <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
<br />
* CREAM<br />
* Release version 1.16.5 Expected: 2015-01-30<br />
** Main changes: (including other products affected)<br />
*** [https://issues.infn.it/jira/browse/CREAM/fixforversion/11910 CREAM 1.16.5 fixes & new features]<br />
** Other information:<br />
<br />
== STORM ==<br />
* Release version 1.11.5 - emergency <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11819 Fixes in 1.11.5]<br />
** Other information:<br />
*** fixes important issue affecting T1/GPFS 3.5<br />
<br />
<br />
* Release version 1.11.6 <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11815 Fixes in 1.11.6]<br />
** Other information:<br />
*** improvements in STORM Glue2 info-provider<br />
*** yaim-storm asks for a mandatory variable even if it's been defined<br />
<br />
== CREAM GE utils ==<br />
* Release version 2.3.1 Expected: 2014-11-25<br />
** Main changes:<br />
*** Fixes:<br />
**** Sanity checks for memory values<br />
*** New features: <br />
**** UNIVA milisecond precision support<br />
**** Support for both HH:MM:SS and number time formats<br />
** Other information:<br />
*** No other products are affected.<br />
*** [http://ge-utils.github.io/emi-cream-ge-v231.html Release notes]<br />
<br />
== VOMS ==<br />
* Release versions: <br />
** VOMS Admin server <br />
** VOMS Clients v. , VOMS API Java v. <br />
** VOMS C APIs, native clients and server v. <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== WMS ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Globus ==<br />
* Globus Toolkit version 6.0 was released 11 September.<br />
** Updates in Fedora updates testing/EPEL testing:<br />
*** EPEL5: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2812/<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2799/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2843/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-11457/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11364/<br />
*** F21: https://admin.fedoraproject.org/updates/FEDORA-2014-11226/<br />
** Please provide feedback in the tickets above.<br />
** Main changes: Backwards compatible, no soname changes.<br />
** Other information: The Grid Packaging Tools (GPT) will be dropped in favour of standard autotools. If you are relying on GPT tools or GPT metadata files, now is the time to migrate. The pkg-config support has been the preferred way to find Globus Toolkit dependencies a long time. The globus-makefile-header command will be replaced with a wrapper around pkg-config calls to provide some backward compatibility, but its use is not recommended. No GPT metadata files will be installed with the new release.<br />
** Fixes for reported issues: The updates above have been edited to include fixes for the following issues:<br />
***GGUS 106665 - Bad logging of IPv6 addresses in the gridftp server logs. Reported by STORM. Tested by STORM and DPM. https://github.com/globus/globus-toolkit/pull/8. Updated package: globus-gridftp-server-7.11-2<br />
*** Memory leaks in ftp client control library. Reported and tested by FTS. https://github.com/globus/globus-toolkit/pull/9. Updated package: globus-ftp-control-5.11-2<br />
* jGlobus 2.1.0 was released 26 September.<br />
** Updates in Fedora 19+, EPEL 6+ testing and Debian unstable/Debian testing:<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3072/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3087/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-12019/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11982/<br />
*** F21; https://admin.fedoraproject.org/updates/FEDORA-2014-12020/<br />
<br />
== QCG ==<br />
* Version 3.4.0 was released for SL5 and partialy (qcg-Broker) for SL6.<br />
<br />
* Support for SL6 is planned together with new functionality for first update of 2015, curently in validation <br />
* In preparation for the seame udpate (2015) also:<br />
** several updates of the packages, including a new versions of the QCG-Broker (support for voms) and QCG-Computing services.<br />
<br />
= Report from WLCG MW Officer =<br />
<br />
** open verifications are available at https://its.cern.ch/jira/secure/Dashboard.jspa?selectPageId=15100<br />
<br />
= Other topics =<br />
<br />
== XROOTD v.3 vs XROOTD v. 4 ==<br />
<br />
<br />
* Status: xrootd-compat package created and awaiting review:<br />
** https://bugzilla.redhat.com/show_bug.cgi?id=1168914<br />
<br />
== SL5 & MySQL 5.0 vs. MySQL 5.X, x>=1 ==<br />
<br />
* For more details see [[URT:SupportMysql5X|Middleware support of MySQL v. 5.x, x>=1]]<br />
<br />
= Actions =<br />
== Java 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:Java7 Java 7 - as dependency of released products/components ] - Please have a look and send comments, especially TP missing<br />
<br />
== EPEL 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:EPEL7 Status of support of EPEL 7, together with SL7 or CentOS7] - Please have a look and send comments, especially TP missing<br />
<br />
= AOB =<br />
<br />
* Next meeting '''19 Jan. 2015, 15:00 CET'''<br />
<br />
= Minutes =<br />
<br />
* [Minutes 05-01-2014]<br />
<br />
= Audio conference details =<br />
<i><br />
Room link: http://connect.ct.infn.it/egi-inspire-sa1-ter/<br />
<br />
Please provide you Name and product team/affiliation as Guest Name.<br />
<br />
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.<br />
<br />
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm<br />
<br />
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/<br />
<br />
Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.<br />
</i><br />
<br />
''Back to the URT agendas list page: [[URT_meetings_agendas]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=Agenda-05-01-2015&diff=75230Agenda-05-01-20152015-01-09T09:35:05Z<p>Bschulle: /* UNICORE */</p>
<hr />
<div>{|<br />
|-<br />
| [http://connect.ct.infn.it/egi-inspire-sa1-ter/ '''Adobe connect''' direct link]<br />
| ''Conference system is on adobe connect, no password required. <br />
|}<br />
<br />
{{TOC right}}<br />
<br />
= UMD releases status =<br />
<br />
== Status of the products verification/staged rollout ==<br />
<br />
<br />
=== Released ===<br />
* Last release UMD<br />
<br />
=== Under Staged Rollout ===<br />
<br />
<br />
* cream-torque v. 2.1.4<br />
<br />
* glexec-wn v. 1.3.0<br />
<br />
=== In Verification ===<br />
<br />
* cream-ge v. 2.3.0<br />
* qcg-computing-3.4.0 (only SL6)<br />
* qcg-notifications-3.4.0 (only SL6)<br />
* squid v. 2.7.19<br />
* fts3 v. 3.2.27<br />
* voms-clients v. 3.0.5<br />
* voms-admin v. 2.0.12<br />
* apel v. 1.3.1<br />
* px v. 1.3.36<br />
* DPM 1.8.9 <br />
* wms-ice v. 3.5.4<br />
* Globus 6.0.0 products: Gridftp, Globus-Default-Security, Gram5, MyProxy;<br />
<br />
'''Ready to be released:'''<br />
<br />
* cream v. 1.16.4<br />
<br />
=== Rejected ===<br />
<br />
* -----<br />
<br />
== Timeline for the next UMD updates ==<br />
* Mid December<br />
<br />
= Updates from the product teams =<br />
This section is directly contributed by the product teams. Please, add under your section the scheduled releases with a short comment about the updates introduced and where they are going to be released (EMI repositories, EPEL, private repositories ecc), linking external pages with these information is ok, but please add at least the expected date of the next release. It is important to discuss, within the URT, changes that may affect directly or indirectly other products. The text will be copied into the agenda of the next URT meeting, PT will just need to check that all the information are up to date.<br />
Please, feel free to alter the template if it doesn't feet with your needs.<br />
<br />
== APEL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== ARC ==<br />
* Release version 5.0.0 Expected: 2015-01-yy<br />
** Main changes: (including other products affected)<br />
*** Removal of old components:<br />
**** arc-ur-logger (replaced with Jura)<br />
**** LFC DMC<br />
**** DQ2 DMC<br />
**** old data staging<br />
**** Confusa (abandoned prototype)<br />
**** arcmigrate cli tool<br />
**** arcslcs<br />
**** SAML service<br />
**** gridsite dependency<br />
** Other information:<br />
<br />
== Argus ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
<br />
== dCache ==<br />
* Release version 2.6.38 Expected: next UMD release<br />
** Main changes: see appdb<br />
** Other information:<br />
<br />
== BDII ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== DPM/LFC ==<br />
* DPM <br />
** DPM/LFC 1.8.9 are in epel stable since last week<br />
** https://svnweb.cern.ch/trac/lcgdm/blog/dpm_1.8.9_relnotes<br />
** a fix for a bug on the latest dmlite component part of DPM 1.8.9 has been released and and it's already in EPEL stable<br />
** https://svnweb.cern.ch/trac/lcgdm/attachment/wiki/Dpm/dmlite0.7.2-relnotes.txt<br />
** First tests with CentOS7 using components from EPEL7, some issues found, but most of the components are working out of the box<br />
<br />
== GFAL/lcg_utils ==<br />
* The CERN Data Management Clients publish their releases here: http://dmc.web.cern.ch/releases<br />
* A new page with all releases and they status is available at https://dmc-docs.web.cern.ch/dmc-docs/<br />
* New in EPEL<br />
** gfal2 2.7.8 <br />
** gfal2-python 1.6.0 <br />
** gfal2-util 1.1.0 <br />
** srm-ifce 1.20.14<br />
** CGSI-gSOAP 1.3.7<br />
<br />
* CERN-PROD is available for staged rollout<br />
<br />
== FTS ==<br />
* FTS3 EPEL update released, v 3.2.26<br />
* new FTS3 v. 3.2.30 in Epel-testing<br />
<br />
== Frontier-Squid == <br />
* Release version: 2.7STABLE9-21.1; Released: 2014-12-03 - <br />
** Main changes: http://frontier.cern.ch/dist/rpms/frontier-squidRELEASE_NOTES<br />
*** Mainly improves multiple squid support, increasing max from 4 to 16 squids and limiting each squid to a share of available file descriptors<br />
** Other information (repository): http://frontier.cern.ch/dist/rpms<br />
<br />
== EMIR ==<br />
* Release version: ; Expected:<br />
** Main changes: <br />
** Other information:<br />
<br />
== UNICORE ==<br />
(expected in the course of 2015 that we will publish packages for UMD via AppDB at https://appdb.egi.eu/store/software/unicore<br />
<br />
For now, packages for UNICORE 7.2.0 can be downloaded from<br />
<br />
Debian:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/deb<br />
<br />
RPM:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/rpm<br />
<br />
RPM packages were tested on Centos 6, so SL6 will be fine. SL5 is NOT supported <br />
any more.<br />
<br />
Changes are listed with respect to the last UNICORE version available in UMD <br />
which is 6.6.0<br />
<br />
* UNICORE/X 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** RESTful API in addition to the SOAP/WS API<br />
*** Many performance improvements<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.pdf<br />
<br />
* TSI 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** There are now individual packages for the different supported batch systems, as well as a generic one that lets you choose which batch system you want to use<br />
*** Several bug fixes<br />
*** Improved support for SSL (e.g. when using IPv6, better error messages)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.pdf<br />
<br />
* Gateway 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** Now based on Apache HTTPClient 4<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.pdf<br />
<br />
* Registry 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.pdf<br />
<br />
* XUUDB 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.pdf<br />
<br />
<br />
* UCC 7.x Expected on: TBD<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== LB ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Gridsite ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Proxyrenewal ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CANL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLite-security ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLExec-wn ==<br />
<br />
* LCMAPS-plugins-C-PEP & EES(+xacml library) <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CREAM ==<br />
* BLAH <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
<br />
* CREAM<br />
* Release version 1.16.5 Expected: 2015-01-30<br />
** Main changes: (including other products affected)<br />
*** [https://issues.infn.it/jira/browse/CREAM/fixforversion/11910 CREAM 1.16.5 fixes & new features]<br />
** Other information:<br />
<br />
== STORM ==<br />
* Release version 1.11.5 - emergency <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11819 Fixes in 1.11.5]<br />
** Other information:<br />
*** fixes important issue affecting T1/GPFS 3.5<br />
<br />
<br />
* Release version 1.11.6 <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11815 Fixes in 1.11.6]<br />
** Other information:<br />
*** improvements in STORM Glue2 info-provider<br />
*** yaim-storm asks for a mandatory variable even if it's been defined<br />
<br />
== CREAM GE utils ==<br />
* Release version 2.3.1 Expected: 2014-11-25<br />
** Main changes:<br />
*** Fixes:<br />
**** Sanity checks for memory values<br />
*** New features: <br />
**** UNIVA milisecond precision support<br />
**** Support for both HH:MM:SS and number time formats<br />
** Other information:<br />
*** No other products are affected.<br />
*** [http://ge-utils.github.io/emi-cream-ge-v231.html Release notes]<br />
<br />
== VOMS ==<br />
* Release versions: <br />
** VOMS Admin server <br />
** VOMS Clients v. , VOMS API Java v. <br />
** VOMS C APIs, native clients and server v. <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== WMS ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Globus ==<br />
* Globus Toolkit version 6.0 was released 11 September.<br />
** Updates in Fedora updates testing/EPEL testing:<br />
*** EPEL5: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2812/<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2799/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2843/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-11457/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11364/<br />
*** F21: https://admin.fedoraproject.org/updates/FEDORA-2014-11226/<br />
** Please provide feedback in the tickets above.<br />
** Main changes: Backwards compatible, no soname changes.<br />
** Other information: The Grid Packaging Tools (GPT) will be dropped in favour of standard autotools. If you are relying on GPT tools or GPT metadata files, now is the time to migrate. The pkg-config support has been the preferred way to find Globus Toolkit dependencies a long time. The globus-makefile-header command will be replaced with a wrapper around pkg-config calls to provide some backward compatibility, but its use is not recommended. No GPT metadata files will be installed with the new release.<br />
** Fixes for reported issues: The updates above have been edited to include fixes for the following issues:<br />
***GGUS 106665 - Bad logging of IPv6 addresses in the gridftp server logs. Reported by STORM. Tested by STORM and DPM. https://github.com/globus/globus-toolkit/pull/8. Updated package: globus-gridftp-server-7.11-2<br />
*** Memory leaks in ftp client control library. Reported and tested by FTS. https://github.com/globus/globus-toolkit/pull/9. Updated package: globus-ftp-control-5.11-2<br />
* jGlobus 2.1.0 was released 26 September.<br />
** Updates in Fedora 19+, EPEL 6+ testing and Debian unstable/Debian testing:<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3072/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3087/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-12019/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11982/<br />
*** F21; https://admin.fedoraproject.org/updates/FEDORA-2014-12020/<br />
<br />
== QCG ==<br />
* Version 3.4.0 was released for SL5 and partialy (qcg-Broker) for SL6.<br />
<br />
* Support for SL6 is planned together with new functionality for first update of 2015, curently in validation <br />
* In preparation for the seame udpate (2015) also:<br />
** several updates of the packages, including a new versions of the QCG-Broker (support for voms) and QCG-Computing services.<br />
<br />
= Report from WLCG MW Officer =<br />
<br />
** open verifications are available at https://its.cern.ch/jira/secure/Dashboard.jspa?selectPageId=15100<br />
<br />
= Other topics =<br />
<br />
== XROOTD v.3 vs XROOTD v. 4 ==<br />
<br />
<br />
* Status: xrootd-compat package created and awaiting review:<br />
** https://bugzilla.redhat.com/show_bug.cgi?id=1168914<br />
<br />
== SL5 & MySQL 5.0 vs. MySQL 5.X, x>=1 ==<br />
<br />
* For more details see [[URT:SupportMysql5X|Middleware support of MySQL v. 5.x, x>=1]]<br />
<br />
= Actions =<br />
== Java 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:Java7 Java 7 - as dependency of released products/components ] - Please have a look and send comments, especially TP missing<br />
<br />
== EPEL 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:EPEL7 Status of support of EPEL 7, together with SL7 or CentOS7] - Please have a look and send comments, especially TP missing<br />
<br />
= AOB =<br />
<br />
* Next meeting '''19 Jan. 2015, 15:00 CET'''<br />
<br />
= Minutes =<br />
<br />
* [Minutes 05-01-2014]<br />
<br />
= Audio conference details =<br />
<i><br />
Room link: http://connect.ct.infn.it/egi-inspire-sa1-ter/<br />
<br />
Please provide you Name and product team/affiliation as Guest Name.<br />
<br />
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.<br />
<br />
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm<br />
<br />
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/<br />
<br />
Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.<br />
</i><br />
<br />
''Back to the URT agendas list page: [[URT_meetings_agendas]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=Agenda-05-01-2015&diff=75229Agenda-05-01-20152015-01-09T09:34:03Z<p>Bschulle: /* UNICORE */</p>
<hr />
<div>{|<br />
|-<br />
| [http://connect.ct.infn.it/egi-inspire-sa1-ter/ '''Adobe connect''' direct link]<br />
| ''Conference system is on adobe connect, no password required. <br />
|}<br />
<br />
{{TOC right}}<br />
<br />
= UMD releases status =<br />
<br />
== Status of the products verification/staged rollout ==<br />
<br />
<br />
=== Released ===<br />
* Last release UMD<br />
<br />
=== Under Staged Rollout ===<br />
<br />
<br />
* cream-torque v. 2.1.4<br />
<br />
* glexec-wn v. 1.3.0<br />
<br />
=== In Verification ===<br />
<br />
* cream-ge v. 2.3.0<br />
* qcg-computing-3.4.0 (only SL6)<br />
* qcg-notifications-3.4.0 (only SL6)<br />
* squid v. 2.7.19<br />
* fts3 v. 3.2.27<br />
* voms-clients v. 3.0.5<br />
* voms-admin v. 2.0.12<br />
* apel v. 1.3.1<br />
* px v. 1.3.36<br />
* DPM 1.8.9 <br />
* wms-ice v. 3.5.4<br />
* Globus 6.0.0 products: Gridftp, Globus-Default-Security, Gram5, MyProxy;<br />
<br />
'''Ready to be released:'''<br />
<br />
* cream v. 1.16.4<br />
<br />
=== Rejected ===<br />
<br />
* -----<br />
<br />
== Timeline for the next UMD updates ==<br />
* Mid December<br />
<br />
= Updates from the product teams =<br />
This section is directly contributed by the product teams. Please, add under your section the scheduled releases with a short comment about the updates introduced and where they are going to be released (EMI repositories, EPEL, private repositories ecc), linking external pages with these information is ok, but please add at least the expected date of the next release. It is important to discuss, within the URT, changes that may affect directly or indirectly other products. The text will be copied into the agenda of the next URT meeting, PT will just need to check that all the information are up to date.<br />
Please, feel free to alter the template if it doesn't feet with your needs.<br />
<br />
== APEL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== ARC ==<br />
* Release version 5.0.0 Expected: 2015-01-yy<br />
** Main changes: (including other products affected)<br />
*** Removal of old components:<br />
**** arc-ur-logger (replaced with Jura)<br />
**** LFC DMC<br />
**** DQ2 DMC<br />
**** old data staging<br />
**** Confusa (abandoned prototype)<br />
**** arcmigrate cli tool<br />
**** arcslcs<br />
**** SAML service<br />
**** gridsite dependency<br />
** Other information:<br />
<br />
== Argus ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
<br />
== dCache ==<br />
* Release version 2.6.38 Expected: next UMD release<br />
** Main changes: see appdb<br />
** Other information:<br />
<br />
== BDII ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== DPM/LFC ==<br />
* DPM <br />
** DPM/LFC 1.8.9 are in epel stable since last week<br />
** https://svnweb.cern.ch/trac/lcgdm/blog/dpm_1.8.9_relnotes<br />
** a fix for a bug on the latest dmlite component part of DPM 1.8.9 has been released and and it's already in EPEL stable<br />
** https://svnweb.cern.ch/trac/lcgdm/attachment/wiki/Dpm/dmlite0.7.2-relnotes.txt<br />
** First tests with CentOS7 using components from EPEL7, some issues found, but most of the components are working out of the box<br />
<br />
== GFAL/lcg_utils ==<br />
* The CERN Data Management Clients publish their releases here: http://dmc.web.cern.ch/releases<br />
* A new page with all releases and they status is available at https://dmc-docs.web.cern.ch/dmc-docs/<br />
* New in EPEL<br />
** gfal2 2.7.8 <br />
** gfal2-python 1.6.0 <br />
** gfal2-util 1.1.0 <br />
** srm-ifce 1.20.14<br />
** CGSI-gSOAP 1.3.7<br />
<br />
* CERN-PROD is available for staged rollout<br />
<br />
== FTS ==<br />
* FTS3 EPEL update released, v 3.2.26<br />
* new FTS3 v. 3.2.30 in Epel-testing<br />
<br />
== Frontier-Squid == <br />
* Release version: 2.7STABLE9-21.1; Released: 2014-12-03 - <br />
** Main changes: http://frontier.cern.ch/dist/rpms/frontier-squidRELEASE_NOTES<br />
*** Mainly improves multiple squid support, increasing max from 4 to 16 squids and limiting each squid to a share of available file descriptors<br />
** Other information (repository): http://frontier.cern.ch/dist/rpms<br />
<br />
== EMIR ==<br />
* Release version: ; Expected:<br />
** Main changes: <br />
** Other information:<br />
<br />
== UNICORE ==<br />
(expected in the course of 2015 that we will publish packages for UMD via AppDB at https://appdb.egi.eu/store/software/unicore<br />
<br />
For now, packages for UNICORE 7.2.0 can be downloaded from<br />
<br />
Debian:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/deb<br />
<br />
RPM:<br />
http://unicore-dev.zam.kfa-juelich.de/release-candidates/core/7.2.0-packages/rpm<br />
<br />
RPM packages were tested on Centos 6, so SL6 will be fine. SL5 is NOT supported <br />
any more.<br />
<br />
Changes are listed with respect to the last UNICORE version available in UMD <br />
which is 6.6.0<br />
<br />
* UNICORE/X 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** RESTful API in addition to the SOAP/WS API<br />
*** Many performance improvements<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
*** For a full, detailed list of changes please refer to http://unicore.eu/changes/server.html<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, <br />
and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/unicorex/unicorex-manual.pdf<br />
<br />
* TSI 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** There are now individual packages for the different supported batch systems, as well as a generic one<br />
that lets you choose which batch system you want to use<br />
*** Several bug fixes<br />
*** Improved support for SSL (e.g. when using IPv6, better error messages)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, <br />
and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/tsi/tsi-manual.pdf<br />
<br />
* Gateway 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** Now based on Apache HTTPClient 4<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, <br />
and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/gateway/manual.pdf<br />
<br />
* Registry 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
*** Many fixes for bugs and some security vulnerabilities (e.g. SSL POODLE)<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, <br />
and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/registry/registry-manual.pdf<br />
<br />
* XUUDB 7.2.0 (expected on: 2015-01-21)<br />
** Main changes: (including other products affected)<br />
*** New web services stack based on Apache CXF and Apache HTTPClient 4<br />
** Other information:<br />
*** This is a major update. We recommend uninstalling any older (6.6) version that you may have, <br />
and re-install from scratch.<br />
*** UNICORE 7 is backwards compatible with UNICORE 6<br />
*** HTML doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.html<br />
*** PDF doc http://unicore.eu/documentation/manuals/unicore6/files/xuudb/manual.pdf<br />
<br />
<br />
* UCC 7.x Expected on: TBD<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== LB ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Gridsite ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Proxyrenewal ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CANL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLite-security ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== gLExec-wn ==<br />
<br />
* LCMAPS-plugins-C-PEP & EES(+xacml library) <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CREAM ==<br />
* BLAH <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
<br />
* CREAM<br />
* Release version 1.16.5 Expected: 2015-01-30<br />
** Main changes: (including other products affected)<br />
*** [https://issues.infn.it/jira/browse/CREAM/fixforversion/11910 CREAM 1.16.5 fixes & new features]<br />
** Other information:<br />
<br />
== STORM ==<br />
* Release version 1.11.5 - emergency <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11819 Fixes in 1.11.5]<br />
** Other information:<br />
*** fixes important issue affecting T1/GPFS 3.5<br />
<br />
<br />
* Release version 1.11.6 <br />
*Expected: A.S.A.A, 2014<br />
*Main changes:<br />
** [https://issues.infn.it/jira/browse/STOR/fixforversion/11815 Fixes in 1.11.6]<br />
** Other information:<br />
*** improvements in STORM Glue2 info-provider<br />
*** yaim-storm asks for a mandatory variable even if it's been defined<br />
<br />
== CREAM GE utils ==<br />
* Release version 2.3.1 Expected: 2014-11-25<br />
** Main changes:<br />
*** Fixes:<br />
**** Sanity checks for memory values<br />
*** New features: <br />
**** UNIVA milisecond precision support<br />
**** Support for both HH:MM:SS and number time formats<br />
** Other information:<br />
*** No other products are affected.<br />
*** [http://ge-utils.github.io/emi-cream-ge-v231.html Release notes]<br />
<br />
== VOMS ==<br />
* Release versions: <br />
** VOMS Admin server <br />
** VOMS Clients v. , VOMS API Java v. <br />
** VOMS C APIs, native clients and server v. <br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== WMS ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== Globus ==<br />
* Globus Toolkit version 6.0 was released 11 September.<br />
** Updates in Fedora updates testing/EPEL testing:<br />
*** EPEL5: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2812/<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2799/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2843/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-11457/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11364/<br />
*** F21: https://admin.fedoraproject.org/updates/FEDORA-2014-11226/<br />
** Please provide feedback in the tickets above.<br />
** Main changes: Backwards compatible, no soname changes.<br />
** Other information: The Grid Packaging Tools (GPT) will be dropped in favour of standard autotools. If you are relying on GPT tools or GPT metadata files, now is the time to migrate. The pkg-config support has been the preferred way to find Globus Toolkit dependencies a long time. The globus-makefile-header command will be replaced with a wrapper around pkg-config calls to provide some backward compatibility, but its use is not recommended. No GPT metadata files will be installed with the new release.<br />
** Fixes for reported issues: The updates above have been edited to include fixes for the following issues:<br />
***GGUS 106665 - Bad logging of IPv6 addresses in the gridftp server logs. Reported by STORM. Tested by STORM and DPM. https://github.com/globus/globus-toolkit/pull/8. Updated package: globus-gridftp-server-7.11-2<br />
*** Memory leaks in ftp client control library. Reported and tested by FTS. https://github.com/globus/globus-toolkit/pull/9. Updated package: globus-ftp-control-5.11-2<br />
* jGlobus 2.1.0 was released 26 September.<br />
** Updates in Fedora 19+, EPEL 6+ testing and Debian unstable/Debian testing:<br />
*** EPEL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3072/<br />
*** EPEL7: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3087/<br />
*** F19: https://admin.fedoraproject.org/updates/FEDORA-2014-12019/<br />
*** F20: https://admin.fedoraproject.org/updates/FEDORA-2014-11982/<br />
*** F21; https://admin.fedoraproject.org/updates/FEDORA-2014-12020/<br />
<br />
== QCG ==<br />
* Version 3.4.0 was released for SL5 and partialy (qcg-Broker) for SL6.<br />
<br />
* Support for SL6 is planned together with new functionality for first update of 2015, curently in validation <br />
* In preparation for the seame udpate (2015) also:<br />
** several updates of the packages, including a new versions of the QCG-Broker (support for voms) and QCG-Computing services.<br />
<br />
= Report from WLCG MW Officer =<br />
<br />
** open verifications are available at https://its.cern.ch/jira/secure/Dashboard.jspa?selectPageId=15100<br />
<br />
= Other topics =<br />
<br />
== XROOTD v.3 vs XROOTD v. 4 ==<br />
<br />
<br />
* Status: xrootd-compat package created and awaiting review:<br />
** https://bugzilla.redhat.com/show_bug.cgi?id=1168914<br />
<br />
== SL5 & MySQL 5.0 vs. MySQL 5.X, x>=1 ==<br />
<br />
* For more details see [[URT:SupportMysql5X|Middleware support of MySQL v. 5.x, x>=1]]<br />
<br />
= Actions =<br />
== Java 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:Java7 Java 7 - as dependency of released products/components ] - Please have a look and send comments, especially TP missing<br />
<br />
== EPEL 7 ==<br />
* [https://wiki.egi.eu/wiki/URT:EPEL7 Status of support of EPEL 7, together with SL7 or CentOS7] - Please have a look and send comments, especially TP missing<br />
<br />
= AOB =<br />
<br />
* Next meeting '''19 Jan. 2015, 15:00 CET'''<br />
<br />
= Minutes =<br />
<br />
* [Minutes 05-01-2014]<br />
<br />
= Audio conference details =<br />
<i><br />
Room link: http://connect.ct.infn.it/egi-inspire-sa1-ter/<br />
<br />
Please provide you Name and product team/affiliation as Guest Name.<br />
<br />
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.<br />
<br />
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm<br />
<br />
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/<br />
<br />
Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.<br />
</i><br />
<br />
''Back to the URT agendas list page: [[URT_meetings_agendas]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:Agenda-03-02-2014&diff=64165URT:Agenda-03-02-20142014-02-03T13:57:24Z<p>Bschulle: /* UNICORE */</p>
<hr />
<div>{|<br />
|-<br />
| [http://connect.ct.infn.it/egi-inspire-sa1/ Audio conference link] <br />
| ''Conference system is Adobe Connect, no password required.''<br />
|-<br />
| [https://wiki.egi.eu/wiki/URT:Agenda_template#Audio_conference_details Audio conference details] <br />
| [https://indico.egi.eu/indico/conferenceDisplay.py?confId=2027 Indico page]<br />
|}<br />
<br />
{{TOC right}}<br />
<br />
= UMD releases status =<br />
<br />
== Status of the products verification/staged rollout ==<br />
<br />
=== Next UMD-3 releases ===<br />
<br />
=== Ready to be released ===<br />
<br />
= Updates from the product teams =<br />
This section is directly contributed by the product teams. Please, add under your section the scheduled releases with a short comment about the updates introduced and where they are going to be released (EMI repositories, EPEL, private repositories ecc), linking external pages with these information is ok, but please add at least the expected date of the next release. It is important to discuss, within the URT, changes that may affect directly or indirectly other products. The text will be copied into the agenda of the next URT meeting, PT will just need to check that all the information are up to date.<br />
Please, feel free to alter the template if it doesn't feet with your needs.<br />
<br />
== APEL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
== ARC ==<br />
* Release 13.11 version 4.0.0 released<br />
** Main changes: Major release, new BDB job storage, new infosys startup scripts, direct DQ2 support, improved WebDAV support, improved proxy handling<br />
** Other information: Currently in EPEL testing repo.<br />
<br />
== Argus ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
== dCache ==<br />
* dCache Release Schedule<br />
** Main changes: released dcache-srmclient 2.2.22 to EMI-2 and EMI-3<br />
** new Releases for UMD-2 dcache-server 2.2.17 and UMD-3 dcache-server 2.6.17 could be pulled from EMI<br />
** Other information:<br />
<br />
== DPM/LFC ==<br />
* An update to DPM 1.8.7 has been released which includes support for StAR accounting.<br />
** https://svnweb.cern.ch/trac/lcgdm/attachment/wiki/Dpm/pkglist_26082013.txt<br />
<br />
== GFAL/lcg_utils ==<br />
* Release version: gfal2 update (v2.4.8), first release of gfal2-util (replacement for lcg_util), davix update (v0.2.8)<br />
** Main changes: : https://svnweb.cern.ch/trac/lcgutil/wiki/Release_status<br />
** Other information: Bugfixes<br />
<br />
== FTS ==<br />
* Release version FTS3 (v3.1) is available in EPEL<br />
** Main changes: <br />
*** FTS 3 is the replacement of FTS 2. It has been a pilot service tested by WLCG for several months and now it is ready to go to production.<br />
*** Details: https://svnweb.cern.ch/trac/fts3/roadmap<br />
** Other information:<br />
<br />
== BDII ==<br />
<br />
New release of the BDII that decommissions the FCR mechanism in the top BDII. <br />
<br />
The update also defines a new default value for the cache validity in the top BDII that is 4 days. <br />
<br />
New packages are available in EMI 2 and EMI 3 repositories. For more details:<br />
<br />
http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-11-02-12-2013-v-3-6-1-1#BDII_core_v_1_5_5<br />
<br />
http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-11-02-12-2013-v-3-6-1-1#BDII_top_v_1_1_4<br />
<br />
== EMIR ==<br />
* Release version: <br />
** Main changes: <br />
** Other information:<br />
<br />
== UNICORE ==<br />
We will publish packages for UMD via AppDB at https://appdb.egi.eu/store/software/unicore<br />
<br />
* UCC 7.0.1 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
* UNICORE/X 7.0.0 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
* TSI 7.0.0 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
* Gateway 7.0.0 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
* Registry 7.0.0 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== LB ==<br />
* Release version w.k.j Expected on: 2013-12-20<br />
** 4.0.12, 3.2.12<br />
** Main changes: Fixes<br />
** Latest releases<br />
*** L&B 4.0.11-1 (EMI-3), released Fri 21 June 2013 through the EMI repos, available officially since July 8 from EMI repos.<br />
*** https://github.com/CESNET/glite-lb/wiki/Glite-l%26b-release-page#wiki-LB_40111<br />
*** L&B 4.0.11-1 (EMI-2), released Fri 21 June 2013 through the EMI repos, available officially since July 8 from EMI repos.<br />
*** https://github.com/CESNET/glite-lb/wiki/Glite-l%26b-release-page#wiki-LB_32111<br />
<br />
== Gridsite ==<br />
* Release version: GridSite 2.2.1: https://github.com/CESNET/gridsite/wiki/Gridsite-release-page#wiki-GridSite_2211<br />
** Main changes: revision of GridSite, turning off server-side TLS tickets support, which has been turned on by default since OpenSSL 1.0. More elaborate support will be provided in a later revision.<br />
** Other information:<br />
<br />
== Proxyrenewal ==<br />
* Release version: PX 1.0.25 (ProxyRenewal 1.3.25): https://github.com/CESNET/proxyrenewal/wiki/Px-release-page#wiki-PX_10251<br />
** Main changes: revision for ProxyRenewal, which makes sure 1024-bit keys are explicitly requested from Globus, overriding the current Globus default of 512 bits.<br />
** Other information:<br />
<br />
== CANL ==<br />
* Release version: caNl, v. 2.2.1, containing caNl-c v. 2.1.3 & caNl-java v. 1.3.1<br />
** Main changes: Fixed handling of the KeyUsage attribute in proxies created by caNl-java.<br />
*** https://github.com/eu-emi/canl-java/issues/62<br />
*** https://github.com/CESNET/canl-c/wiki/caNl-c-Release-Page#wiki-caNlc_2131<br />
** Other information:<br />
<br />
== gLite- security ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CREAM ==<br />
<br />
* Plan to release version: Update EMI 2 & EMI 3 - 31 Oct.2013<br />
** BLAH 1.20 4 (EMI 3)<br />
** CREAM SLURM module 1.0.1 (EMI 3)<br />
** CREAM TORQUE module 2.1.2 (EMI 3)<br />
** CREAM 1.14.6 (EMI 2)<br />
** Main changes:<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=96171 GGUS #96171 - Missing CE information from SLURM infoprovider]<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=95751 GGUS #95751 - MPI support for SLURM jobs ]<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=96703 GGUS #96703 - Wrong total cpu count from PBS infoprovider]<br />
** Other information:<br />
<br />
== STORM ==<br />
<br />
* Next release: Oct. 2013<br />
** STORM 1.11.3 (EMI 3)<br />
** Main changes:<br />
*** Mainly WebDAV issues<br />
** Other information:<br />
<br />
== VOMS ==<br />
* Next releases: Oct 2013<br />
** VOMS Clients v. 3.0.4, VOMS API Java v. 3.0.2 (EMI 3)<br />
** VOMS Admin server v. 3.3.0 (EMI 3)<br />
** Main changes:<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=97555 GGUS #97555 - Serializing private key using pkcs#8 encoding confuses dCache clients]<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=95660 GGUS #95660 - Socket timeout can lead to VOMS Server hanging in endless loop]<br />
*** Migrate Java API to CAnL 1.3<br />
*** [https://issues.infn.it/jira/issues/?jql=project%20%3D%20VOMS%20AND%20fixVersion%20%3D%20%22VOMS%20Admin%20server%20v.%203.3.0%22%20AND%20resolution%20is%20not%20EMPTY VOMS Server fixed issues]<br />
** Other information:<br />
<br />
<br />
== WMS ==<br />
* Next releases: EMI 3 - 31 Oct. 2013<br />
** WMS 3.6.1 (EMI 3)<br />
** Main changes:<br />
*** Sec. Vulnerabilities<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=96733 GGUS #96733 - glite_wms_wmproxy_server prints taint check warnings]<br />
*** Other information: <br />
<br />
<br />
== Globus ==<br />
* The RHEL/CentOS/SL update from version 6.4 to 6.5 caused problems for the globus gatekeeper:<br />
** https://ggus.eu/ws/ticket_info.php?ticket=99406<br />
* The problem was caused by updating openssl from version 1.0.0 to version 1.0.1.<br />
* One globus package (globus-gssapi-gsi) was identified as behaving differently when compiled against openssl 1.0.0 and 1.0.1. (It is the only one that has a requires on libcrypto.so.10(OPENSSL_1.0.1)(64bit) when compiled against openssl 1.0.1)<br />
* Using a recompiled globus-gssapi-gsi package makes the globus-gatekeeper work again.<br />
* Packages in Fedora updates testing and EPEL testing, please provide feedback (karma)<br />
<br />
== QCG ==<br />
* Release version 3.2.0, Ready to be released<br />
** Main changes: <br />
*** QCG-Broker<br />
**** SHA2 certificates support<br />
**** Improved support for parallel and multi-scale applications<br />
**** Migration from CoG 1.8 to jGlobus2<br />
**** Migration from Tomcat to Jetty servlet container<br />
**** Support iRODS transfers<br />
**** Support for http:// http:// transfers (stage-in only)<br />
**** Advance reservation of nodes. <br />
**** Bug fixes<br />
*** QCG-Broker Client<br />
**** SHA2 certificates support<br />
**** Configurable columns in qcg-list and qcg-rlist commands<br />
**** New qcg-resub command for resubmitting jobs<br />
**** New "#QCG include" directive in simple description format<br />
**** Full support for interactive tasks. <br />
*** QCG-Computing<br />
**** Performance optimization of the GetFactoryAttributes method<br />
**** GPUSCount extension element in SLURM module<br />
**** Bug fixes<br />
*** QCG-Notification<br />
**** New configuration option for disabling CurrentMessages (set to true in the default service config file)<br />
**** Updated requirement for qcg-core to the version 3.2.0.<br />
**** Move to the newer version of libxml2 (from 2.6.27 to 2.9.1). <br />
**** Updated the database configuration script.<br />
**** WorkingDirectory location changed to the $localstate/log/qcg/qcg-ntf directory (in the service config file). <br />
**** Fix: removed a doubled database rollback.<br />
**** Fix: repaired a memory leak related with not freeing the fault data. <br />
**** Other minor corrections.<br />
** Other information:<br />
<br />
= Other topics =<br />
= Other topics =<br />
== UMD to sign packages ==<br />
So far UMD did not sign RPMs or DEB produced by the product teams, relying on the check of the EMI or EPEL gpg keys. To be able to get new middleware updates as soon as the product teams release, UMD team is considering to sign the RPMs that can be imported also from repositories or web locations. <br />
<br />
== UMD-2 decommission == <br />
'''The EMI 2 [[PROC16#Decommissioning_deadline |decommissioning deadline]] is 31-05-2014'''.<br />
<br />
Details:<br />
* by 01-03-2014: new EMI 2 version probes are tested returning WARNING<br />
* on 03-03-2014: EMI 2 version monitoring probes start returning CRITICAL, alarms are displayed in the [https://operations-portal.egi.eu/dashboard Operations Dashboard]<br />
* 30-04-2014: end of security updates and support of EMI 2<br />
* 31-05-2013: EMI 2 [[PROC16#Decommissioning_deadline |decommissioning deadline]] after this date all the EMI-2 services must be decommissioned, upgraded to a supported version or in downtime.<br />
<br />
Affected software:<br />
<br />
*ARC v2.*<br />
*ARGUS v1.5.*<br />
*BDII Site ''older'' than v1.2.0<br />
*BDII Top ''older'' than v1.1.0<br />
*CREAM v1.14.*<br />
*dCache v2.2.*<br />
*DPM ''older'' than v1.8.6<br />
*EMI-UI v2.*<br />
*EMI-WN v2.*<br />
*FTS v.2.2.8<br />
*StoRM ''older'' than v.1.11.0<br />
*VOMS v.2.*<br />
<br />
I will update the list adding Globus and UNICORE.<br />
<br />
= AOB =<br />
<br />
= Minutes = <br />
<br />
= Audio conference details =<br />
<i><br />
Room link: http://connect.ct.infn.it/egi-inspire-sa1/<br />
<br />
Please provide you Name and product team/affiliation as Guest Name.<br />
<br />
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.<br />
<br />
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm<br />
<br />
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/<br />
<br />
Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.<br />
</i><br />
<br />
''Back to the URT agendas list page: [[URT_meetings_agendas]]</div>Bschullehttps://wiki.egi.eu/w/index.php?title=URT:Agenda-03-02-2014&diff=64162URT:Agenda-03-02-20142014-02-03T13:57:07Z<p>Bschulle: /* UNICORE */</p>
<hr />
<div>{|<br />
|-<br />
| [http://connect.ct.infn.it/egi-inspire-sa1/ Audio conference link] <br />
| ''Conference system is Adobe Connect, no password required.''<br />
|-<br />
| [https://wiki.egi.eu/wiki/URT:Agenda_template#Audio_conference_details Audio conference details] <br />
| [https://indico.egi.eu/indico/conferenceDisplay.py?confId=2027 Indico page]<br />
|}<br />
<br />
{{TOC right}}<br />
<br />
= UMD releases status =<br />
<br />
== Status of the products verification/staged rollout ==<br />
<br />
=== Next UMD-3 releases ===<br />
<br />
=== Ready to be released ===<br />
<br />
= Updates from the product teams =<br />
This section is directly contributed by the product teams. Please, add under your section the scheduled releases with a short comment about the updates introduced and where they are going to be released (EMI repositories, EPEL, private repositories ecc), linking external pages with these information is ok, but please add at least the expected date of the next release. It is important to discuss, within the URT, changes that may affect directly or indirectly other products. The text will be copied into the agenda of the next URT meeting, PT will just need to check that all the information are up to date.<br />
Please, feel free to alter the template if it doesn't feet with your needs.<br />
<br />
== APEL ==<br />
* Release version x.y.z Expected: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
== ARC ==<br />
* Release 13.11 version 4.0.0 released<br />
** Main changes: Major release, new BDB job storage, new infosys startup scripts, direct DQ2 support, improved WebDAV support, improved proxy handling<br />
** Other information: Currently in EPEL testing repo.<br />
<br />
== Argus ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information: <br />
== dCache ==<br />
* dCache Release Schedule<br />
** Main changes: released dcache-srmclient 2.2.22 to EMI-2 and EMI-3<br />
** new Releases for UMD-2 dcache-server 2.2.17 and UMD-3 dcache-server 2.6.17 could be pulled from EMI<br />
** Other information:<br />
<br />
== DPM/LFC ==<br />
* Next releases: 1.8.7 has been released to EPEL<br />
** Other information: https://svnweb.cern.ch/trac/lcgdm/attachment/wiki/Dpm/dpmrelnotes_082013-1.txt <br />
<br />
== GFAL/lcg_utils ==<br />
* Release version: gfal2 update (v2.4.8), first release of gfal2-util (replacement for lcg_util), davix update (v0.2.8)<br />
** Main changes: : https://svnweb.cern.ch/trac/lcgutil/wiki/Release_status<br />
** Other information: Bugfixes<br />
<br />
== FTS ==<br />
* Release version FTS3 (v3.1) is available in EPEL<br />
** Main changes: <br />
*** FTS 3 is the replacement of FTS 2. It has been a pilot service tested by WLCG for several months and now it is ready to go to production.<br />
*** Details: https://svnweb.cern.ch/trac/fts3/roadmap<br />
** Other information:<br />
<br />
== BDII ==<br />
<br />
New release of the BDII that decommissions the FCR mechanism in the top BDII. <br />
<br />
The update also defines a new default value for the cache validity in the top BDII that is 4 days. <br />
<br />
New packages are available in EMI 2 and EMI 3 repositories. For more details:<br />
<br />
http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-11-02-12-2013-v-3-6-1-1#BDII_core_v_1_5_5<br />
<br />
http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-11-02-12-2013-v-3-6-1-1#BDII_top_v_1_1_4<br />
<br />
== EMIR ==<br />
* Release version: <br />
** Main changes: <br />
** Other information:<br />
<br />
== UNICORE ==<br />
We will publish packages for UMD via AppDB at https://appdb.egi.eu/store/software/unicore<br />
<br />
* UCC 7.0.1 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
* UNICORE/X 7.0.0 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
* Gateway 7.0.0 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
* Registry 7.0.0 Expected on: 2014-03-01<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== LB ==<br />
* Release version w.k.j Expected on: 2013-12-20<br />
** 4.0.12, 3.2.12<br />
** Main changes: Fixes<br />
** Latest releases<br />
*** L&B 4.0.11-1 (EMI-3), released Fri 21 June 2013 through the EMI repos, available officially since July 8 from EMI repos.<br />
*** https://github.com/CESNET/glite-lb/wiki/Glite-l%26b-release-page#wiki-LB_40111<br />
*** L&B 4.0.11-1 (EMI-2), released Fri 21 June 2013 through the EMI repos, available officially since July 8 from EMI repos.<br />
*** https://github.com/CESNET/glite-lb/wiki/Glite-l%26b-release-page#wiki-LB_32111<br />
<br />
== Gridsite ==<br />
* Release version: GridSite 2.2.1: https://github.com/CESNET/gridsite/wiki/Gridsite-release-page#wiki-GridSite_2211<br />
** Main changes: revision of GridSite, turning off server-side TLS tickets support, which has been turned on by default since OpenSSL 1.0. More elaborate support will be provided in a later revision.<br />
** Other information:<br />
<br />
== Proxyrenewal ==<br />
* Release version: PX 1.0.25 (ProxyRenewal 1.3.25): https://github.com/CESNET/proxyrenewal/wiki/Px-release-page#wiki-PX_10251<br />
** Main changes: revision for ProxyRenewal, which makes sure 1024-bit keys are explicitly requested from Globus, overriding the current Globus default of 512 bits.<br />
** Other information:<br />
<br />
== CANL ==<br />
* Release version: caNl, v. 2.2.1, containing caNl-c v. 2.1.3 & caNl-java v. 1.3.1<br />
** Main changes: Fixed handling of the KeyUsage attribute in proxies created by caNl-java.<br />
*** https://github.com/eu-emi/canl-java/issues/62<br />
*** https://github.com/CESNET/canl-c/wiki/caNl-c-Release-Page#wiki-caNlc_2131<br />
** Other information:<br />
<br />
== gLite- security ==<br />
* Release version w.k.j Expected on: 2013-xx-yy<br />
** Main changes: (including other products affected)<br />
** Other information:<br />
<br />
== CREAM ==<br />
<br />
* Plan to release version: Update EMI 2 & EMI 3 - 31 Oct.2013<br />
** BLAH 1.20 4 (EMI 3)<br />
** CREAM SLURM module 1.0.1 (EMI 3)<br />
** CREAM TORQUE module 2.1.2 (EMI 3)<br />
** CREAM 1.14.6 (EMI 2)<br />
** Main changes:<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=96171 GGUS #96171 - Missing CE information from SLURM infoprovider]<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=95751 GGUS #95751 - MPI support for SLURM jobs ]<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=96703 GGUS #96703 - Wrong total cpu count from PBS infoprovider]<br />
** Other information:<br />
<br />
== STORM ==<br />
<br />
* Next release: Oct. 2013<br />
** STORM 1.11.3 (EMI 3)<br />
** Main changes:<br />
*** Mainly WebDAV issues<br />
** Other information:<br />
<br />
== VOMS ==<br />
* Next releases: Oct 2013<br />
** VOMS Clients v. 3.0.4, VOMS API Java v. 3.0.2 (EMI 3)<br />
** VOMS Admin server v. 3.3.0 (EMI 3)<br />
** Main changes:<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=97555 GGUS #97555 - Serializing private key using pkcs#8 encoding confuses dCache clients]<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=95660 GGUS #95660 - Socket timeout can lead to VOMS Server hanging in endless loop]<br />
*** Migrate Java API to CAnL 1.3<br />
*** [https://issues.infn.it/jira/issues/?jql=project%20%3D%20VOMS%20AND%20fixVersion%20%3D%20%22VOMS%20Admin%20server%20v.%203.3.0%22%20AND%20resolution%20is%20not%20EMPTY VOMS Server fixed issues]<br />
** Other information:<br />
<br />
<br />
== WMS ==<br />
* Next releases: EMI 3 - 31 Oct. 2013<br />
** WMS 3.6.1 (EMI 3)<br />
** Main changes:<br />
*** Sec. Vulnerabilities<br />
*** [https://ggus.eu/ws/ticket_info.php?ticket=96733 GGUS #96733 - glite_wms_wmproxy_server prints taint check warnings]<br />
*** Other information: <br />
<br />
<br />
== Globus ==<br />
* The RHEL/CentOS/SL update from version 6.4 to 6.5 caused problems for the globus gatekeeper:<br />
** https://ggus.eu/ws/ticket_info.php?ticket=99406<br />
* The problem was caused by updating openssl from version 1.0.0 to version 1.0.1.<br />
* One globus package (globus-gssapi-gsi) was identified as behaving differently when compiled against openssl 1.0.0 and 1.0.1. (It is the only one that has a requires on libcrypto.so.10(OPENSSL_1.0.1)(64bit) when compiled against openssl 1.0.1)<br />
* Using a recompiled globus-gssapi-gsi package makes the globus-gatekeeper work again.<br />
* Packages in Fedora updates testing and EPEL testing, please provide feedback (karma)<br />
<br />
== QCG ==<br />
* Release version 3.2.0, Ready to be released<br />
** Main changes: <br />
*** QCG-Broker<br />
**** SHA2 certificates support<br />
**** Improved support for parallel and multi-scale applications<br />
**** Migration from CoG 1.8 to jGlobus2<br />
**** Migration from Tomcat to Jetty servlet container<br />
**** Support iRODS transfers<br />
**** Support for http:// http:// transfers (stage-in only)<br />
**** Advance reservation of nodes. <br />
**** Bug fixes<br />
*** QCG-Broker Client<br />
**** SHA2 certificates support<br />
**** Configurable columns in qcg-list and qcg-rlist commands<br />
**** New qcg-resub command for resubmitting jobs<br />
**** New "#QCG include" directive in simple description format<br />
**** Full support for interactive tasks. <br />
*** QCG-Computing<br />
**** Performance optimization of the GetFactoryAttributes method<br />
**** GPUSCount extension element in SLURM module<br />
**** Bug fixes<br />
*** QCG-Notification<br />
**** New configuration option for disabling CurrentMessages (set to true in the default service config file)<br />
**** Updated requirement for qcg-core to the version 3.2.0.<br />
**** Move to the newer version of libxml2 (from 2.6.27 to 2.9.1). <br />
**** Updated the database configuration script.<br />
**** WorkingDirectory location changed to the $localstate/log/qcg/qcg-ntf directory (in the service config file). <br />
**** Fix: removed a doubled database rollback.<br />
**** Fix: repaired a memory leak related with not freeing the fault data. <br />
**** Other minor corrections.<br />
** Other information:<br />
<br />
= Other topics =<br />
= Other topics =<br />
== UMD to sign packages ==<br />
So far UMD did not sign RPMs or DEB produced by the product teams, relying on the check of the EMI or EPEL gpg keys. To be able to get new middleware updates as soon as the product teams release, UMD team is considering to sign the RPMs that can be imported also from repositories or web locations. <br />
<br />
== UMD-2 decommission == <br />
'''The EMI 2 [[PROC16#Decommissioning_deadline |decommissioning deadline]] is 31-05-2014'''.<br />
<br />
Details:<br />
* by 01-03-2014: new EMI 2 version probes are tested returning WARNING<br />
* on 03-03-2014: EMI 2 version monitoring probes start returning CRITICAL, alarms are displayed in the [https://operations-portal.egi.eu/dashboard Operations Dashboard]<br />
* 30-04-2014: end of security updates and support of EMI 2<br />
* 31-05-2013: EMI 2 [[PROC16#Decommissioning_deadline |decommissioning deadline]] after this date all the EMI-2 services must be decommissioned, upgraded to a supported version or in downtime.<br />
<br />
Affected software:<br />
<br />
*ARC v2.*<br />
*ARGUS v1.5.*<br />
*BDII Site ''older'' than v1.2.0<br />
*BDII Top ''older'' than v1.1.0<br />
*CREAM v1.14.*<br />
*dCache v2.2.*<br />
*DPM ''older'' than v1.8.6<br />
*EMI-UI v2.*<br />
*EMI-WN v2.*<br />
*FTS v.2.2.8<br />
*StoRM ''older'' than v.1.11.0<br />
*VOMS v.2.*<br />
<br />
I will update the list adding Globus and UNICORE.<br />
<br />
= AOB =<br />
<br />
= Minutes = <br />
<br />
= Audio conference details =<br />
<i><br />
Room link: http://connect.ct.infn.it/egi-inspire-sa1/<br />
<br />
Please provide you Name and product team/affiliation as Guest Name.<br />
<br />
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.<br />
<br />
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm<br />
<br />
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/<br />
<br />
Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.<br />
</i><br />
<br />
''Back to the URT agendas list page: [[URT_meetings_agendas]]</div>Bschulle