UMD 1.6.0 Contents
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.6.0
The release timeline will be as follows:
12 March 2012 | Release day freeze |
27 March 2012 12:00 CET | Release contents freeze |
2 April 2012 | Release day |
Useful links
- Which products are planned for UMD 1.6.0
- 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.6.0; the order of entries in the table indicate the relative priority per platform with which the referenced products will be taken through the provisioning process.
Platform | EGI Capability | Product | available on | Provider release | Notes | ||
---|---|---|---|---|---|---|---|
SL5 | SL6 | Debian6
| |||||
Globus
| |||||||
Job Execution | GridSAM 2.3.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 | OGF BES based front-end to GRAM5
| |
Job Scheduling | GridWay 5.8.2 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
Parallel Job, Job Execution | GRAM5 5.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
File Transfer | GridFTP 5.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
Interactive Job Management | GSISSH 4.3.4 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
Interactive Job Management | GSISSHTerm 1.3.2 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
Authorisation | DefaultSecurity 5.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
Credential Management | MyProxy 5.5.2 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
Metadata Catalogue | RLS 5.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 |
| |
Client API | SAGA Adaptors for IGE 1.6.1 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | IGE 2.0 | Does not include JSAGA
| |
gLite
| |||||||
Attribute Authority | VOMS 2.0.7 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 14 | Fixes very urgent issue: https://ggus.eu/tech/ticket_show.php?ticket=78892
| |
BDII core 1.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 13 | Fixes a security vulnerability Internal component to other BDII products
| ||
BDII core 1.3.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 14 |
| ||
Information Discovery | BDII site 1.1.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 13 |
| |
Gridsite 1.7.19 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 14 |
| ||
File Access, File Transfer, Storage Management |
StoRM 1.8.2 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 13 |
| |
UNICORE 6
| |||||||
Authentication | Gateway 4.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 11 |
| |
Attribute Authority | XUUDB 1.3.2-3 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 11 |
| |
Attribute Authority | UVOS 1.5.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 10 |
| |
Job Scheduling, Storage Management |
X6 4.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 12 |
| |
Parallel Job, File Access, Job Execution | TSI6 4.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 12 |
| |
Client Tools | Client 4.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 12 |
| |
Information Discovery | Registry 4.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 12 |
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 | [UMD 1.6.0 RC1] | Michel
|
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 | [UMD 1.6.0 RC1] | Michel
|
3 | "Known Issues & Installation notes" | Check that sub-actions are finished according to requirements | TSA2.1 | T - 4 | see below | Michel
|
3.1 - Create Wiki entry | Create a Wiki entry for the release at UMD-1:UMD-1.6.0 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 | https://wiki.egi.eu/wiki/UMD-1:UMD-1.6.0 | Kostas
| |
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 | https://wiki.egi.eu/wiki/UMD-1:UMD-1.6.0 | Mario, Alvaro
| |
3.3 - Document Staged Rollout findings | Collect all issues, warnings, workarounds etc. to the "Known issues & Installation notes" wiki entry. | TSA1.3 | T - 7 | https://wiki.egi.eu/wiki/UMD-1:UMD-1.6.0 | Mario
| |
4 | Compile UMD release documentation | UMD release metadata will be published in the UMD Repository and must cover the following sections:
TSA1.3, TSA2.3 will contribute. TSA1.3 and all SA2 tasks review drafts and give comments. |
TSA2.1 | 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 | http://repository.egi.eu/category/umd_release_candidates/umd_1_rc2/ | Kostas
|
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 | http://repository.egi.eu/category/umd_release_candidates/umd_1_rc2/ | Kostas
| |
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:
|
TSA2.1 | after T |