URT Meeting January 13th 2014. Minutes.

Agenda:

Participants

Christian Bernardt
João Pina
Cristina Aiftimiei
Mattias Ellert
Peter Solagna
Zdenek Sustr

UMD releases status

Products which finished successfully the SR:

  • ARC 4.0.0
  • Verification done by product team, reduced the testing time.
  • BDII-TOP v. 1.1.4
  • BDII-CORE v. 1.5.5
  • CREAM-TORQUE 2.1.2
  • QCG-NTF v. 3.2.0
  • QCG-COMP v. 3.2.0
  • WMS v. 3.6.2

Next UND-3 update expected by the end of the month.

Next UMD releases

Updates from the product teams

Globus: IGE released an update in EPEL of Globus gatekeeper to fix the compatibility with the latest openssl version.

Gridsite: released both in EMI-3 and EMI-2 the update to be compatible with the latest openssl releases.

BDII: New release that disable the FCR mechanism in the top-bdii. The update also defines a new default value for the cache validity in the top BDII that is 4 days.

New packages are available in EMI 2 and EMI 3 repositories.

Decommission of UMD-2

Decommission calendar for UMD-2 services has been approved:

All UMD-2 components must be decommissioned or upgraded by the end of May 2014.

Product teams who support products in UMD-2 (e.g. EMI-2 products) which support calendar goes beyond the end of April 2014 should provide information about the calendar in the URT mailing list, and update the URT:UMD_products_ID_cards.

Changes in the UMD process for import of products

So far UMD processes resolved the dependencies in the EMI, IGE or QCG repositories to create the most complete product entries for the UMD framework.

Some product team moved permanently to EPEL, other product teams are still releasing to EMI but not as a main repository, in many cases for UMD is impossible to resolve the dependencies getting a reasonable set of libraries (e.g. without downloading the EPEL dependencies not under the PT responsibility).

UMD team has started at the end of last year to list directly the list of relevant RPMs that compose a product entry in the UMD release process. The rpm files are then downloaded with a direct wget into the UMD repositories.

Pros: RPMs or DEB can be downloaded from YAIM or Debian repositories but also from web sites with a wget easier to import into UMD repositories the products.

Cons: Since there is no check about the integrity of the dependencies in UMD until the products are tested for installation, it is important that product teams provide correct list of rpms once they want to submit their products to UMD. Also 32 bit libraries where available.

Next meeting

February 3rd, 15:00 CETon Adobe connect