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.

UMD 1.7.0 Contents

From EGIWiki
Jump to navigation Jump to search
Technology Software Component Delivery Software Provisioning UMD Middleware Cloud Middleware Distribution Containers Distribution Technology Glossary


Roadmap and Technology | Technology insertion plans UMD Release Schedule Overview | Glossary




The following provides an overview of the planned contents of UMD 1.7.0

The release timeline will be as follows:

14 May 2012 Release day freeze
21 May 2012 Release contents freeze
28 May 2012 Release day

Useful links

UMD 1.7.0

- What is the status of the products planned for UMD 1.7.0?

UMDStore

- Which products are available for immediate publication

EGI Provisioning Dashboard - What is the general Software Provisioning pipeline?

Release plan

The following provides an overview of the planned contents for UMD 1.7.0

Platform EGI Capability Product available on Provider release Notes
SL5 SL6 Debian6


ARC
no information available


dCache


File Access,
File Transfer,
Storage Management
dCache 1.9.15 {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 12


gLite


Metadata Catalogue LFC 1.8.2 for Oracle {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 13
BLAH 1.16.5 {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 15
File Access,File Transfer,Storage Management DPM 1.8.3 {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 15
GFAL/lcg_util 1.12.0 {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 15
Credential Management gLite proxyrenewal 1.3.25 {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 15
Metadata Catalogue LFC 1.8.3 {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 15 May override LFC 1.8.2 for Oracle (see above)
Job Scheduling WMS 3.3.5 {{{SL5}}} {{{SL6}}} {{{Debian6}}} EMI-1 Update 15


Globus


Job Execution GridSAM 2.3.0 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.0
Client API IGE SAGA plugins 1.6.1 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.0
Interactive Job management Globus GSISSH 4.3.5 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1
Interactive Job Management GSISSHTerm {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1
Job Execution GridSAM 4.3.5 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1 May supersede GrudSAM 2.3.0
Job Scheduling Gridway 5.10.1 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1
Job Execution IGE GRAM5 5.2.0 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1 IGE-repackaged GRAM5
Accounting GridSAFE 1.0.1 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1 Initial UR-based accounting solution. Will integrate with EGI Accounting with IGE-3
Authorisation IGE Security integration 2.1.0 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1 Globus-specific LCAS/LCMAPS integration
Data Access OGSA-DAI 4.2.1 {{{SL5}}} {{{SL6}}} {{{Debian6}}} IGE 2.1 Distributed data access using a common standardised access interface OGSA-DAI


UNICORE 6
no information available

Delivery slip

No. Action Description Responsible unit due on References signed off by


1 Freeze UMD release contents Using the UMD Composer add all products that are queued in the UMDStore to a new UMD release bundle. TSA2.1 Before T - 7


2 Update UMD capabilities Check that UMD Capabilities in UMD-1:Capabilities are up to date and in synch with the products in the UMD release. TSA2.1 Before T - 7


3 "Known Issues & Installation notes" Check that sub-actions are finished according to requirements TSA2.1 T - 4


3.1 - Create Wiki entry Create a Wiki entry for the release at UMD-x:UMD-x.y.z using the major (x), minor (y) and revision (z) numbers of the UMD release.
Create sections for each product that is included in the documented UMD release.
TSA2.4 T - 7


3.2 - Document Verification findings Add all findings (bugs, workarounds, etc.) collected in the QC Verification reports to the "Known Issues & Installation notes" wiki entry. TSA2.3 T - 7


3.3 - Document Staged Rollout findings Collect all issues, warnings, workarounds etc. to the "Known issues & Installation notes" wiki entry. TSA1.3 T - 7


4 Compile UMD release documentation UMD release metadata will be published in the UMD Repository and must cover the following sections:
  1. Description
  2. Contact Info
  3. Technical Contact Info
  4. Release Notes
  5. Installation Notes
  6. Known Issues
  7. Change Log

TSA1.3, TSA2.3 will contribute. TSA1.3 and all SA2 tasks review drafts and give comments.

TSA2.3 T - 3


5 Produce and test release candidate(s) Produce as many Release Candidates as required based on the feedback given. If no feedback is given assume the Release Candidate working correctly. For each Release Candidate round new sub-actions need to be created for the delivery slip. TSA2.1 T - 7


5.1 - Produce first release candidate From the list of included products in (1) generate a Release Candidate. Notify TSA2.4 and TSA1.3 of the existence and location of the Release Candidate. TSA2.4 T - 7


5.2 - Test first Release Candidate (Verification) Test the first release candidate for errors and advise TSA2.4 whether to create another Release Candidate. Testing is mandatory for TSA2.3. TSA2.3 T - 5


5.3 - Test the first Release Candidate (SR) Call for volunteers for RC testing among the EAs in Staged Rollout. Collect feedback from participating sites and advise TSA2.4 whether to create another Release Candidate. Testing is optional for TSA1.3. TSA1.3 T - 5


6 Publish UMD release Only when all previous actions are signed off, publish the UMD release. TSA2.1 T


7 Post-release cleanup Post-release actions perform some housekeeping in the UMD release management area, including:
  1. Add the UMD release announcement to UMD release schedule overview
  2. Add text "EGI has released UMD 1.4.0 on 19 December 2011. (Announcement)" linking to the repository's announcement
  3. Remove the entire Release Plan section in the release's Wiki entry
  4. Ensure that the Delivery slip is kept
  5. protect the release wiki entry (hence the delivery slip too) against changes
TSA2.1 after T