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-27-05-2013"

From EGIWiki
Jump to navigation Jump to search
 
(10 intermediate revisions by 3 users not shown)
Line 7: Line 7:
| [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1656 Indico page]
| [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1656 Indico page]
|}
|}
 
[[Category:Middleware]]
[[Category:URT]]
 
{{TOC right}}
{{TOC right}}


Line 49: Line 52:
** globus-gridftp 5.2.4
** globus-gridftp 5.2.4
** gsisshterm 1.3.5
** gsisshterm 1.3.5
[http://repository.egi.eu/2013/05/14/release-umd-3-0-0/ UMD 3.0.0] was released on 2013-05-14.


=== UMD-3: Products ready for the next UMD release ===
=== UMD-3: Products ready for the next UMD release ===


* EMI wms  3.5.1
* EMI wms  3.5.1
Next update of UMD-3 is expected in two weeks time. StoRM needs to be released in UMD-3 to allow sites deploying StoRM from UMD-1 to upgrade to a supported version. The date can be '''middle of June''', as soon as possible after the successful staged rollout of the new StoRM version.
The target is to release as many updates as possible without delaying the UMD release. If there are updates being relesed, that need to be included in the next UMD update, PTs are strongly recommended to let EGI-SA2 know through the URT list/wiki pages.


=== UMD-2: General status of new updates ===
=== UMD-2: General status of new updates ===
Line 72: Line 81:
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. <br>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.
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. <br>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.
<br>Please, feel free to alter the template if it doesn't feet with your needs. ''Note: if your product is missing in the list, please add a new section.''
<br>Please, feel free to alter the template if it doesn't feet with your needs. ''Note: if your product is missing in the list, please add a new section.''
''For the meeting 2013-05-27 updates for'':
* CREAM
* StoRM
* QCG


== APEL ==
== APEL ==
Line 134: Line 148:
*** 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]
== STORM ==
== STORM ==
* Release version w.k.j Expected on: 2013-xx-yy
* Release version 1.11.1 Expected on: 2013-05-27
** Main changes: (including other products affected)
** Main changes:
** Other information:  
*** 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:
*** [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]
 
== VOMS ==
== VOMS ==
* Release version w.k.j Expected on: 2013-xx-yy
* Release version w.k.j Expected on: 2013-xx-yy
Line 153: Line 177:
* Release version 3.0.x Expected on: 2013-06-30
* Release version 3.0.x Expected on: 2013-06-30
** Main changes: Candidate for the first UMD release
** Main changes: Candidate for the first UMD release
** Other information: RPMs 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/


Please inform us about the UMD schedule. When we have to be ready and with what to be included into upcoming UMD updates.
Please inform us about the UMD schedule. When we have to be ready and with what to be included into upcoming UMD updates.
Line 169: Line 193:
** StoRM, waiting for the first release in UMD-3, will it be enabled?
** StoRM, waiting for the first release in UMD-3, will it be enabled?


= AOB =  
== Products ID cards ==
 
Place to record information more static about the products currently supported by the product teams.
Currently it includes:
* Supported releases
* Support calendar
* Release channels
 
Available here: [[URT:UMD products ID cards]]
 
It can be edited by URT members, Peter added a first set of information, to be verified.
 
= AOB =
Next meeting scheduled for June 10th, 15:00 CEST


= Audio conference details =
= Audio conference details =

Latest revision as of 12:51, 5 July 2013

Audio conference link Meeting time 15:00 CEST. No Passowrd required
Audio conference details Indico page


UMD releases status

Next UMD releases

Status of the products verification/staged rollout

UMD-3: In verification/staged rollout for UMD-3

  • EMI :
    • dpm 1.8.6-3
    • px 1.3.32
    • lb. 4.0.92
    • cream-lsf 2.0.2
    • cream-slurm 1.0.0 (new product)
    • slurm-wn 1.0.0 (new product)
    • cream-sge. 2.0.1
    • mpi 1.5.0
    • UNICORE:
      • x6 6.0.0
      • client6 6.0.0
      • registry6 6.0.0
      • tsi6 5.1.0
      • xuudb 2.0.0
      • gateway 5.0.0
      • hila 2.4.0
    • ARC:
      • arc-ce 3.0.1
      • arc-core.3.0.1
      • arc-clients 3.0.1
      • arc-infosys 3.0.1
  • IGE :
    • globus-default-security 5.2.4
    • security-integration 3.0.0
    • globus-gridftp 5.2.4
    • gsisshterm 1.3.5

UMD 3.0.0 was released on 2013-05-14.

UMD-3: Products ready for the next UMD release

  • EMI wms 3.5.1

Next update of UMD-3 is expected in two weeks time. StoRM needs to be released in UMD-3 to allow sites deploying StoRM from UMD-1 to upgrade to a supported version. The date can be middle of June, as soon as possible after the successful staged rollout of the new StoRM version.

The target is to release as many updates as possible without delaying the UMD release. If there are updates being relesed, that need to be included in the next UMD update, PTs are strongly recommended to let EGI-SA2 know through the URT list/wiki pages.

UMD-2: General status of new updates

UMD 2.5.0 was released last week, including:

  • GSI-SSHTerm 1.3.4
  • Globus GridFTP 5.2.3
  • Globus GRAM5 5.2.3
  • CREAM Torque module 2.0.2
  • TORQUE server config 1.0.1
  • BLAH 1.18.3
  • LB 3.2.10
  • globus-32-bit 5.2.4
  • WMS 3.4.1
  • globus 5.2.4

Released security patch for BLAH.

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. Note: if your product is missing in the list, please add a new section.

For the meeting 2013-05-27 updates for:

  • CREAM
  • StoRM
  • QCG

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:

DPM/LFC

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

GFAL/lcg_utils

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

FTS

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

BDII

  • 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

  • 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/

Please inform us about the UMD schedule. When we have to be ready and with what to be included into upcoming UMD updates.

Other topics

SHA-2 readiness

Currently EGI is maintaining a wiki page with the product versions supporting SHA-2, using the information gathered by EMI and IGE. The wiki page is accessible here: SHA-2 support middleware baseline.
Note:

  • The version number listed in the wiki page will be used for an active monitoring that will start after the end of EMI-1 decommissioning
    • Check the versions reported, contact Peter or Cristina for any correction
  • Some products are still missing:
    • dCache, has sha-2 support been released yet?
    • StoRM, waiting for the first release in UMD-3, will it be enabled?

Products ID cards

Place to record information more static about the products currently supported by the product teams. Currently it includes:

  • Supported releases
  • Support calendar
  • Release channels

Available here: URT:UMD products ID cards

It can be edited by URT members, Peter added a first set of information, to be verified.

AOB

Next meeting scheduled for June 10th, 15:00 CEST

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.