e-Infrastructure Integration-with gCube

807 views

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
807
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Scenarios: TS curation 2? 3) the Aquamaps maps expert validation
  • VRE resources can be published in the VO at any time by the VRE data managers.
  • Interoperability is among the most critical issues to be faced when building systems as "collections" of independently developed constituents (systems on its own) that should co-operate and rely on each other to accomplish larger tasks. Unfortunately, interoperability is a kind of problem that has multiple facets and it is very challenging. Interoperability issues arising whenever two (or more systems) are willing to ''share'' a certain resource (whatever it is) and one of the two systems plays the role of ''provider'' of the resource while the other plays the role of a ''consumer'' of this resource. The multiple facets result from the fact there are multiple barriers hindering the involved systems to ''share'' a common understanding of the resource that is the target of the interoperability scenario. These barriers range from different models of the resource to different protocols and API to access the resource and interact with it, different policies (and policy models) governing the resource consumption, etc.
  • Different Interoperability approaches
  • Resources accessble from a common ecosystem of resources and different communities can access different Ecosystem views. Communities define their VREs ( trasparentrly from the providers, which could be also Cloud systems) Competition of the same resources btw VREs ( eg. Indexes or Storage)
  • Blacboard bases ( Information System) Wrapper /medoator based ( CM) Adaptor-based ( PES adaptor over condor, grid and hadoop) map reduce)
  • OCMA is an open, WSRF-compliant architecture for gCube content management services. OCMA defines a design pattern for such services and, by contextualisation of the pattern, their role in a gCube infrastructure. Requirements and Assumptions OCMA acknowledges that gCube is concerned with content that may: be hosted inside or outside a gCube infrastructure; be described with a variety of models, for different media, and with different degrees of structure; be accessed with a variety of protocols; OCMA makes only the following assumptions about content: content is created, accessed, and distributed in units called documents ; documents are grouped in collections ; collections are hosted in local management systems called repositories . Finally, OCMA acknowledges that content management in gCube needs to: embrace heterogeneity , i.e. support simultaneously multiple locations, protocols, and models; hide heterogeneity , i.e. abstract over differences in location, protocol, and model; scale , i.e. retain good throughput under heavy load;
  • OCMA is the Architecture, flagship CM sevice A storage back-end R may already offer a native T-interface. In this case OCMA relies on wrapper for R . A storage back-end R may offer a different T'-interface. In this case OCMA relies on adapter for R .
  • Composition of: Data access to External infrastructures ( Aquamaps) Data process on Hadoop Data process on glite
  • In statistics , signal processing , econometrics and mathematical finance , a time series is a sequence of data points , measured typically at successive times spaced at uniform time intervals. Time series analysis comprises methods for analyzing time series data in order to extract meaningful statistics and other characteristics of the data.
  • R is a language and environment for statistical computing and graphics. It is a GNU project which is similar to the S language and environment which was developed at Bell Laboratories (formerly AT&T, now Lucent Technologies) by John Chambers and colleagues. R can be considered as a different implementation of S. There are some important differences, but much code written for S runs unaltered under R. R provides a wide variety of statistical (linear and nonlinear modelling, classical statistical tests, time-series analysis, classification, clustering, ...) and graphical techniques, and is highly extensible. The S language is often the vehicle of choice for research in statistical methodology, and R provides an Open Source route to participation in that activity.
  • e-Infrastructure Integration-with gCube

    1. 1. e-Infrastructure Integration with gCube Andrea Manzi ( CERN ) Pasquale Pagano ( ISTI-CNR ) EGI User Forum 13 April 2011 Vilnius ( Lithuania ) www.d4science.eu
    2. 2. Outline <ul><li>D4Science II Ecosystem </li></ul><ul><li>gCube architecture </li></ul><ul><li>Interoperability approaches </li></ul><ul><ul><ul><li>Resource Discovery </li></ul></ul></ul><ul><ul><ul><li>Data Storage & Access </li></ul></ul></ul><ul><ul><ul><li>Data Discovery </li></ul></ul></ul><ul><ul><ul><li>Data Process </li></ul></ul></ul><ul><ul><ul><li>Security </li></ul></ul></ul><ul><li>Applications </li></ul><ul><ul><ul><li>AquaMaps </li></ul></ul></ul><ul><ul><ul><li>Time Series </li></ul></ul></ul>
    3. 3. D4Science II Ecosystem <ul><ul><li>Heterogeneous resources </li></ul></ul><ul><ul><li>Heterogeneous computational platforms </li></ul></ul><ul><ul><li>Rich set of legacy applications </li></ul></ul><ul><ul><li>Multiple administrative domains </li></ul></ul><ul><ul><li>Evolving communities </li></ul></ul>D4SCIENCE INFRASTRUCTURE Hadoop EGEE/EGI INSPIRE DRIVER GENESI-DR AquaMaps FAO Geonetwork FAO FIGIS Community A Community B
    4. 4. gCube architecture gCube run-time environment gCube Definition and Management Services gCube Application Services Presentation Services Portlets Application Support Layer Information Organization Services Storage Management Collection - Content - Metadata - Annotation -… Management Information Access Services Search Framework Ontology Management Personalization Service Index Management Framework DIR Support Framework Process Execution Management VRE Management Information System Security gCube Container gCore Framework User Services
    5. 5. Virtual Organization <ul><li>A Virtual Organization (VO) specifies how a set of users can access a set of resources </li></ul><ul><ul><li>what is shared </li></ul></ul><ul><ul><li>who is allowed to share </li></ul></ul><ul><ul><li>the conditions under which sharing can occur </li></ul></ul><ul><li>The concept of VO Is not adequate to cover some common scenarios </li></ul><ul><ul><li>Data needs to be assessed before to make it publically exploitable by the VO members. </li></ul></ul><ul><ul><li>Restricted set of users have to collaborate to refine processes and implement show cases. </li></ul></ul><ul><ul><li>Products generated through elaboration of data or simulation have to be validated by expert users. </li></ul></ul>
    6. 6. Virtual Research Environment <ul><li>Virtual Research Environment (VRE) is </li></ul><ul><ul><li>a distributed and dynamically created environment </li></ul></ul><ul><ul><li>where subset of resources can be assigned to a subset of users via interfaces </li></ul></ul><ul><ul><li>for a limited timeframe </li></ul></ul><ul><ul><li>at little or no cost for the providers of the infrastructure </li></ul></ul><ul><ul><li>Integrated with cloud systems ( OpenNebula ) </li></ul></ul>VRE 1 VO gCube is a first example of a VRE management system VRE 2
    7. 7. Interoperability: Assumptions <ul><ul><li>Very rich applications and data collections are currently maintained by a multitude of authoritative providers </li></ul></ul><ul><ul><li>Different problems require different execution paradigms: batch, map-reduce, synchronous call, message-queue, … </li></ul></ul><ul><ul><li>Key distributed computation technologies exist: grid (gLite and Globus), distributed resource management (Condor), clusters (Hadoop), … </li></ul></ul><ul><ul><li>Several standards are adopted in the same domain </li></ul></ul>
    8. 8. Interoperability: Landscape <ul><li>Unstructured Data: blob (binary), and textual files </li></ul><ul><li>Structured Data: tabular, statistical, geospatial, temporal, and textual data </li></ul><ul><li>Compound Data: data composed by unstructured and structured data entities </li></ul>security
    9. 9. Interoperability: gCube Vision <ul><li>gCube objectives: </li></ul><ul><ul><li>hide heterogeneity , i.e. abstract over differences in location, protocol, and model; </li></ul></ul><ul><ul><li>embrace heterogeneity , i.e. allow for multiple locations, protocols, and models; </li></ul></ul><ul><li>Technical goals: </li></ul><ul><ul><li>no bottlenecks : scale no less than the interfaced resources </li></ul></ul><ul><ul><li>no outages : keep failures partial and temporary </li></ul></ul><ul><ul><li>autonomicity : system reacts and recovers </li></ul></ul>
    10. 10. Hiding Heterogeneity <ul><ul><li>Heterogeneous resources are virtually accessible in a common ecosystem of resources </li></ul></ul><ul><ul><ul><li>despite their locations, technologies, and protocol </li></ul></ul></ul><ul><ul><li>Different communities have access to different views </li></ul></ul><ul><ul><ul><li>according to the conditions under which the sharing can occur </li></ul></ul></ul><ul><ul><li>Each community can define its own VRE </li></ul></ul><ul><ul><ul><li>for a limited timeframe and at no cost for the providers of the resource </li></ul></ul></ul><ul><ul><li>Several VRE can coexist </li></ul></ul><ul><ul><ul><li>without interfering each other even by competing for the same resources </li></ul></ul></ul>
    11. 11. Embracing Heterogeneity <ul><li>Approaches and solutions to achieve interoperability : </li></ul><ul><li>Blackboard-based </li></ul><ul><ul><li>asynchronous communication between components in a system </li></ul></ul><ul><ul><li>one protocol to R/W and one language to specify messages </li></ul></ul><ul><li>Wrapper/ Mediator-based </li></ul><ul><ul><li>translates one interface for a component into a compatible interface </li></ul></ul><ul><li>Adaptor-based </li></ul><ul><ul><li>provides a unified interface to a set of other components interfaces and encapsulates how this set of objects interact </li></ul></ul>
    12. 12. <ul><li>Each resource is represented by a profile (metadata) characterising: </li></ul><ul><ul><li>the interface </li></ul></ul><ul><ul><li>the state </li></ul></ul><ul><ul><li>the list of dependencies </li></ul></ul><ul><ul><li>the run-time status </li></ul></ul><ul><ul><li>the policies </li></ul></ul><ul><ul><li>the configuration </li></ul></ul><ul><ul><li>the pending tasks to execute </li></ul></ul><ul><li>A Resource profile </li></ul><ul><ul><li>is published by the resource owner </li></ul></ul><ul><ul><li>is discovered by the resource consumers asynchronously through a common resource-independent protocol </li></ul></ul><ul><li>gCube offers a distributed and scalable Information System ( blackboard ) to store, discover, and access resource profiles </li></ul>Interoperability Approaches: Resource Discovery gCube interoperability framework: the solution
    13. 13. Interoperability Approaches: Content Interoperability[1/2] <ul><ul><li>gCube Open Content Management Architecture (OCMA) </li></ul></ul><ul><ul><li>Assumption </li></ul></ul><ul><ul><ul><li>data stored in different storage back-ends </li></ul></ul></ul><ul><ul><ul><li>diverse locations, models, access types </li></ul></ul></ul><ul><ul><ul><li>few common primitives: documents, collections, repositories </li></ul></ul></ul><ul><ul><li>gCube allows to </li></ul></ul><ul><ul><ul><li>reach content that lies outside system </li></ul></ul></ul><ul><ul><ul><li>expose content (reachable from) inside system </li></ul></ul></ul><ul><ul><ul><li>perform coarse-grained as well as fine-grained retrieval, update, and addressing </li></ul></ul></ul><ul><ul><li>Runtime scalability </li></ul></ul><ul><ul><ul><li>autonomic read-only state replication, </li></ul></ul></ul><ul><ul><ul><li>maximize throughput, minimize response time: discovery-time load balancing (through IS) </li></ul></ul></ul><ul><ul><ul><li>reduce latencies </li></ul></ul></ul><ul><ul><li>Software </li></ul></ul><ul><ul><ul><li>plugin-based architecture to reduce development costs (plugins over Storage systems) </li></ul></ul></ul>
    14. 14. Interoperability Approaches: Content Interoperability[2/2] T 1 T 2 adapts adapts factory gDoc … gDoc Read gDoc Write <ul><li>Content Manager Service ( OCMA Service) </li></ul><ul><li>Adapts gCube doc model ( gDoc ) to an unbounded number of back-end types </li></ul>
    15. 15. Interoperability Approaches : Data Discovery <ul><li>gCube offers </li></ul><ul><ul><li>Several index types </li></ul></ul><ul><ul><ul><li>Forward indexing, which supports ultra fast lookups on tabular typed metadata; </li></ul></ul></ul><ul><ul><ul><li>XML indexing, that supports semistructured lookups on content metadata; </li></ul></ul></ul><ul><ul><ul><li>Textual field indexing, that supports full text and qualified lookups on textual (mainly) metadata; </li></ul></ul></ul><ul><ul><ul><li>Metadata full text indexing, that enables full text lookups on metadata; </li></ul></ul></ul><ul><ul><ul><li>Content full text indexing, that enables full text lookups on text extracted by content; </li></ul></ul></ul><ul><ul><ul><li>Geospatial/temporal indexing, that enables geospatial proximity and coverage queries to be executed over geospatial/temporal metadata; </li></ul></ul></ul><ul><ul><ul><li>Feature indexing, that enables high-dimension vector indexing, for feature lookup (currently the feature is inactive); </li></ul></ul></ul>
    16. 16. <ul><li>gCube offers solutions to: </li></ul><ul><ul><li>Decouple the business domain and infrastructure specific logic from the core “execution” functionality </li></ul></ul><ul><ul><ul><li>Invocate a wide range of logic components: SOAP and REST WebServices, Shell Scripts, Executable Binaries, POJOs, … </li></ul></ul></ul><ul><ul><ul><li>Support most of the execution paradigms: batch, map-reduce, synchronous call </li></ul></ul></ul><ul><ul><ul><li>Bridges key distributed computation technologies: grid (gLite and Globus), Condor, Hadoop </li></ul></ul></ul><ul><ul><li>Control and monitor the execution of a processing flow </li></ul></ul><ul><ul><li>Staging of data among different storage providers </li></ul></ul><ul><ul><li>Streaming data among computation elements </li></ul></ul>Interoperability Approaches : Process Execution [1/2]
    17. 17. Interoperability Approaches : Process Execution [2/2] <ul><li>By using adaptors that </li></ul><ul><ul><li>operate on a specific third party language and translate them into native constructs, </li></ul></ul><ul><ul><li>allow for the creation of complex workflows that exploit several diverse technologies deployed on different infrastructures </li></ul></ul>
    18. 18. Interoperability Approaches : Security [1/2] <ul><li>gCube offers solutions : </li></ul><ul><ul><li>To secure access to gCube resources for interoperable external systems (incoming security) </li></ul></ul><ul><ul><li>To ensure Interoperability of gCube security mechanisms with standards compliant security systems (reuse) </li></ul></ul><ul><ul><li>To facilitate secure access to external resources for gCube services (outgoing) </li></ul></ul>
    19. 19. <ul><li>Authz: </li></ul><ul><li>XACML for authz request/response protocol and policy definition </li></ul><ul><li>SAML assertions to transport user/service authN information </li></ul><ul><li>Argus-based approach (EMI Authz framework) having pluggable design to integrate additional PIPs </li></ul><ul><li>SAML Profile for XACML 2.0 following the OASIS Authorization Interoperability Profile Specification </li></ul><ul><li>AuthN: </li></ul><ul><li>Production level SSL/HTTPS support </li></ul><ul><li>Key- and Trust-Manager </li></ul>Interoperability Approaches : Security [2/2]
    20. 20. <ul><li>AquaMaps is an application* </li></ul><ul><ul><li>tailored to predict global distributions of marine species initially designed for marine mammals and subsequently generalised to marine species, </li></ul></ul><ul><ul><li>that generates color-coded species range maps using a half-degree latitude and longitude blocks </li></ul></ul><ul><ul><li>by interfacing several databases and repository providers </li></ul></ul>Species Distribution Maps Generation * A lgorithm by Kashner et al. 2006
    21. 21. <ul><li>AquaMaps execution is based on the gCube Ecological Niche Modelling Suite which allows the extrapolation of known species occurrences </li></ul>Species Distribution Maps Generation <ul><ul><li>to determine environmental envelopes (species tolerances) </li></ul></ul><ul><ul><li>to predict future distributions by matching species tolerances against local environmental conditions (e.g. climate change and sea pollution) </li></ul></ul>Very large volume of input and output data : HSPEC native range 56,468,301 - HSPEC suitable range 114,989,360 Very large number of computation : One multispecies map computed on 6,188 half degree cells (over 170k) and 2,540 species requires 125 millions computations (Eli E. Agbayani, FishBase Project/INCOFISH WP1, WorlFish Center)
    22. 22. Time Series Management <ul><li>Offers a set of tools to manage capture statistics </li></ul><ul><ul><li>Supports the complete TS lifecycle </li></ul></ul><ul><ul><li>Supports validation, curation, and analysis </li></ul></ul><ul><ul><li>Provides support for data reallocation </li></ul></ul><ul><ul><li>Produces uniform data-set </li></ul></ul>
    23. 23. Time Series and R statistical software integration <ul><li>The main aims are to: </li></ul><ul><li>provide a complete, fully working, environment for R language </li></ul><ul><li>give user methods to automatically extract data from the time series he was working on </li></ul><ul><li>give user the possibility to perform queries on the time series database </li></ul><ul><li>provide a service distributed on the infrastructure. Multiple instances can be managed on the infrastructure VREs, the distribution being transparent to the users (SaaS model) </li></ul>
    24. 24. Conclusions <ul><li>gCube System: </li></ul><ul><ul><li>Stable software being improved over the last 5 years ( end of DILIGENT -> D4Science -> D4ScienceII) </li></ul></ul><ul><li>gCube offers a variety of patterns, tools, and solutions </li></ul><ul><ul><li>to delivery interoperability solutions and interconnect </li></ul></ul><ul><ul><ul><li>Heterogeneous digital content </li></ul></ul></ul><ul><ul><ul><li>Heterogeneous repository systems </li></ul></ul></ul><ul><ul><ul><li>Heterogeneous computation platforms </li></ul></ul></ul><ul><ul><li>to decrease the cost of adoption </li></ul></ul><ul><ul><li>to deal with several standards </li></ul></ul>
    25. 25. Questions Time

    ×