Studio di meccanismi di attacco e difesa nei collegamenti in ponte radio Hiperlan

In this thesis we analyze security mechanisms like WEP and 802.11i considering theirs implementation in Hiperlan 2. The goal of the thesis is to study attacks on this implementationopenEmbargo per motivi di segretezza e di proprietà dei risultati e informazioni sensibil

Studio di meccanismi di attacco e difesa nei collegamenti in ponte radio Hiperlan

In this thesis we analyze security mechanisms like WEP and 802.11i considering theirs implementation in Hiperlan 2. The goal of the thesis is to study attacks on this implementatio

CRIS-INAF: a fruitful cooperation among IT specialists, librarians, and researchers

<p>The <strong><em>C</em></strong><em>urrent <strong>R</strong>esearch <strong>I</strong>nformation <strong>S</strong>ystem</em> of the <strong><em>I</em></strong><em>stituto <strong>N</strong>azionale di <strong>A</strong>stro<strong>F</strong>isica</em>  (CRIS-INAF) is an institutional archive of the whole scientific and technological outcome of the staff. The system is the result of the co-operation among four main actors: Information Technologist (system development), Librarians/Documentalists (library science/scholarly communication and scientometry), Administration (central and local management of  staff and structures) and Researchers (mainly, data provision & validation).</p

Merging OpenStack-based private clouds: the case of CloudVeneto.it

The Cloud Area Padovana, deployed in 2014, is a scientific IaaS cloud, spread between two different sites: the INFN Padova Unit and the INFN Legnaro National Labs. It provides about 1100 logical cores and 50 TB of storage. The entire computing facility, owned by INFN, satisfies the computational and storage demands of more than 100 users belonging to about 30 research projects, mainly related to HEP and nuclear physics. The Padova data centre also has hosted and operated since 2015 an independent IaaS cloud managing network, storage and computing resources owned by 10 departments of the University of Padova, supporting a broader range of scientific and engineering disciplines. This infrastructure provides about 480 logical cores and 90 TB of storage and supports more than 40 research projects. These two clouds share only a limited set of ICT services and tools (mainly for configuration, monitoring and accounting), whereas their daily operations and maintenance are carried out separately by INFN and University personnel. At the end of 2017 we planned to merge the two infrastructures in order to optimise the use of resources (both human and ICT) and to avoid useless duplication of services. We discuss here how we plan to implement this integration, resulting in a single cloud infrastructure named CloudVeneto.it

Merging OpenStack-based private clouds: the case of CloudVeneto.it

The Cloud Area Padovana, deployed in 2014, is a scientific IaaS cloud, spread between two different sites: the INFN Padova Unit and the INFN Legnaro National Labs. It provides about 1100 logical cores and 50 TB of storage. The entire computing facility, owned by INFN, satisfies the computational and storage demands of more than 100 users belonging to about 30 research projects, mainly related to HEP and nuclear physics. The Padova data centre also has hosted and operated since 2015 an independent IaaS cloud managing network, storage and computing resources owned by 10 departments of the University of Padova, supporting a broader range of scientific and engineering disciplines. This infrastructure provides about 480 logical cores and 90 TB of storage and supports more than 40 research projects. These two clouds share only a limited set of ICT services and tools (mainly for configuration, monitoring and accounting), whereas their daily operations and maintenance are carried out separately by INFN and University personnel. At the end of 2017 we planned to merge the two infrastructures in order to optimise the use of resources (both human and ICT) and to avoid useless duplication of services. We discuss here how we plan to implement this integration, resulting in a single cloud infrastructure named CloudVeneto.it