Skip to content
Snippets Groups Projects
Commit fdb97597 authored by Doina Cristina Duma's avatar Doina Cristina Duma
Browse files

Update ds_eoscpilot.tex

parent df5ffcf9
No related branches found
No related tags found
1 merge request!6Eoscpilot
Pipeline #21869 failed
...@@ -11,16 +11,90 @@ ...@@ -11,16 +11,90 @@
\begin{abstract} \begin{abstract}
The EOSCpilot project is the first project in the entire EOSC programme, tasked with exploring some of the scientific, technical and cultural challenges that need to be addressed in the deployment of the EOSC. The EOSCpilot project has been funded to support the first phase in the development of the European Open Science Cloud (EOSC). In this paper we present a summary of the second year activities results in the field of interoperability containing the first results of the validation of services and demonstrators in the interoperability testbeds and the revised interoperability requirements derived from these activities. The EOSCpilot project is the first project in the entire EOSC programme, tasked
with exploring some of the scientific, technical and cultural challenges that need
to be addressed in the deployment of the EOSC. The EOSCpilot project has been funded
to support the first phase in the development of the European Open Science Cloud
(EOSC). In this paper we present a summary of the second year activities results
in the field of interoperability containing the first results of the validation
of services and demonstrators in the interoperability testbeds and the revised
interoperability requirements derived from these activities.
\end{abstract} \end{abstract}
\section{Introduction} \section{Introduction}
The European Open Science Cloud (EOSC) programme aims to deliver an Open Data Science Environment that federates existing scientific data infrastructures to offer European science and technology researchers and practitioners seamless access to services for storage, management, analysis and re-use of research data presently restricted by geographic borders and scientific disciplines. The European Open Science Cloud (EOSC) programme aims to deliver an Open Data
Science Environment that federates existing scientific data infrastructures to
offer European science and technology researchers and practitioners seamless
access to services for storage, management, analysis and re-use of research data
presently restricted by geographic borders and scientific disciplines.
In the framework of the EOSCpilot, WP6, "Interoperability", aims to develop and
demonstrate the interoperability requirements between e-Infrastructures,
domain research infrastructures and other service providers needed in the
European Open Science Cloud. It provides solutions, based on analysis of existing
and planned assets and techniques, to the challenge of interoperability.
Two aspects of interoperability are taken into consideration: {\bf Data interoperability},
ensuring that data can be discovered accessed and used according to the FAIR
principles, and {\bf Service interoperability}, ensuring that services operated
within different infrastructures can interchange and interwork.
In the framework of the EOSCpilot project INFN, and in particular CNAF is the
coordinator of the activities of the task T6.3 - “Interoperability pilots
(service implementation, integration, validation, provisioning for Science
Demonstrators)”.
One of the main project Objectives is to:
\begin{itemize}
\item “Develop a number of pilots that integrate services and infrastructures
to demonstrate interoperability in a number of scientific domains”
\end{itemize}
while specific Objectives addressed by the 6.3 task during 2018 were:
\begin{itemize}
\item Validating the compliance of services provided by WP5, "Services",
with specifications and requirements defined by the Science Demonstrators in WP4,
"Science Demonstrators"
\item Defining and setting up distributed Interoperability Pilots, involving
multiple infrastructures, providers and scientific communities, with the purpose
of validating the WP5 service portfolio.
\end{itemize}
\section{First section} \section{Activities and Achievements}
\label{sec:release} \label{sec:activities}
During 2018 the main activities coordinated by INFN-CNAF were:
\begin{itemize}
\item Support the setup of the Science Demonstrator pilots, following their
interoperability requirements and matching them again with available services and solutions
\item Setup of different pilot addressing different interoperability aspects:
\begin{itemize}
\item Transparent Networking – PiCo2 (Pilot for COnnection between COmputing centers)
\item Grid and Cloud interoperability – pilot demonstrator for one of the HEP experiments
\item AAI – through the setup of a scoped interoperability pilot as part of the
WLCG Authorization WG, AARC and EOSCpilot collaboration
\item Resource Brokering & orchestration – leveraging INDIGO-DataCloud solutions
\item Data accessibility & interoperability of underlying storage systems –
distributed Onedata deployment
\end{itemize}
\end{itemize}
\subsection{Interoperability pilots: Transparent Networking}
The {\bf PiCO2 (Pilot for COnnecting COmputing centers)} is one of the first
interoperability pilots between generic, community agnostic, infrastructures,
especially Tier-1 (National HPC/HTC centres), and Tier-2 (HPC/HTC regional centres).
Its main objective is the automation of frequent, community agnostic, data flow
(many large files) and code exchange between HPC (National, Regional) and HTC (national, grid) infrastructures
technical groups have been set up:
\begin{itemize}
\item one for building a network of peer to peer federations between iRODS zones
(data storage service), between Tier1 & Tier 2, between Tier2, and between Tier 2 and the grid
\item one for connecting the infrastructures within a L3VPN network and
monitoring the performance of the network between sites
\item one for facilitating the mobility and use of codes between different
machines, using containers, packages for configuration management, and notebooks
\end{itemize}
TOCHANGE TOCHANGE
The software development lifecycle (SDL) process (Figure~\ref{fig:1}) in INDIGO has been supported by a continuous The software development lifecycle (SDL) process (Figure~\ref{fig:1}) in INDIGO has been supported by a continuous
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment