URT:Agenda-24-06-2013
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.
UMD-3: Products recently verified
UMD-3: Products in staged rollout
UMD-3: Products ready for the next UMD release
UMD-2: General status of new updates
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 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
- build time deps:
- dCache 2.6 has the following
- build time deps:
- open-jdk-7
- maven3
- runtime deps:
- open-jdk-7
- build time deps:
DPM/LFC
- Release version 1.8.7-1 Expected on: July 2013
- Main changes:
- Connection pooling on the ns daemons
- 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
- Other information:
- Main changes:
DPM/LFC is moving to a new build infrastructure and new development/testing lifecycle.
GFAL/lcg_utils
- Release version GFAL 2.3 Expected on: July 2013
- Main changes: :
- Http support
- gsiftp/xrootd bugfixes
- Details: https://its.cern.ch/jira/browse/LCGUTIL/fixforversion/11028
- Other information:
- Main changes: :
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:
- Main changes:
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:
- 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:
- Main changes:
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
- Main changes:
- Fix for vulnerability
- BDII configuration improvements
- glue-validator improvements
- Details: http://tinyurl.com/BDIISavannahBugs
- Other information:
- Main changes:
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:
- Main changes:
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:
- Main changes:
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 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:
- EGI will continue to pull products from the EMI or IGE repositories
- More repositories will be gradually integrated with the EGI sw provisioning infrastructure
- 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.
What are the information needed
- Technology Provider: TPs can release multiple products as long as they're available in the same repository.
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.