Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

URT:UMD products ID cards

From EGIWiki
Jump to navigation Jump to search


This page reports the main information about the products currently released in UMD:

  • Support calendar for the major releases currently supported
  • Preferred release channels to get the future updates

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.

Products ID cards

Former EMI products

AMGA

  • UMD-2 : 2.3.0
    • End of security support 2014-04-30
  • Planning to continue to take care of maintaining the code in the medium-long term with updates to the current major release.
  • Intend to provide standard support.
  • No plan for a new major release

APEL

  • UMD-2 : 3.3.0
    • End of security support 2014-04-30
  • UMD-3 :
    • Packages are available on github page: http://apel.github.io/
    • Latest version of APEL software is 1.1.3 (lib, parsers, client, server) and the SSM messaging software is 2.1.1.
  • Planning to continue to support the current version by maintaining the code in the medium to long term.
    • 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.
  • We are committing to running the accounting repository service for the next 2 years.
    • 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.

ARC

  • UMD-2 : 2.0.1
    • End of security support 2014-04-30
  • UMD-3 : 3.0.1
    • End of security support 2014-04-30
  • The policy of NorduGrid is to have one major release per year.
    • We support the current release until the next major release is out.
    • Users are then advised to move to the new major release.
    • Feature requests are treated in the same way as bugfixes.
  • Next major release is planned for November 2014 so 13.11 will be supported until then.
    • 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.
    • It will be supported until the next major release, so most likely until end of 2015.

ARGUS

  • UMD-2 : 1.5.0
    • End of security support 2014-04-30
  • UMD-3 : 1.6.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

BDII core

  • UMD-2 : 1.4.0
    • End of security support 2014-04-30
  • UMD-3 : 1.5.0
  • Support for the BDII is guaranteed.
  • 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.
  • 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.

BDII Site

  • UMD-2 : 1.1.0
    • End of security support 2014-04-30
  • UMD-3 : 1.2.0
  • Support for the BDII is guaranteed.
  • 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.
  • 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.

BDII Top

  • UMD-2 : 1.0.1; 1.0.2
    • End of security support 2014-04-30
  • UMD-3 : 1.1.X
  • Support for the BDII is guaranteed.
  • 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.
  • 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.


BLAH

CANl

  • UMD-3 : 2.0.7
    • canl-c++ - is part of ARC

canl-c

  • Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform.
  • There are currently no plans to retire EMI-3 products
  • No tangible plans for other major releases

canl-java

  • currently there are two parallel canl-java major releases:
    • 1.?.?: in EMI repos and Maven central
    • 2.?.?: in Maven central only, i.e. no RPMs/debs.
  • Differences:
    • 2.x depends on latest BouncyCastle, 1.x on 1.46.
    • So far the branches are pretty similar (most of 2.x features and all bugfixes were backported to 1.x).
    • No plans nor time to think about moving 2.x to EMI repositories (due to problems with BC - packaging and compatibility).
  • 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.
  • minor features - to the end of 2014. Bigger developments won't be included.
  • standard support - to the end of 2014, but if needed it can be prolonged.
  • security support - to the end of 2014
  • no major release planned (besides 2.x which are different wrt to BC dependency).
    • 2.x are backwards incompatible due to conflicting dependency usage.

Cluster

  • UMD-2 : 2.0.0
    • End of security support 2014-04-30
  • UMD-3: v. 1.15.1
  • Product NO LONGER SUPPORTED

CREAM LSF module

CREAM (S)GE module

  • UMD-3 : 2.1.0
    • best effort support
    • End of Full Support: 2014-04-30
    • End of Standard Updates: 2014-10-30
    • End of Security Updates & EOL: 2015-04-30
  • New major release:
    • Probably in 2015

CREAM Torque module

CREAM

dCache-srmclient

  • UMD-3 : 2.2.22
    • 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.

DCACHE

  • UMD-3: 2.2.22
    • support the dCache server 2.6 branch until at least end of April 2015
  • new golden release 2.10 in July, this, as always will then be supported for two years
  • golden releases are often backward incompatible
    • Within golden releases we try not to implement new features to keep them stable
    • do not differentiate between standard support and security support only, if it is supported, it is supported.
  • support calendar: http://www.dcache.org/downloads/1.9/index.shtml

DPM

  • UMD-3 : 1.8.8
  • Support for DPM/LFC and gfal2 is indefinite.
    • LFC:
      • Atlas and LHCb both intend to stop using LFC by the end of 2014
      • LFC will still be supported for other VOs, albeit at best-effort.
    • GFAL/lcg_util will not be supported after October 2014
  • Not planning a major release - in the "major=backward incompatible" sense

EMI UI

EMI WN

EMIR

  • UMD-2 : 1.2.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

GFAL/lcg_util

  • UMD-3 : 1.16.0
    • will not be supported after October 2014

gLExec-wn

  • UMD-3 : 1.2.0
    • 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
    • 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
    • security bug fixes will not be rolled in with standard updates, but will always be available as individual fixes
    • we are willing to coordinate API and ABI interface deprecation time lines with EGI UMD and in coordination with other EMI partners.
  • We are supporting our other components (ARGUS-EES) under the same conditions.
  • All support and maintenance will continue under the Nikhef PDP reference conditions:
    • security and critical bug fix support is included,
    • 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,
    • the necessary software distribution and integration services based on standard OS platform distribution mechanisms and packaging formats,
    • 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.
  • 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.

MPI

  • UMD-3 : 1.5.0
    • support is going to be provided.
    • Both adding features as requested by users and maintaining the code.
      • In principle it will be done by updating the current major release.
  • No plan for retiring the current version. New features will be implemented on this release if no major changes are needed for supporting them.
  • will be supported during this year, 2014, for sure. Probably the support will continue next year, but that is still undefined.
  • No plan for a new major release

gridsite

  • UMD-3 : 2.2.0
    • Proactive maintenance, possibly new features if required. These products are used also in EGI's Federated Cloud platform.
  • There are currently no plans to retire EMI-3 products
  • No tangible plans for other major releases
  • Backaward incompatible changes:
    • 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.

gsoap-gss

  • UMD-2 : 3.1.4
    • End of security support 2014-04-30
  • UMD-3 : 3.2.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

jclassads

  • UMD-2 : 2.4.3
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

lb-metapack

  • UMD-2 : 3.2.8
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

L&B

  • UMD-2 : 3.2.7; 3.2.10
    • End of security support 2014-04-30
  • UMD-3 : 4.0.4
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

lcg-info-clients

  • UMD-3 : 1.0.1
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

lcg-info-dynamic-software

  • UMD-2 : 1.0.7
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

LFC

  • UMD-2 : 1.8.3; 1.8.4; 1.8.5; 1.8.6
    • End of security support 2014-04-30
  • UMD-3 : 1.8.6
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

myproxy

  • UMD-2 : 1.0.1
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

QosCosGrid [QCG]

  • UMD-2 : ----
  • UMD-3: 3.2.0
    • Support model: last revision of a released major release
    • full support: at least to the end of the year 2015, hopefully longer
    • (security) bug fixes: at least to the end of the year 2018, hopefully longer
    • 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.
  • Release channels (QCG repository):
  • Product main web page: www.qoscosgrid.org

STORM

torque-server

torque-wn

trustmanager

  • UMD-2 : 3.1.4
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE Client6

  • UMD-2 : 5.0.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE Gateway

  • UMD-2 : 4.3.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE HILA

  • UMD-2 : 2.3.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE Registry6

  • UMD-2 : 5.0.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE TSI6

  • UMD-2 : 5.0.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE UVOS

  • UMD-2 : 1.5.1
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE XUUDB

  • UMD-2 : 1.3.2
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

UNICORE/X6

  • UMD-2 : 5.0.0
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

VOMS admin

VOMS

WMS

yaim-core

  • UMD-3 : 5.1.1
    • End of security support 2014-04-30
  • Release channels (e.g. EMI repos, EPEL repos..):
  • Product main web page:

Former IGE products

globus-32-bit

  • UMD-2 : 5.2.2; 5.2.4
    • End of security support ????-??-??
  • UMD-3 : 5.2.4
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

globus-default-security

  • UMD-2 : 5.2.1; 5.2.2
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

globus-gram5-ige

  • UMD-2 : 5.2.2
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

globus-gram5

  • UMD-2 : 5.2.1; 5.2.2; 5.2.3
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

globus-gridftp

  • UMD-2 : 5.2.2; 5.2.3
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

globus-gsissh

  • UMD-2 : 4.3.5; 5.3.5
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

globus-myproxy

  • UMD-2 : 5.6.3; 5.9.1
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

globus-rls

  • UMD-2 : 5.2.2
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

gridway

  • UMD-2 : 5.12.0
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

gsisshterm

  • UMD-2 : 1.3.4
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

saga

  • UMD-2 : 1.6.1; 1.6.2
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:

security-integration

  • UMD-2 : 2.2.0; 2.2.1
    • End of security support ????-??-??
  • Reelase channels (e.g. EPEL repos, IGE repos..):
  • Product main web page:
Retrieved from "https://wiki.egi.eu/w/index.php?title=URT:UMD_products_ID_cards&oldid=67888"