URT:Agenda-08-07-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

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.

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:
  • 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
  • dCache Release Schedule
    • 2.6.5 will be released 16 July 2013 (SHA-2 support)
    • 2.2 none SHA-2 release 23 July 2013
    • 2.2 SHA-2 release 30 July 2013

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

STORM

  • 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

Release in UMD from new repositories (not EMI/IGE/QCG)

Beside using the repositories currently configured for UMD (EMI/IGE/QCG) the software provisioning process could be extended to add more repositories.

Note: the following options are not implemented yet, they are under discussion.

All the product packages are in EPEL

Retrieve packages for the UMD software provisioning directly from EPEL testing' Product teams expressed interest in moving the EGI quality assurance process earlier in the PTs release process. In order to receive feedback from the verification/staged rollout before the EPEL official release.

  • Pull the packages directly from EPEL testing
  • Pull only the packages that are released by the PT, not all the EPEL dependencies (which will continue to be installed from EPEL at site level).
  • Release in UMD after the verification/staged rollout
    • The EPEL production release can be a requisite for the release in UMD (question)
  • Product team must provide extensive information about the packages to be downloaded from EPEL for the UMD repositories

Not all the pakcages are in EPEL

If the product team is releasing in EPEL, as primary repository, but with additional packages still released in other repositories. An example could be the metapackages that cannot be released in EPEL, and which may be released in the EMI repositories.

  • It's not entirely impossible to submit a product to UMD from more than one repository (e.g. EMI and EPEL)
    • All the packages (e.g. from EPEL testing and the metapackages in the EMI repositories) must be available at the moment of submission to UMD
  • Using AppDB would simplify things

Release using AppDB

AppDB allows to build a product release (or a release of multiple products). Authorized developers can submit a new release of their products uploading the packages composing the new release in few minutes of work. The products released in this way are automatically available in a repository that can be used to import to UMD or as a normal yum/apt repository.

  • The advantage is that every product team can handle the releases in AppDB, and then be automatically integrated with the UMD release processes.
  • Easy to produce releases when packages are scattered in multiple repositories
  • If this solution becomes popular, the plan would be to integrate even more the AppDB processes with the UMD software release process.

Release using product team proprietary repository

This option is not impossible, but it would be preferable to use the AbbDB as entry point.

Participating to the EGI Technical forum

Relevant sessions during the TF (16-20 September, Madrid):

  • Timeline online
  • Middleware session: Monday
  • Information system workshop: Wednesday morning
  • URT F2F: Wednesday afternoon


AOB

- GGUS AB - Forum for the announcements

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.

Back to the URT agendas list page: URT_meetings_agendas