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.

Difference between revisions of "URT:Agenda-10-06-2013"

From EGIWiki
Jump to navigation Jump to search
 
(32 intermediate revisions by 4 users not shown)
Line 13: Line 13:


== Next UMD releases ==
== Next UMD releases ==
* UMD 3.1.0: ''17~20 June 2013''
* UMD 2.5.1: Probably this week
* UMD 2.6: ''End of the month'' (2.5.1 and 2.6.0 could be merged in a single one)


== Status of the products verification/staged rollout ==
== Status of the products verification/staged rollout ==
Line 19: Line 23:
=== UMD-3: Products recently verified ===
=== UMD-3: Products recently verified ===


=== UMD-3: Products in staged rollout ===
=== UMD-3: Products in staged verification&rollout ===
* StoRM 1.11.1, finished the verification, now under staged rollout
* BDII under verification, likely to be released in the next UMD release


=== UMD-3: Products ready for the next UMD release ===
Products in verification:
* argus
* emi-UI
* glite-Cluster
* gridftp and globus-default-security
* gsisshterm (gsisshterm is '''not''' SHA2 compliant)
 
Products in SR:
* unicore-*
* cream-lsf
* DPM
* glite-MPI
 
Products ready to be released:
* Security update of EMI wms (3.5.1)
* px 1.3.32
* lb 4.0.92


=== UMD-2: General status of new updates ===
=== UMD-2: General status of new updates ===
* Releasing the WN 2.0.1-1 probably this week. This will include also glexec and gfal/lcg-utils


= Updates from the product teams =
= Updates from the product teams =
Line 29: Line 52:
Please, feel free to alter the template if it doesn't feet with your needs.
Please, feel free to alter the template if it doesn't feet with your needs.


'''New updates for BDII, DPM, GFAL and FTS'''


== APEL ==
== APEL ==
Line 42: Line 66:
** Main changes: (including other products affected)
** Main changes: (including other products affected)
** Other information:  
** 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 ==
* Release version 1.8.7-1 Expected on: July 2013
* Release version 1.8.7-1 Expected on: July 2013
** Main changes:
** Main changes:
*** DB support
*** Connection pooling on the ns daemons
*** Bug fixes
*** Bug fixes in the information provider and DB backends
*** Configuration improvements
*** Stability and robustness enhancements for dmlite
*** EMIR integration
*** Storage Accounting record for DPM
*** MacOSx support for dmlite
*** Details: https://its.cern.ch/jira/browse/LCGDM#selectedTab=com.atlassian.jira.plugin.system.project:roadmap-panel&allVersions=true
*** Details: https://its.cern.ch/jira/browse/LCGDM#selectedTab=com.atlassian.jira.plugin.system.project:roadmap-panel&allVersions=true
** Other information:
** Other information:
DPM/LFC is moving to a new build infrastructure and the development work is being reorganized.
DPM/LFC is moving to a new build infrastructure and new development/testing lifecycle.


== GFAL/lcg_utils ==
== GFAL/lcg_utils ==
* Release version 2.3 Expected on: July 2013
* Release version GFAL 2.3 Expected on: July 2013
** Main changes: :  
** Main changes: :  
*** Http support
*** Http support
Line 58: Line 113:
*** Details: https://its.cern.ch/jira/browse/LCGUTIL/fixforversion/11028
*** Details: https://its.cern.ch/jira/browse/LCGUTIL/fixforversion/11028
** Other information:
** Other information:
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 and then few more days to release GFAL.
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 version gfal2-python 1.2 Expected on: July 2013
** Main changes:
*** GFAL 2.0 python bindings
*** Details: https://its.cern.ch/jira/browse/LCGUTIL/fixforversion/11029
** Other Information:
Release under EPEL review. It will take 2-3 weeks to be reviewed and released.


== FTS ==
== FTS ==
* Release version 3.0.0 Expected on: July 2013
* Release version 3.0.0 Expected on: July 2013
** Main changes: https://svnweb.cern.ch/trac/fts3/roadmap
** Main changes:
*** FTS 3 is the replacement of FTS 2. It has been a pilot service tested by WLCG for several months and now it is ready to go to production.
*** Details: https://svnweb.cern.ch/trac/fts3/roadmap
** Other information:
** Other information:
FTS 3 is about to be released in EPEL testing where it will stay for at least a couple of weeks.
FTS 3 is about to be reviewed EPEL. It will then take 2-3 weeks to be reviewed and released.


== BDII ==
== BDII ==
Line 74: Line 138:
*** Details: http://tinyurl.com/BDIISavannahBugs
*** Details: http://tinyurl.com/BDIISavannahBugs
** Other information:
** Other information:
This is a minor release to fix a security vulnerability and implement some enhancements in both BDII configuration and glue-validator.
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.


== UNICORE ==
== UNICORE ==
Line 109: Line 173:
*** Reduced number of tomcat restart in YAIM
*** Reduced number of tomcat restart in YAIM
** Other information:
** Other information:
*** [https://issues.infn.it/issues/?jql=project%20%3D%20CREAM%20AND%20fixVersion%20%3D%20%221.15.2%22%20AND%20resolution%20is%20not%20EMPTY CREAM 1.15.2 - solved issues]
*** [https://issues.infn.it/jira/browse/CREAM/fixforversion/10913 CREAM 1.15.2 - solved issues]


== STORM ==
== STORM ==
Line 121: Line 185:
*** Improve PROPFIND performance
*** Improve PROPFIND performance
** Other information:
** Other information:
*** [https://issues.infn.it/issues/?jql=project%20%3D%20StoRM%20AND%20fixVersion%20%3D%20%221.11.1%22%20AND%20resolution%20is%20not%20EMPTY STORM 1.11.1 - solved issues]
*** [https://issues.infn.it/jira/browse/STOR/fixforversion/10810 STORM 1.11.1 - solved issues]


== VOMS ==
== VOMS ==
Line 139: Line 203:
** Main changes: Candidate for the first UMD release
** 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 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 issues =  
= Other issues =  
Line 152: Line 215:
** Updated the versions for: StoRM and dCache.
** Updated the versions for: StoRM and dCache.
** dCache reported that the support can be backported (to the previous golden release?).
** dCache reported that the support can be backported (to the previous golden release?).
== Quality criterion: SHA-2 support to be critical ==
* From October 2013 EUGridPMA plans to start distributing in production SHA-2 based certificates
* Next version of the Quality Criteria document is due for September, in that version the sha-2 support criterion will be ''mandatory''
* Middleware not supporting sha-2 will be unusable starting from October, UMD must provide this capability before the deadline.
'''Proposal''':
#All the products already in the UMD queue will consider the SHA-2 requirement as non-critical
#* If the product fails the SHA-2 test, it will be specified in the release notes with a disclaimer for the Site Administrators.
# For every new product submitted to UMD - starting from today - the SHA-2 requirement will be considered '''mandatory'''.
#* RT ticket creation date >= 10 June 2013
'''Current situation''':
* Currently there were no issues found during verification (for UMD-3) for SHA-2 support


= Audio conference details =
= Audio conference details =

Latest revision as of 20:50, 19 June 2013

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: 17~20 June 2013
  • UMD 2.5.1: Probably this week
  • UMD 2.6: End of the month (2.5.1 and 2.6.0 could be merged in a single one)

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 recently verified

UMD-3: Products in staged verification&rollout

  • StoRM 1.11.1, finished the verification, now under staged rollout
  • BDII under verification, likely to be released in the next UMD release

Products in verification:

  • argus
  • emi-UI
  • glite-Cluster
  • gridftp and globus-default-security
  • gsisshterm (gsisshterm is not SHA2 compliant)

Products in SR:

  • unicore-*
  • cream-lsf
  • DPM
  • glite-MPI

Products ready to be released:

  • Security update of EMI wms (3.5.1)
  • px 1.3.32
  • lb 4.0.92

UMD-2: General status of new updates

  • Releasing the WN 2.0.1-1 probably this week. This will include also glexec and gfal/lcg-utils

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.

New updates for BDII, DPM, GFAL and FTS

APEL

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

ARC

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

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.

UNICORE

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

LB

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

Gridsite

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

Proxyrenewal

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

CANL

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

gLite- security

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

CREAM

  • Release version 1.15.2 Expected 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:

STORM

  • Release version 1.11.1 Expected 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:

VOMS

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

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 issues

Status of the PT ID Cards

The page URT:UMD_products_ID_cards has not been edited (10:37 am), ok if the information are correct. Please, note that this will be used in ~ one year time to decommission unsupported software.

Status of the SHA-2 baseline versions page

  • Page: SHA-2_support_middleware_baseline
  • It cannot be edited by all the URT members, please contact me if there are corrections in the versions.
    • Updated the versions for: StoRM and dCache.
    • dCache reported that the support can be backported (to the previous golden release?).

Quality criterion: SHA-2 support to be critical

  • From October 2013 EUGridPMA plans to start distributing in production SHA-2 based certificates
  • Next version of the Quality Criteria document is due for September, in that version the sha-2 support criterion will be mandatory
  • Middleware not supporting sha-2 will be unusable starting from October, UMD must provide this capability before the deadline.

Proposal:

  1. All the products already in the UMD queue will consider the SHA-2 requirement as non-critical
    • If the product fails the SHA-2 test, it will be specified in the release notes with a disclaimer for the Site Administrators.
  2. For every new product submitted to UMD - starting from today - the SHA-2 requirement will be considered mandatory.
    • RT ticket creation date >= 10 June 2013

Current situation:

  • Currently there were no issues found during verification (for UMD-3) for SHA-2 support

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.