Skip to content
Snippets Groups Projects
Commit cbc4b7ae authored by bovy89's avatar bovy89
Browse files

some corrections

parent af226fe9
No related branches found
No related tags found
1 merge request!4Feature/syinfo
......@@ -57,7 +57,7 @@ Thanks to the continuous integration system based on Gitlab, the configuration m
\begin{center}
\includegraphics[width=1.0\textwidth]{pres_rundeck.png}
\end{center}
\caption{\label{fig:deloy_rundeck} Presenze deploy using Rundeck}
\caption{\label{fig:deloy_rundeck} Deploy using Rundeck}
\end{figure}
......@@ -79,9 +79,11 @@ Furthermore, the log analysis infrastructure based on Elasticsearch-Logstash-Kib
\section{Disaster Recovery}
On November 9th CNAF T1 datacenter was flooded following a problem with a water pipeline, filling up to one/two rack unit.
Because of this disaster, it was necessary to physically move our infrastructure to the INAF (CNR Bologna) datacenter in order to restore our services while maintaining the same network.
Because of this disaster, it was necessary to physically move our infrastructure to the National Institute For Astrophysics (INAF) datacenter, located at the National Research Council (CNR), in order to restore our services while maintaining the same network.
Following this event, the GARR team provide us a disaster recovery (DR) site with dedicated hardware in ReCaS-Bari datacenter. On such hardware a virtualization infrastructure based on VMware was prepared on which to operate autonomously.
As result of this event, INFN general manager and executive council, request a new DR site to ensure availability of data and recovery times in the range of 2 days in case of further incident, not possible in LNF DR site.
To achieve this purpose, the Italian national computer network for universities and research (GARR) team provide us a disaster recovery (DR) site with dedicated hardware in ReCaS-Bari datacenter. On such hardware a virtualization infrastructure based on VMware was prepared on which to operate autonomously.
Our database systems (Oracle, MongoDB, etc) are replicated on disaster recovery sites using their own replication system (e.g. Oracle Dataguard). For database systems in which there was already a slave on the LNF site, an additional slave was added to the Bari site.
At the same time, database backups (e.g. made with Oracle RMAN) and a cold backup of INFN ERP system were also sent to the Bari Site.
......@@ -130,7 +132,7 @@ The most important task, which was started in 2017 till the first months of 2018
\section{Repertorio Contratti}
A brand new Java application, called "Repertorio Contratti" has been developed, and at the time of writing is in test phase. Its aim is to allow the administrative staff to register a contract made between INFN and an external agent in a safe and maintainable manner. A contract is in general represented by an electronic document with a list of associated metadata. Upon contract registration, the application is able to assign a unique id to each contract, year by year, and to efficiently and permanently store the relevant document in a dedicated Alfresco area, while saving the associated metadata in a database in a persistent manner. The contracts can than be easily managed, searched for, or, if necessary canceled and easily recreated, but the canceled document is not wiped out from the system in order to always keep track of the legal aspects of the operations. The application is interfaced with the INFN AAI system, but a set of ACLs controls the different privileges a user can have inside the application.
A brand new Java application, called "Repertorio Contratti" has been developed, and at the time of writing is in test phase. Its aim is to allow the administrative staff to register a contract made between INFN and an external agent in a safe and maintainable manner. A contract is in general represented by an electronic document with a list of associated metadata. Upon contract registration, the application is able to assign a unique id to each contract, year by year, and to efficiently and permanently store the relevant document in a dedicated Alfresco area, while saving the associated metadata in a database in a persistent manner. The contracts can than be easily managed, searched for, or, if necessary canceled and easily recreated, but the canceled document is not wiped out from the system in order to always keep track of the legal aspects of the operations.
The application is interfaced with the INFN AAI system for the authentication, even if a specific set of ACLs controls the different privileges a user can have inside the application, and with the INFN Protocol system through appropriate Application Programming Interfaces (APIs), to ensure that the contracts, with the related metadata, can be registered and stored in accordance with the law.
\end{document}
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