JRA1.1 - EMI Technical Objectives

• 2010-10-15 Morris : Initial setup of technical objectives based on DNA1.3.1 version 0.12 beta (some outcome Geneva F2F).
• 2010-10-21 Morris : Update of new rendering and ordering of technical objectives based on DNA1.3.1 version 0.12 (official after Geneva F2F)
• 2010-10-31 Morris : Update again of new version of the overall technical plan based on DNA1.3.1 version 0.14 (project-wide review version)
• 2010-11-01 Morris : Year 1 objectives are updated according to version 0.14 of DNA1.3.1 and status tracking pages added
• 2010-11-07 Morris : Year 2 and 3 objectives are updated according to version 0.14 of DNA1.3.1
• 2010-11-09 Morris : Added JRA1 : Component Improvements Technical Objectives for work on components that are not directly related to DNA1.3.1 objectives
• 2010-11-13 Morris : The ARC Security Utils have been added
• 2010-11-16 Morris : Synchronized with final version and GANTT chart of DJRA1.1.1 (Compute Area Work Plan)

• Technical Objectives relevant for the EMI - 1 Release [ More Information ]

• Full description : Component Improvements that are not covered by DNA1.3.1 technical objectives for Year 1
• Objective Version : 2010-11-09
• Technical Objective of JRA1
• Due : M10

The following components are affected in the context of this technical objective :

• dCache
• DPM
• StoRM
• ARC Security Utils
• ARGUS

• Full description : Provide early internal guidelines for integrating messaging into potential EMI target components.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 1
• Due : M10

The following components are affected in the context of this technical objective :

• all EMI services

• Full description : Design a common EMI service registry that is required in order to discover all the service endpoints of the different middleware components.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 2
• Due : M10

The following components are affected in the context of this technical objective :

• EMI registry (new component)

• Full description : Investigate possible use cases for a common standard messaging system in the accounting area.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 3
• Due : M12

The following components are affected in the context of this technical objective :

• APEL-publisher
• DGAS HLR-sensors
• JURA

• Full description : Investigate possible use cases for a common standard messaging system for the service monitoring and management.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 4
• Due : M12

The following components are affected in the context of this technical objective :

• all EMI services

• Full description : Investigate possible use cases for a common standard messaging system for the information services and L&B.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 5
• Due : M12

The following components are affected in the context of this technical objective :

• L&B
• BDII
• EMI Registry (new)

• Full description : Define the Information Flow architecture describing messaging and non-messaging based information exchange of the EMI components (e.g. service registry, information system, accounting, monitoring, and instrumentation). A common information exchange between the EMI components is preferable.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 1
• Due : M9

The following components are affected in the context of this technical objective :

• all EMI services

• Full description : Investigate possible use cases for a common standard messaging system in the computing area.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 2
• Due : M12

The following components are affected in the context of this technical objective :

• All EMI compute area services

• Full description : Investigate possible use cases for a common standard messaging system in the data area.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 3
• Due : M12

The following components are affected in the context of this technical objective :

• All EMI data area services

• Full description : Evaluate integration scenarios with off-the-shelf computing cloud systems to be able to execute grid jobs on those (scaling out to clouds).
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 4
• Due : M12

The following components are affected in the context of this technical objective :

• A-REX
• CREAM
• WMS
• UNICORE/X
• U. TSI
• U. XNJS
• UAS-Compute

• Full description : Glue 2.0 support in job management services and client tools
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 1
• Due : M12

The following components are affected in the context of this technical objective :

• A-REX
• CREAM
• UNICORE - BES
• WMS
• libarcclient
• arc*
• UCC

* Not relevant: U. TSI, U. XNJS, WSRFlite, HILA

• Full description : All storage elements publishing initial GLUE 2.0 storage information and one storage client (library) is capable consuming that.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Data Area - Technical Objective 1
• Due : M12

The following components are affected in the context of this technical objective :

• DPM
• dCache
• StoRM
• GFAL

• Full description : Using https instead of httpg for the SRM protocol as a prototype implementation in one storage element and client (library).
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Data area - Technical Objective 2
• Due : M12

The following components are affected in the context of this technical objective :

• dCache server
• One client

• Full description : All storage elements offering support for the http(s) protocol
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Data Area - Technical Objective 3
• Due : M12

The following components are affected in the context of this technical objective :

• dCache
• StoRM
• DPM

• Full description : All storage elements offering at least a prototype-level support for the "file://" access protocol.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Data Area - Technical Objective 4
• Due : M12

The following components are affected in the context of this technical objective :

• dCache
• StoRM
• DPM

• Full description : Agreement on a minimal common set of security attributes to be used in policies.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Security Area - Technical Objective 1
• Due : M12

The following components are affected in the context of this technical objective :

• ARGUS
• VOMS

• Full description : Component Improvements that are not covered by DNA1.3.1 technical objectives for Year 2
• Objective Version : 2010-11-09
• Technical Objective of JRA1
• Due : M22

The following components are affected in the context of this technical objective :

• none yet

• Full description : Implementation of the agreed common job submission and management methods in all the CEs and compute clients.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 2
• Due : M18

The following components are affected in the context of this technical objective :

• A-REX
• CREAM
• UNICORE - EMS
• libarcclient
• arc*
• CREAM Client
• UCC
• HILA

* Not relevant: U. TSI, U. XNJS, WSRFlite

• Full description : Provide limited interactive access for at least one EMI Computing element.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 3
• Due : M18

The following components are affected in the context of this technical objective :

• A-REX
• CREAM

• Full description : Support for the agreed compute accounting record (UR).
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 4
• Due : M18

The following components are affected in the context of this technical objective :

• A-REX
• CREAM
• UNICORE XNJS
• UAS-Compute
• UNICORE TSI

• Full description : An EMI-blessed delegation solution for at least the computing area.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 5
• Due : M18

The following components are affected in the context of this technical objective :

• A-REX
• CREAM
• U.EMIEX (new)

• Full description : Definition and implementation of initial support for the common SAML profile all over the middleware stacks.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 6
• Due : M18

The following components are affected in the context of this technical objective :

• A-REX
• CREAM
• CEMON
• UNICORE Compute and Data
• UNICORE/X
• ARGUS
• VOMS
• STS
• SLCS
• Hydra

• Full description : Integration of the compute area services with the ARGUS authorization framework.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 7
• Due : M24

The following components are affected in the context of this technical objective :

• CREAM
• CEMON
• WMS
• A-REX
• HED
• UNICORE/X
• UAS-Compute
• ARGUS

• Full description : Initial integration of the storage elements with the ARGUS authorization framework.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 8
• Due : M24

The following components are affected in the context of this technical objective :

• DPM
• dCache
• StoRM
• FTS
• ARGUS

• Full description : The legacy Globus security infrastructure (GSI) will be replaced with a common security solution on TLS/SSL still including the delegation capability.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 9
• Due : M24

The following components are affected in the context of this technical objective :

• DPM
• dCache
• StoRM
• gfal
• WMS
• CREAM
• A-REX
• HED
• libarcclient
• libarcdata2

One additional component (to DNA1.3.1) is needed as well :

• VOMS

• Full description : Adapt or implement monitoring interfaces, sensors, providers for compute, data, security and infrastructure services to allow the use of standard monitoring tools preferably based on the common EMI messaging system.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 10
• Due : M24

The following components are affected in the context of this technical objective :

• all EMI services

• Worked on by the Service Monitoring Task Force (https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1T5TaskForceServiceMonitoring)

• Full description : Investigate service instrumentation interface for compute, data, security and infrastructure services, including remote configuration change and service management, utilizing the messaging system.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 11
• Due : M24

The following components are affected in the context of this technical objective :

• all EMI services

• Full description : Simplified management of security credentials by reducing the complexities of handling certificates and integrating different security mechanisms like Shibboleth and Kerberos across the EMI stack that allows users to use their own authentication system to access a ``Grid''.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Security Area - Technical Objective 2
• Due : M18

The following components are affected in the context of this technical objective :

• STS
• SLCS
• VOMS

• Full description : All storage elements publishing full set of GLUE 2.0 storage information and EMI clients are capable consuming that.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 5
• Due : M24

The following components are affected in the context of this technical objective :

• dCache
• StoRM
• DPM
• UAS-Data
• GFAL
• libarcdata2

• Full description : All storage elements offering support for the WebDav protocol.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 6
• Due : M24

The following components are affected in the context of this technical objective :

• dCache
• StoRM
• DPM

• Full description : Using https instead of httpg for the SRM protocol as a production implementation in all the storage elements and clients.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 7
• Due : M24

The following components are affected in the context of this technical objective :

• dCache
• StoRM
• DPM
• All data clients

• Full description : Overall consolidation of data area by adopting a consistent interpretation of SRM.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 8
• Due : M24

The following components are affected in the context of this technical objective :

• dCache
• StoRM
• DPM
• FTS
• GFAL
• libarcdata2

• Full description : Providing a common set of data access libraries at least between gLite and ARC.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 9
• Due : M24

The following components are affected in the context of this technical objective :

• GFAL
• libarcdata2
• emi_datalib (new)

• Full description : Solve the synchronization problem of the storage elements and the file catalogue.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 10
• Due : M24

The following components are affected in the context of this technical objective :

• LFC
• dCache
• StoRM
• DPM

• Full description : Consolidation and harmonization of compute area clients/APIs.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 5
• Due : M24

The following components are affected in the context of this technical objective :

• libarcclient
• arc*
• CREAM client
• WMS client
• UCC
• HILA

• Full description : Extend job definition language, resource information (GLUE model) and job management service capabilities so that EMI compute clients are able to request access to virtualized resource managers and appliances.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 6
• Due : M24

The following components are affected in the context of this technical objective :

• A-REX
• Janitor
• WMS
• CREAM
• UNICORE EMI-XS
• EMI Compute Clients

• Full description : Provide common authentication libraries supporting X.509 and optionally SAML.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Security Area - Technical Objective 3
• Due : M24

The following components are affected in the context of this technical objective :

• Emi_authNlib (new component)

• Full description :Agreement and full support for a common single X.509 and SAML based Attribute Authority Service integrated with all EMI components.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Security Area - Technical Objective 5
• Due : M24

The following components are affected in the context of this technical objective :

• VOMS
• UVOS

• Full description : Consolidation and reduction in the number of security CLIs so that the users don’t have to face the very different clients and utilities.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Security Area - Technical Objective 4
• Due : M24

The following components are affected in the context of this technical objective :

• EMI security clients and utilities

• Full description : Implement the common EMI Registry.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 6
• Due : M24

The following components are affected in the context of this technical objective :

• EMI Registry (new)

• Full description : Fully utilize and support the GLUE2 information model.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 7
• Due : M24

The following components are affected in the context of this technical objective :

• All EMI services
• all infosys clients

(WMS is included in all EMI services, no need to list seperately)

• Full description : Provide guidelines for 3rd parties to integrate messaging into their service/application based on the EMI experience.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 8
• Due : M24

The following components are affected in the context of this technical objective :

• External products

• Full description : Explore the modifications necessary in the EMI services to take advantages of the elasticity of the clouds resource management model while provisioning grid services within virtual machines (“grid in a cloud” scenario).
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 9
• Due : M24

The following components are affected in the context of this technical objective :

• all EMI services

• Full description : Implement or adapt the accounting record publishers of compute and data area services to use the common messaging system.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 10
• Due : M24

The following components are affected in the context of this technical objective :

• DGAS HLR sensors
• APEL-publisher
• JURA
• new-publisher for data area services

• Full description : Component Improvements that are not covered by DNA1.3.1 technical objectives for Year 3
• Objective Version : 2010-11-09
• Technical Objective of JRA1
• Due : M34

The following components are affected in the context of this technical objective :

• none yet

• Full description : Successful computational usage of emerging computing models i.e. clouds with EMI components (scaling out to clouds).
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 7
• Due : M30

The following components are affected in the context of this technical objective :

• A-REX
• CREAM
• UNICORE TSI
• UNICORE XNJS
• UNCORE EMI-XS

• Full description : Provision of a common MPI execution framework, a “backend” across the different computing services to allow users to execute parallel applications in a uniform way.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 8
• Due : M30

The following components are affected in the context of this technical objective :

• MPI-Start
• MPI-Utils
• BLAH
• CREAM
• WMS
• A-REX
• UNICORE TSI
• UNICORE XNJS
• UAS - Compute

• Full description : Extend the parallel computing capabilities to better address multi-core jobs on all emerging architectures resources, multi-node execution on interconnected clusters; and special scenarios like advanced topologies, FPGAs, GPGPUs
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Compute Area - Technical Objective 9
• Due : M36

The following components are affected in the context of this technical objective :

• MPI-Start
• MPI-Utils
• BLAH
• CREAM
• WMS
• A-REX
• UNICORE TSI
• UNICORE XNJS
• UAS - Compute

• Full description : Completed migration to the common set of data access libraries.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 11
• Due : M36

The following components are affected in the context of this technical objective :

• EMI data access clients

• Full description : Add support for storage space usage accounting on the SE/FTS side, including the refinement, definition and adoption (if/when applicable) of relevant standards.
• Objective Version : 2010-11-07 (DNA1.3.1 - v014)
• Data Area - Technical Objective 12
• Due : M36

The following components are affected in the context of this technical objective :

• dCache
• StoRM
• DPM
• UAS-Data
• FTS

• Full description :Substantial simplification and reduction in the number of security area libraries, internal components and services..
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Security Area - Technical Objective 6
• Due : M36

The following components are affected in the context of this technical objective :

• all security area components

• Full description : Provide a transparent solution for encrypted storage utilizing ordinary EMI SEs.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Security Area - Technical Objective 7
• Due : M36

The following components are affected in the context of this technical objective :

• Pseudonymity
• Hydra

• Full description : Complete migration to the new AuthN libraries.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Cross Area - Technical Objective 12
• Due : M36

The following components are affected in the context of this technical objective :

• all EMI services

• Full description : Consolidation and reduction in the number of information system discovery APIs and CLIs.
• Objective Version : 2010-10-31 (DNA1.3.1 - v014)
• Infrastructure Area - Technical Objective 11
• Due : M36

The following components are affected in the context of this technical objective :

• lcg-info
• lcg-infosite
• gstat-validation
• GFAL
• libarcclient
• HILA
• U. client libs
• SAGA-SD
• SAGA-ISN