EMI2priorities

EMI 2 was released, and effort for early adoption needs to be redistributed so that important products of EMI 1 and EMI 2 are properly staged rollout. It is thus necessary to review the current list of Early Adopters for each supported EMI product. Staged Rollout for gLite 3.2 will be only conducted in case of security fixes, and ad-hoc volunteers will be contacted in case of need.

Only products that undergo the full staged rollout process will be released in UMD.

In order to proceed, priorities of products need to be assessed. The following table is a proposal for distribution of priorities. It will be revised according to the NGI input. The proposal is based on the SA1 survey Operations/Platform_Deployment_Survey as well as on the current availability of EAs: https://www.egi.eu/earlyAdopters/teams.

For ARC and UNICORE components in Debian 6, Early Adopters have been separately contacted. No other products for Debian 6 were released in EMI 2.

See EMI 2 Release Notes

EMI 2 priorities: proposal

PROPOSED POLICY:

• products that are flagged as HIGH priority (3), will be released BOTH for sl5 AND sl6.
• the sl6 version will always undergo full verification.
• In case of no staged rollout for one of the two platforms, the product will be released in UMD also for the missing platform. This will be documented in the release notes of UMD in case this happens.

KEY:

• GREEN: top priority product
• ORANGE: low priority component with EAs
• YELLOW: to check

	# of Eas		Priority: 3 High - 1 Low
Component	SL6	SL5	SL6	SL5
EMI2 AMGA	0	1		1
EMI2 APEL	1	1	2	0 (already in sl5)
EMI2 ARC-CE (introduces backward incompatibility with clients older than ARC 11.05)	2	1	3 (complete LDAP/XML GLUE 2 rendering supported)	3 (complete LDAP/XML GLUE 2 rendering supported)
EMI2 ARC-Clients	1	0	3	3
EMI2 ARC-Infosys	0	1	3 (complete LDAP GLUE2.0 rendering)	3 (complete LDAP GLUE2.0 rendering)
EMI2 ARGUS	0	0	2	2
EMI2 BDII-site	1	1	1	1 (already in EMI 1)
EMI2 BDII-top	0	1	1	1 (already in EMI 1)
EMI2 CANL (Common AUTH Library)	0	0	0	0
EMI2 CLUSTER	0	0
EMI2 CREAM	3	4	3 (Support for RFC proxies, Publication in Glue 2.0 format finalized, support of cluster mode)	3 (Support for RFC proxies, Publication in Glue 2.0 format finalized, support of cluster mode)
EMI2 CREAM-LSF	0	0	3 (as CREAM)	3 (as CREAM)
EMI2 CREAM-SGE	0	1	3 (as CREAM)	3 (as CREAM)
EMI2 CREAM-Torque	2	2	3 (as CREAM)	3 (as CREAM)
EMI2 dCache	1	3	3 (support of file protocol, webdav, NFS4.1, ssh2)	3 (support of file protocol, webdav, NFS4.1, ssh2)
EMI2 DPM-mysql	2	1	3 (support of NFS4.1/pNFS frontend and SEMSG - Catalog Synchronization)	0 (staged rollout already undertaken for EMI 1)
EMI2 EMIR	0	0
EMI2 GLEXEC	0	0
EMI2 LB	1	1	1	1
EMI2 LFC	0	0	3 (support of SEMSG - Catalog Synchronization)	0 (staged rollout undertaken for EMI 1)
EMI2 MPI	0	1	1	1
EMI2 MyPROXY	0	1	1	1
EMI2 Nagios	0	0
EMI2 Pseudonymity	0	0
EMI2 Storm	0	1	3 (first release of gridHTTPs)	3 (first release of gridHTTPs)
EMI2 Torque server	0	0	3 (new version of maui packages redistributed from the third-party repository)	3 (new version of maui packages redistributed from the third-party repository)
EMI2 Torque WN	2	1	3 (same priority as WN)	3 (same priority as WN)
EMI2 UI (WMS client is backward incompatible)	2	0	3 (same priority as WN). WMS client backward incompatible	3 (same priority as WN). WMS client backward incompatible
EMI2 UNCORE-TSI	0	0
EMI2 UNICORE-Client	0	0
EMI2 UNICORE-Gateway	0	0
EMI2 UNICORE-HILA	0	0
EMI2 UNICORE-Registry	0	0
EMI2 UNICORE-UVOS	0	0
EMI2 UNICORE-X	0	0
EMI2 UNICORE-XUUDB	0	0
EMI2 VOMS (minor upgrade, backward compatible)	0	0	3 (major number of bug fixes released in EMI 2 for VOMS admin)	3 (major number of bug fixes released in EMI 2 for VOMS admin)
EMI2 WN	4	1	3 (in order to offer improved I/O that is available from sl6)	3 (in order to upgrade from gLite 3.2 WNs by end of Sep 2012)
EMI2 Wnodes	0	0