This paper describes the achievements and the evolution of INFN Corporate Cloud (INFN-CC), the geographically
distributed private Cloud infrastructure aimed at providing ICT services starting from the Infrastructure as a Service
(IaaS) cloud level based on OpenStack. In particular, the contribution provided by CANF in terms of operations and possible evolution
(IaaS) cloud level based on OpenStack. In particular, the contribution provided by CNAF in terms of operations and possible evolution
is here described and analysed.
...
...
@@ -22,7 +22,7 @@ is here described and analysed.
\section{Introduction}
The INFN Cloud Working Grouph as been active for almost three years within the so called "Commissione Calcolo e Reti" (CCR)
The INFN Cloud Working Group as been active for almost three years within the so called "Commissione Calcolo e Reti" (CCR)
in INFN. Its activity being that of testing and acquiring expertise on technologies related to Cloud Computing and of selecting
solutions that can be adopted in INFN sites in order to meet the computing needs of the INFN scientific community and more
generally to ease information sharing inside and outside INFN. In the recent past, a number of projects related to Cloud
...
...
@@ -63,7 +63,7 @@ layer, together with the underlying IaaS, is able to provide automatic scalabili
Techinically speaking, from the OpenStack \cite{openstack} point of view INFN-CC is a multi-region cloud composed of different OpenStack
installations sharing a set of services that are managed globally while maintaining other services local, as shown in Figure \ref{infncc-services}.
The avilable INFN-CC services can be summarized in the following categories:
The available INFN-CC services can be summarized in the following categories:
Ancillary services such as:
\begin{itemize}
...
...
@@ -72,12 +72,12 @@ Ancillary services such as:
\end{itemize}
Local services, implemented independently on each site, they have a local scope such as compute, volume and network.
In particular Compute and Volume services rely on a CEPH \cite{ceph} back-end. Each site has a CEPH instance with differnt priority and the
In particular Compute and Volume services rely on a CEPH \cite{ceph} back-end. Each site has a CEPH instance with different priority and the
CEPH rbd mirror is employed to replicate data across INFN-CC sites for disaster recovery.
Global services, Implemented on all sites for high availability, backed by common DBs when needed, they have a global scope and are here listed:
\begin{itemize}
\item Openstack Horizon, providing the GUI to access the INFN-resouces and services via Web,
\item Openstack Horizon, providing the GUI to access the INFN-resources and services via Web,
\item OpenStack Keystone access points, pointing to the above mentioned distributed DBMS, are available on all INFN-CC sites,
\item OpenStack Swift relies on the INFN-CC private network and is deployed geographically,
\item Openstack Glance relies on CEPH as a storage backend and on the Percona cluster as a catalog, this way it is fully distributed as well.
...
...
@@ -111,8 +111,7 @@ enable tos dynamically migrate cloud services, when needed, for high availabilit
\subsection{INFN-CC functionalities}
INFN-CC provides some interesting functionalities and features thanks to the its geographical distribution among differnt sites.
In particular we can highlight the following:
INFN-CC provides some interesting functionalities and features thanks to the its geographical distribution among different sites:
\begin{itemize}
\item Single point of access to distributed resources, fully exploiting the native functionalities of OpenStack and with no (or very small)
...
...
@@ -175,7 +174,7 @@ daemon that exposes the OpenStack Networking API and passes tenant requests to a
\item A storage node: bare metal resource hosting a cluster distribution of CEPH object storage that provides interfaces for object-, block- and file-level storage
\item A ToR switch
\end{itemize}
Up to date, CNAF is providing to the INFN-CC the following IaaS resources: 20 VCPUs, 50GB RAM, 50 FIPs and 50TB of volume storage.
Up to date, CNAF is providing to the INFN-CC the following IaaS resources: 20 VCPUs, 50GB RAM, 50 Floating IPs and 50TB of volume storage.
A set of new resources are expected to be acquired by 2019 and became part of the CNAF region od INFN-CC infrastructure.
In the next year, a contribution from CNAF in terms of development and integration of new services is also expected, in particular in the deployment and testing of
CEPH distributions.
...
...
@@ -184,10 +183,10 @@ CEPH distributions.
\section{Conclusions}
In this contribution, the INFN-CC cloud infrastructure has been briefly presented from different aspects. Archietecture, services, maintecance model
and possible usecse have been also discussed.
In particular, the contribution of CNAF in terms of operations and evolution of both the CNAF regione and the the INFN-CC cloud infrastructure at whole
have been describeded.
In the next years, the evolution of the services offered by INFN-CC is expected to bring new and changelling usecases.
In this respect, CNAF is aiming to contribute in terms of manpower and expertise to improve both the reilability and the quality of the service offered to INFN and worldwide.
In particular, the contribution of CNAF in terms of operations and evolution of both the CNAF regions and the the INFN-CC cloud infrastructure at whole
have been described.
In the next years, the evolution of the services offered by INFN-CC is expected to bring new and challenging usecases.
In this respect, CNAF is aiming to contribute in terms of manpower and expertise to improve both the reliability and the quality of the service offered to INFN and worldwide.
