Major Release Version in EMI task force
The
Major Release Version in EMI
task force is responsible for defining a strategy to be able to publish in the information system the EMI major version under which EMI components are released.
Task Force Members
- Task Force Responsible:
- Members
Introduction
The publication of the major release of middleware services in the information system is very useful for operational purposes and to monitor the deployment of a major release in the grid infrastructure.
The command
glite-version
together with the
glite-info-provider-release
plugin is used to publish the gLite version, 3.1 o 3.2, of a service in the information system.
glite-version
relies on some information provided by the metapackage in the form of files organised in the following way:
/opt/glite/release/glite-nodetypename/COPYRIGHT
/opt/glite/release/glite-nodetypename/LICENSE
/opt/glite/release/glite-nodetypename/arch
/opt/glite/release/glite-nodetypename/node-version
/opt/glite/release/glite-nodetypename/service
/opt/glite/release/glite-nodetypename/update
In order to configure
glite-info-provider-release
, yaim-core has the function
config_gip_service_release
as documented in the
YAIM twiki.
A similar solution needs to be implemented for EMI, not necessarily following this approach since metapackages are not supposed to contain any files in EMI.
Some ideas have been discussed so far:
- Modify the config file of
glite-info-service
to publish the EMI major release by adding i.e.
get_otherinfo = echo -e "MiddlewareName=EMI\nMiddlewareVersion=1.0\nMetapackageVersion=1.2.3"
- Create an
emi-version
package released only in major releases.
- Mechanism to provide a file like
/etc/grid-middleware
that will contain EMI 1.0 (or gLite3.2, or whatever)
.
Action List
The following actions have been identified:
Action |
Description |
Responsible |
Deadline |
--
MariaALANDESPRADILLO - 23-Mar-2011