EUROPEAN MIDDLEWARE INITIATIVE

Transcription

1 EUROPEAN MIDDLEWARE INITIATIVE MSA EMI REF ERENCE RELE AS ES EC MILESTONE: MS18 Document identifier: EMI_MS18_v1.0.doc Activity: Lead Partner: Document status: Document link: SA1 INFN Final

2 Copyright notice: Copyright (c) Members of the EMI Collaboration See for details on the copyright holders. EMI ( European Middleware Initiative ) is a project partially funded by the European Commission. For more information on the project, its partners and contributors please see This document is released under the Open Access license. You are permitted to copy and distribute verbatim copies of this document containing this copyright notice, but modifying this document is not allowed. You are permitted to copy this document in whole or in part into other documents if you attach the following reference to the copied elements: "Copyright (C) Members of the EMI Collaboration. ". The information contained in this document represents the views of EMI as of the date they are published. EMI does not guarantee that any information contained herein is error-free, or up to date. EMI MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, BY PUBLISHING THIS DOCUMENT.

3 Delivery Slip Name Partner / Activity Date Signature From Cristina Aiftimiei INFN/SA1 22/01/2011 Approved by PEB 20/02/2011 Document Log Issue Date Comment Author / Partner 1 22/01/2011 Milestone sent to PEB for review 2 20/02/2011 Final version sent to PEB 3 Cristina Aiftimiei/ INFN Cristina Aiftimiei/ INFN Document Change Record Issue Item Reason for Change 1 2 3

4 MILESTONE REPORT EMI plans to have at least a baseline reference release per year to introduce the major functionality changes and improvements foreseen by the DNA1.3 Technical Development Plan 1. EMI 0 (Zugspitze) is an exercise release designed to understand how to apply the agreed procedures, find problems with tools and processes and in general fine tune the EMI software engineering process before the EMI 1 release. The outcome of EMI 0 is not for external consumption. The goal of EMI 0 is to prepare a consistent, coherent repository of non-conflicting packages without any specific commitment on functionality. This milestone reflects the integration effort of all software products within EMI under one build environment, a first necessary step towards having a unique distribution. The EMI 0 activity is described in detail into a dedicated twiki page 2 containing information on: Mandatory platforms General guidelines followed, that will be applied for all EMI-Releases Specific EMI-0 Guidelines ETICS-configuration schedule status of the various PTs activity EMI-0 nightly-builds results ETICS-responsible persons & external-dependencies lists The operational and infrastructural resources used consist of: Infrastructural resource: o Build & Test System, with a new platform and Worker Nodes, sl5_x86_64_gcc412epel o Repositories: AFS: /afs/cern.ch/project/emi/repository/dist YUM/APT repository based on AFS and HTTPD services provided by CERN: Operational Resources: o Weekly EMT phone-conferences: Agendas: Audio & video conference tool: EVO ( under the dedicated EMI community o EMT mailing list: o EMT actions and EMI-0 tasks tracking tool:

5 The resulting EMI 0 packages, making up the first EMI Reference Releases list, are available in the EMI 0 repository. The milestone was originally planned for October The delay in achieving this was mainly due to the new way of managing the external dependencies, the need to adapt certain components to use packages with the versions available from the OS/EPEL repositories, like globus and gsoap, to improve conformance with EMI (Fedora/Debian) packaging guidelines. Technical details can be found at the dedicated EMI-0 Activity twiki page used to share important information with all users and keep every project member updated on the EMI 0 procedures, status, achievements, and issues. Actions taken to gradually resolve the build problems: the corresponding middleware representatives were informed regularly, during the weekly EMT meeting, about the build status, for which minutes 3 are available; components with problems and the actions taken to resolve those problems were tracked in the EMI-EMT tracker 4 ; PTs whose components had problems were followed also through direct s exchange. If these problems continue to exist the PEB/PTB are consulted and necessary beneficiary leader are informed in order to make sure the PTs put the building process to a higher priority. A list of of software components and their build status is present also in Annex A of this document. Annex B contains a table with the main reasons for the failing components

6 ANNEX A: List of software products, and the build status of their components Product PT components status (build yes/no) A-REX ARC Grid Manager ARC gridftp jobplugin interface ARC CE-Cache ARC CE-staging ARC LRMS modules JANITOR JURA accounting hook pre-ws compute CLI (ng*) WS compute CLI (arc*) libarcclient libarcdata2 pre-ws data CLI (ng*) WS data CLI (arc*) ARC DMCs ARC gridftp server ARIS EGIIS ARC Grid Monitor ARC infoproviders update-crls nordugridmap arcproxy HED HED security HED LIDI HED language bindings MPI-start MPI-utils CREAM BLAH CEMon ARC Compute Element ARC Compute Clients ARC Data Libraries ARC Classic SE ARC Information System ARC Security Utils ARC Container glite MPI glite Job Management arc0 - yes arc1 - yes glite-mpi yes mpi-start yes yaim-mpi yes cream-ce.blahp - yes cream-ce.cemonitor - yes cream-ce.cemonitor-api-java - yes cream-ce.cream - yes cream-ce.cream-api-java - yes cream-ce.cream-common - yes cream-ce.cream-interface - yes cream-ce.cream-job-plugin - yes cream-ce.cream-utils - yes cream-ce.osg-ce-plugin - yes cream-ce.yaim-cream - yes cream-ui.cemonitor-cli - yes cream-ui.cream-cli - yes cream-ui.cream-client-api-c - yes jdl.jdl-api-cpp - yes

7 jobwrapper jdl.jdl-api-java - yes WMS wms.ice - no wms.jobsubmission no wms.wmproxy - no wms.wmproxy-interface - yes wms.wms-broker - no wms.wms-brokerinfo no wms.wms-classad-plugin yes wms.wms-common yes wms.wms-configuration yes wms.wms-helper no wms.wms-ism yes wms.wms-manager no wms.wms-matchmaking yes wms.wms-purger yes wms.yaim-wms yes wms-ui.brokerinfo-access yes wms-ui.wmproxy-api-cpp - yes wms-ui.wmproxy-api-java yes wms-ui.wmproxy-api-python yes wms-ui.wms-ui-api-python no wms-ui.wms-ui-commands - no wms-ui.wms-ui-configuration - yes FTS CERN Data fts.agents-common - no fts.config-service - yes fts.delegation-api-c - no fts.delegation-cli - no fts.glite-fta_oracle - yes fts.glite-ftm - yes fts.glite-fts_oracle - yes fts.sd2cache - yes fts.srm-api-c - no fts.srm-util-cpp - no fts.srm2-api-c - no fts.test-utils - yes fts.transfer-agents - no fts.transfer-cli - no fts.transfer-fts - no fts.transfer-interface - yes fts.transfer-load-generator - no fts.transfer-monitor-gridview - yes fts.transfer-monitor-report - yes fts.transfer-monitor-schema - yes fts.transfer-proxyrenewal - no fts.transfer-scripts - yes fts.transfer-url-copy - no fts.util-c - yes fts.yaim-fts - yes

8 DPM lcgdm.dpm - yes lcgdm.dpm-copy-server-mysql - yes lcgdm.dpm-copy-server-oracle - yes lcgdm.dpm-devel - yes lcgdm.dpm-dsi - no lcgdm.dpm-httpd-cgi - no lcgdm.dpm-httpd-mod_dpmput - yes lcgdm.dpm-httpd-mod_keyauth - yes lcgdm.dpm-httpd-service - yes lcgdm.dpm-httpd-shell - yes lcgdm.dpm-libs - yes lcgdm.dpm-name-server-mysql - yes lcgdm.dpm-name-server-oracle - yes lcgdm.dpm-nfs - no lcgdm.dpm-perl - yes lcgdm.dpm-python - yes lcgdm.dpm-python25 - no lcgdm.dpm-python26 - yes lcgdm.dpm-rfio-server - yes lcgdm.dpm-server-mysql - yes lcgdm.dpm-server-oracle - yes lcgdm.dpm-xrootd - no lcgdm.glite-se_dpm_disk - yes lcgdm.glite-se_dpm_mysql - yes lcgdm.glite-se_dpm_oracle - yes lcgdm.lcg-dm - yes lcgdm.lcg-dm-oracle - no lcgdm.lcg-dm-py25 - no lcgdm.lcg-dm-py26 - no lcgdm.lcgdm-devel - yes lcgdm.lcgdm-libs - yes LFC GFAL lcgdm.lfc - yes lcgdm.lfc-devel - yes lcgdm.lfc-libs - yes lcgdm.lfc-perl - yes lcgdm.lfc-python - yes lcgdm.lfc-python25 - no lcgdm.lfc-python26 - no lcgdm.lfc-server-mysql - yes lcgdm.lfc-server-oracle - yes lcgdm.yaim-dpm - yes lcgdm.yaim-lfc - yes lcgutil.gfal - no lcgutil.gfal-py25 lcgutil.gfal-py26

9 lcg_util dcache server dcache client StoRM SE AMGA server AMGA client APEL parsers APEL publisher HLR-Clients HLR-sensors BDII Glue model dcache StoRM AMGA APEL Client DGAS Client glite Information System lcgutil.build-common-cpp - yes lcgutil.cgsi-gsoap - yes lcgutil.is-interface - yes lcgutil.lcg-util - no lcgutil.lcg-util-py25 lcgutil.lcg-util-py26 lcgutil.srm-ifce - no lcgutil.yaim-lcgutil - yes dcache.dcap - yes dcache.glite-se_dcache_info_0 dcache.glite- SE_dcache_nameserver_0 dcache.glite-se_dcache_pool_0 dcache.glite-se_dcache_srm_0 dcache.server - yes dcache.srmclient - yes dcache.voms2gplasma - yes dcache.yaim-dcache storm.backend - no storm.checksum - yes storm.client - yes storm.common - yes storm.dynamic-info-provider - yes storm.frontend - no storm.glite-yaim-storm - yes storm.gridftp-dsi - yes amga.amga-cli - no amga.amga-server - no amga.glite-amga_postgres - yes apel.condor - yes apel.core - yes apel.glite-apel - yes apel.lsf - yes apel.pbs - yes apel.publisher - yes apel.sge - yes apel.yaim - yes dgas.common - yes dgas.hlr-clients - yes dgas.hlr-sensors - yes bdii.bdii-config-site - yes bdii.bdii-config-top - yes bdii.bdii-resource - yes bdii.bdii-site - yes bdii.bdii-top - yes bdii.glite-bdii_site - yes bdii.glite-bdii_top - yes bdii.glite-info-plugin-fcr - yes bdii.glite-info-provider-ldap - yes bdii.glite-info-provider-release - yes bdii.glite-info-provider-service - yes bdii.glite-info-site - yes bdii.glite-info-static - yes

10 glite service info providers glite site info provider gstat-validation lcg-info and lcg-infosites SAGA-SD SAGA-ISN VOMS VOMS-Admin Trustmanager Util-Java LCAS LCMAPS LCMAPS-plugins-c-pep glexec SCAS Hydra STS Delegation Java SAGA-SD-RAL VOMS glite security bdii.glite-info-update-endpoints - yes bdii.glue-schema - yes bdii.yaim-bdii - yes org.glite.security.voms-admin-server - yes org.glite.security.voms-api-cpp - yes org.glite.security.voms-api-java - yes org.glite.security.voms-api - yes org.glite.security.voms-clients - yes org.glite.security.voms-mysql - yes org.glite.security.voms-oracle - yes voms-server - yes voms.voms-javadoc - yes org.glite.security.voms-admin-client - yes voms.emi-voms-mysql - yes sac.glexec_wn - no sac.ees - yes sac.glexec - yes sac.glexec-mkgltempdir - yes sac.glexec-wrapper-scripts - yes sac.jobrepository sac.lcas - yes sac.lcas-interface - yes sac.lcas-lcmaps-gt4-interface - no sac.lcas-plugins-basic - yes sac.lcas-plugins-check-executable - yes sac.lcas-plugins-voms - yes sac.lcmaps - yes sac.lcmaps-interface - yes sac.lcmaps-plugins-afs - afs sac.lcmaps-plugins-basic - yes sac.lcmaps-plugins-c-pep - no sac.lcmaps-plugins-gums - yes sac.lcmaps-plugins-jobrep sac.lcmaps-plugins-scas-client - yes sac.lcmaps-plugins-verify-proxy - yes sac.lcmaps-plugins-voms - yes sac.lcmaps-plugins-voms-attr sac.lcmaps-rules-parser sac.lcmaps-without-gsi - yes sac.saml2-xacml2-c-lib - yes sac.scas - no sac.yaim-glexec-wn - yes sac.yaim-scas - yes java-security.trustmanager - yes java-security.trustmanager-axis - yes java-security.trustmanager-axis2 java-security.trustmanager-test java-security.trustmanager-test-certs java-security.trustmanager-tomcat -

11 SLCS Pseudonymity yes delegation.delegation-interface - yes delegation.delegation-java - yes delegation.delegation-service-java - no hydra.ssss - yes hydra.cli - no hydra.service - no hydra.catalog-interface - no org.glite.security.gss org.glite.security.gsoap-plugin org.glite.security.proxyrenewal CESNET Security jobid.api-c - yes jobid.api-cpp - yes jobid.api-java - yes lbjp-common.db - yes lbjp-common.gsoap-plugin - yes lbjp-common.gss - yes lbjp-common.jp-interface - yes lbjp-common.log - yes lbjp-common.maildir - yes lbjp-common.server-bones - yes lbjp-common.trio - yes px.glite-px - yes px.myproxy-yaim - yes px.proxyrenewal - yes org.gridsite gridsite.apache - yes gridsite.commands - yes gridsite.core - yes gridsite.shared - yes Argus Argus-EES Argus argus.glite-argus - yes argus.gsi-pep-callout - yes argus.pap - yes argus.pdp - yes argus.pdp-pep-common - yes argus.pep-api-c - yes argus.pep-api-java - yes argus.pep-cli - yes argus.pep-common - yes argus.pep-server - yes argus.yaim-argus-server - yes L&B Server L&B lb.client - yes lb.client-java - yes lb.common - yes lb.doc - yes lb.glite-lb - yes lb.harvester - yes

12 L&B Client lb.logger - yes lb.server - no lb.state-machine - yes lb.types - yes lb.utils - yes lb.ws-interface - yes lb.ws-test - no lb.yaim - yes U. TSI U. Target System U. XNJS Access UAS-C UAS-D U. BES U. WS Interfaces U. Registry CIP UCC U. client libs U. Client and APIs HILA UNICORE/X U. Container WSRFLite UNICORE Gateway XUUDB UVOS UNICORE Security U. XACML Entity U. authorization data providers U. security libraries EMI Service Registry Registry EMI messaging layer Messaging unicore.gateway - yes unicore.hila-shell - yes unicore.hila-unicore6 - yes unicore.registry - no unicore.ucc - yes unicore.unicorex - no unicore.xuudb - yes

13 ANNEX B: Reasons of Failures PT WMS FTS DPM LFC GFAL lcg_util STORM AMGA glite Security L&B Client UNICORE Reasons of Failures dependencies on gsoap dependencies on vdt.globus, gsoap, m4 macros dependencies on vdt.globus, gsoap, m4 macros missing dependency on python26 problems with m4 macors problems with m4 macors dependencies on boost (version not in SL5), xmlrpc-c, xmlrpc-devel (not present in EPEL problems with unixodbc dependency problems with m4 macors, with one glibusgridmap-callout-error package dependency on other PT components (lcas) change in SourceForge certificate that needed a change in the VCS checkout command