URT:Agenda-24-06-2013

From EGIWiki
Jump to: navigation, search
Audio conference link Conference system is Adobe Connect, no password required.
Audio conference details Indico page


UMD releases status

Next UMD releases

  • UMD 3.1.0 scheduled for 25 June 2013
  • UMD 3.2.0 scheduled for 29 July 2013

Status of the products verification/staged rollout

For UMD-3 a comprehensive view can be found in this RT dashboard. Please note that the page could take time to load.


UMD-3: Products ready for the next UMD release

  • UMD-3 Update 1 will be released this week with over 16 products
    • EMI.unicorex6 - 6.0.0
    • EMI.unicore-tsi6 - 5.1.0
    • EMI.unicore-client6 - 6.0.0
    • EMI.unicore-registry6 - 6.0.0
    • EMI.unicore-xuudb - 2.0.0
    • EMI.unicore-gateway
    • EMI.cream-lsf - 2.0.2
    • EMI.arc-ce - 3.0.1
    • EMI.arc-core - 3.0.1
    • EMI.arc-clients - 3.0.1
    • EMI.arc-infosys - 3.0.1
    • EMI.arc-gridftp - 3.0.1
    • EMI.mpi - 1.5.0
    • EMI.dpm - 1.8.6
    • EMI.px - 1.3.32
    • EMI.lb - 4.0.92
    • EMI.bdii 1.5.1
    • EMI.wms - 3.5.1
    • EMI gLite CLUSTER 2.0.0-2

Updates from the product teams

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. Please, feel free to alter the template if it doesn't feet with your needs.


APEL

  • Release version x.y.z Expected: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:

ARC

  • Release version 3.0.3 Expected: 2013-07-31
    • Main changes: bugfix release
    • Other information: none

Argus

  • Release version w.k.j Expected on: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:

dCache

  • Release version w.k.j Expected on: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:
  • What is the exact release process into UMD?
  • Proposed:
   - Release sha-2 compatible dcache-server 2.2 into UMD2 (backport needed)
   - (optional, only if needed) Release of dcache-server 2.6 could be released into UMD-3
  • dCache 2.2 has the following
    • build time deps:
      • open-jdk-6
      • maven3
    • runtime deps:
      • open-jdk-6


  • dCache 2.6 has the following
    • build time deps:
      • open-jdk-7
      • maven3
    • runtime deps:
      • open-jdk-7

DPM/LFC

DPM/LFC is moving to a new build infrastructure and new development/testing lifecycle.

GFAL/lcg_utils

This release depends on Davix 0.2 (initial preview version of http/webdav toolkit) which is under EPEL review. It will take 2-3 weeks to be reviewed and released. Then, GFAL could be released in a few days.

Release under EPEL review. It will take 2-3 weeks to be reviewed and released.

FTS

  • Release version 3.0.0 Expected on: July 2013
    • Main changes:
    • Other information:

FTS 3 is about to be reviewed EPEL. It will then take 2-3 weeks to be reviewed and released.

BDII

  • Release version: Update 2 Expected on: end of July 2013

Development has not started yet. This is a minor release to fix a security vulnerability and implement some enhancements in both BDII configuration and glue-validator.

EMIR

  • Release version w.k.j Expected on: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:

UNICORE

  • Release version w.k.j Expected on: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:

LB

Gridsite

Proxyrenewal

  • No release at this point

CANL

  • No release at this point

gLite- security

  • Release version w.k.j Expected on: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:

CREAM

  • Released version 1.15.2 on: 2013-05-30
    • Main changes:
      • Increased default size for CREAM log files
      • Removed spurious files for CREAM-ES and CEMonitor when those services are not enabled
      • Reduced number of tomcat restart in YAIM
    • Other information:
  • Plan to release version 1.16.0 on: 2013-06-30

STORM

  • Released version 1.11.1 on: 2013-05-27
    • Main changes:
      • StorM publishes wrong values for storage area sizes in the information system
      • Change GPFS Quota Job to leverage native quota info call
      • Ensure storm-gridhttps-server starts automatically on boot
      • Duplicate PtG on a file incorrectly marks it as busy
      • Ensure StoRM services RPM packaging requires OpenJDK
      • Improve PROPFIND performance
    • Other information:
  • Planned to be released - version 1.11.2 on: 2013-06-20
    • Main changes:
      • StoRM native libs call to change_group_ownership does not correctly forward exceptions to the parent java process
      • StoRM GPFS get_fileset_quota_info leaks file descriptors
    • Other information:

VOMS

WMS

  • Release version w.k.j Expected on: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:

Globus

  • Release version w.k.j Expected on: 2013-xx-yy
    • Main changes: (including other products affected)
    • Other information:

QCG

  • Release version 3.0.x Expected on: 2013-06-30
    • Main changes: Candidate for the first UMD release
    • Other information: RPMs SL6/6 of three main QCG components (QCG-Broker, QCG-Computing, QCG-Notifications including dependencies) and QCG-BrokerClient. The release will be published using the offical QCG repository: http://www.qoscosgrid.org/qcg-packages/sl5/x86_64/



Other topics

Products release in UMD

This is an overview of what is technically required for the release of software in UMD. After this meeting, as a follow up of the discussion, SA2 will generate a wiki page under the URT sections to be a reference for the product teams.

How software can be handled by UMD

The packages that compose a product must be available in a yum or apt repository, since UMD currently supports SL5, SL6 and Debian6.

Currently UMD repositories are configured to retrieve products from the following repositories:

  • EMI repository
  • IGE repository
  • QCG repository

If your product team foresee the use of other repositories to distribute the packages, the Software Provisioning Infrastructure must be consequently configured with the new repositories.

For the time being, we propose the following:

  1. EGI will continue to pull products from the EMI or IGE repositories
  2. More repositories will be gradually integrated with the EGI sw provisioning infrastructure
    1. Integration with EPEL may be one of the first if multiple PTs are releasing directly in EPEL. Pulling products form EPEL may require some additional care, compared to an dedicated repository, but if many PTs have chosen EPEL as the preferred distribution channel, EGI SA2 is happy to start working on it.

If, for the future, product teams need a repository to upload their packages we suggest the EGI community repository through the Application Database.

Information needed

Creating a new PPA for UMD requires the following information:

  • Name of Technology Provider: TPs can release multiple products as long as they're available in the same repository.
    • Once multiple repositories are configured for UMD, specify also the repository from where the packages are supposed to be
  • Product name
  • Product version: xx-yy-zz
  • Main web page of the product: link
  • Release notes for this release: link
  • List of metapackages
  • List of the packages updated in this release in the same format as above

Verification of new products

EGI SA2 checks the Quality Control Criteria associated to the components during the verification step. Being the SA2 resources limited, in case of a big backlog this step may delay the release of products in UMD. ARC proposed to add the EGI verification criteria to their certification process, this will streamline the UMD release process, pushing the ARC products directly to Staged Rollout. The templates for the verification report are generated for most of the components and they contain the criteria to be verified: Verification report templates. Refer to the following wiki page for more information:

Note: tests are Optional if a failure does not cause product rejection, but they must be checked anyway.

Changes in the 3rd level support tickets in GGUS

Günter Grein presents an overview of the new workflows implemented after the end of EMI and IGE: Günter's slides

More information in the FAQ_GGUS-Waiting-For-PT-Process.

Audio conference details

Room link: http://connect.ct.infn.it/egi-inspire-sa1/

Please provide you Name and product team/affiliation as Guest Name.

In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.

You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm

Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/

Adobe connect is flash-based, please if you have issues with your configuration try Chrome as browser.

Minutes

Minutes available on the indico page.