Collaboration Point Highlights in INDIGO DataCloud WP6
"Explore the key collaboration points, use cases, and requirements within INDIGO DataCloud WP6 for high-level libraries, APIs, gateways, and mobile apps. Special emphasis on standard-compliant interfaces and partnerships with other WPs."
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
INDIGO DataCloud WP6 Marcin P ciennik Roberto Barbera On behalf of WP6
Outline Partners: PSNC, INFN, CMCC, CNRS, KIT Well defined responsibilities and tasks for partners (details discussed) 6.1 Main collaboration point: high level libraries and API s We want to use standard-compliant interfaces: SAGA One of the major point to discuss: AAI inputs provided to other sessions 6.2 We need to identify the use cases for the Gateways and Mobile Apps in details (there are initial candidates) 6.3 We need to identify the w-f scenarios requirements We build on top of existing technologies and tools like Catania Science Gateway Framework, Ophidia, scientific workflows like Taverna, Galaxy etc. (online demonstrations/limitations of several solutions shown) Agreed on weekly meetings Need for collaboration tools/ task tracking systems, etc 2 2 INDIGO INDIGO- -DataCloud DataCloud 18/03/2025 18/03/2025
Relations with other WPs We need to organise meetings with WP2 and with real end users to understand the requirements of specific applications and try to map to the architecture WP6 is supposed to deliver its architecture at M6 (Sep 2015) and to keep this deadline we can not wait until WP2 releases its deliverable on requirements If F2F will not be possible, we foreseen to have series of the teleconferences per each use case We also need to have detailed technical meetings with WP4 and WP5 June could be a good time for a joint F2F meeting where to present the first drafts of the various architectures 3 3 INDIGO INDIGO- -DataCloud DataCloud 18/03/2025 18/03/2025
WP6-WP2 first interactions Due to the partners involved in WP6 and to the already existing connections to some of WP2 communities, first interactions could be done with Climate Change community Cultural Heritage community Elixir community 4 4 INDIGO INDIGO- -DataCloud DataCloud 18/03/2025 18/03/2025
Requirements to other WPs We want to use standard-compliant interfaces: SAGA We want to use standard-based discoverable data: OAI-PMH Sparql DOI s/PID s with data endpoints and access protocols included as metadata 5 5 INDIGO INDIGO- -DataCloud DataCloud 18/03/2025 18/03/2025
Requirements to other WPs To WP5: We would like to know WP5 API s Basing as much as possible on standard solutions as possible Open questions: How will we access data What kind of protocols do we need to target? We understand there are already established repositories/formats/protocols to access the data in the user communities (climate change example), how this will be addressed? 6 6 INDIGO INDIGO- -DataCloud DataCloud 18/03/2025 18/03/2025
Some highlights from the DoW Deliver way to use several tools addressing basic data storage, access and management scenarios: high performance and reliable data transfer (upload and download of data objects: files, directories, meta-data, VM/container images etc.) data synchronization (rsync-like and Dropbox-like scenarios) for directories and datasets data publication (i.e. making selected data sets visible and accessible to public Web with no or minimal authentication or authorization requirements) depositing data to archives and ensuring their persistence and means to refer to the data (e.g. by exploiting services such as EUDAT s B2SAFE and B2SHARE) etc. file-system like interfaces to enable applications to run legacy software within virtualized infrastructure for selected users, applications and environments including Windows, Linux, MacOS data encryption and integrity control-related functionality (e.g. crypto- filesystems, crypto-tools) This has to be supported on the lower layer so we could expose it to the users 7 7 INDIGO INDIGO- -DataCloud DataCloud 18/03/2025 18/03/2025
