The Experts below are selected from a list of 159 Experts worldwide ranked by ideXlab platform
R Zappi - One of the best experts on this subject based on the ideXlab platform.
-
An effective XML based name mapping mechanism within StoRM
Journal of Physics: Conference Series, 2008Co-Authors: E. Corso, A Forti, A Ghiselli, L Magnoni, R ZappiAbstract:In a Grid environment the naming capability allows users to refer to specific data resources in a physical storage system using a high level logical identifier. This logical identifier is typically organized in a file system like structure, a hierarchical tree of names. Storage Resource Manager (SRM) services map the logical identifier to the physical location of data evaluating a set of parameters as the desired quality of services and the VOMS attributes specified in the requests. StoRM is a SRM service developed by INFN and ICTP-EGRID to manage file and space on standard POSIX and high performing parallel and cluster file systems. An upcoming requirement in the Grid data scenario is the orthogonality of the logical name and the physical location of data, in order to refer, with the same identifier, to different copies of data archived in various storage areas with different quality of service. The mapping mechanism proposed in StoRM is based on a XML document that represents the different storage components managed by the service, the storage areas defined by the site administrator, the quality of service they provide and the Virtual Organization that want to use the storage area. An appropriate directory tree is realized in each storage component reflecting the XML Schema. In this scenario StoRM is able to identify the physical location of a requested data evaluating the logical identifier and the specified attributes following the XML Schema, without querying any database service. This paper presents the Namespace Schema defined, the different entities represented and the technical details of the StoRM implementation.
Gerard Lyons - One of the best experts on this subject based on the ideXlab platform.
-
Reflective channel hierarchies
Springer-Verlag, 2003Co-Authors: Edward Curry, Desmond Chambers, Gerard LyonsAbstract:Hierarchical channel structures are used to create granular sub-channels from a parent channel. Utilized in routing situations that are more or less static, they require that the channel Namespace Schema be both well defined and universally understood. The publish/subscribe messaging model currently requires a message publisher to place messages into a specific channel within the hierarchy. A relocation of responsibility for channel selection logic from the publishing client to the middleware service would open up static channel hierarchies to the application of reflective techniques. This shift in responsibilities enables the service more control over the definition, creation and maintenance of the channel hierarchy. The service is now able to apply reflective and adaptive techniques to dynamically adapt, grow and improve the hierarchy to better meet the needs of its changing environment and operating conditions. This paper describes work-in-progress on the definition of reflective channel hierarchies. 1
E. Corso - One of the best experts on this subject based on the ideXlab platform.
-
An effective XML based name mapping mechanism within StoRM
Journal of Physics: Conference Series, 2008Co-Authors: E. Corso, A Forti, A Ghiselli, L Magnoni, R ZappiAbstract:In a Grid environment the naming capability allows users to refer to specific data resources in a physical storage system using a high level logical identifier. This logical identifier is typically organized in a file system like structure, a hierarchical tree of names. Storage Resource Manager (SRM) services map the logical identifier to the physical location of data evaluating a set of parameters as the desired quality of services and the VOMS attributes specified in the requests. StoRM is a SRM service developed by INFN and ICTP-EGRID to manage file and space on standard POSIX and high performing parallel and cluster file systems. An upcoming requirement in the Grid data scenario is the orthogonality of the logical name and the physical location of data, in order to refer, with the same identifier, to different copies of data archived in various storage areas with different quality of service. The mapping mechanism proposed in StoRM is based on a XML document that represents the different storage components managed by the service, the storage areas defined by the site administrator, the quality of service they provide and the Virtual Organization that want to use the storage area. An appropriate directory tree is realized in each storage component reflecting the XML Schema. In this scenario StoRM is able to identify the physical location of a requested data evaluating the logical identifier and the specified attributes following the XML Schema, without querying any database service. This paper presents the Namespace Schema defined, the different entities represented and the technical details of the StoRM implementation.
Edward Curry - One of the best experts on this subject based on the ideXlab platform.
-
Reflective channel hierarchies
Springer-Verlag, 2003Co-Authors: Edward Curry, Desmond Chambers, Gerard LyonsAbstract:Hierarchical channel structures are used to create granular sub-channels from a parent channel. Utilized in routing situations that are more or less static, they require that the channel Namespace Schema be both well defined and universally understood. The publish/subscribe messaging model currently requires a message publisher to place messages into a specific channel within the hierarchy. A relocation of responsibility for channel selection logic from the publishing client to the middleware service would open up static channel hierarchies to the application of reflective techniques. This shift in responsibilities enables the service more control over the definition, creation and maintenance of the channel hierarchy. The service is now able to apply reflective and adaptive techniques to dynamically adapt, grow and improve the hierarchy to better meet the needs of its changing environment and operating conditions. This paper describes work-in-progress on the definition of reflective channel hierarchies. 1
A Forti - One of the best experts on this subject based on the ideXlab platform.
-
An effective XML based name mapping mechanism within StoRM
Journal of Physics: Conference Series, 2008Co-Authors: E. Corso, A Forti, A Ghiselli, L Magnoni, R ZappiAbstract:In a Grid environment the naming capability allows users to refer to specific data resources in a physical storage system using a high level logical identifier. This logical identifier is typically organized in a file system like structure, a hierarchical tree of names. Storage Resource Manager (SRM) services map the logical identifier to the physical location of data evaluating a set of parameters as the desired quality of services and the VOMS attributes specified in the requests. StoRM is a SRM service developed by INFN and ICTP-EGRID to manage file and space on standard POSIX and high performing parallel and cluster file systems. An upcoming requirement in the Grid data scenario is the orthogonality of the logical name and the physical location of data, in order to refer, with the same identifier, to different copies of data archived in various storage areas with different quality of service. The mapping mechanism proposed in StoRM is based on a XML document that represents the different storage components managed by the service, the storage areas defined by the site administrator, the quality of service they provide and the Virtual Organization that want to use the storage area. An appropriate directory tree is realized in each storage component reflecting the XML Schema. In this scenario StoRM is able to identify the physical location of a requested data evaluating the logical identifier and the specified attributes following the XML Schema, without querying any database service. This paper presents the Namespace Schema defined, the different entities represented and the technical details of the StoRM implementation.
