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

Contents


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.


UMD-3: Products ready for the next UMD release

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

ARC

Argus

dCache

   - 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


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

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

BDII

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

UNICORE

LB

Gridsite

Proxyrenewal

CANL

gLite- security

CREAM

STORM

VOMS

WMS

Globus

QCG



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:

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:

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.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export