Abstract
The article describes the distributed cloud infrastructure deployed on the basis of the resources of the Laboratory of Information Technologies of the Joint Institute for Nuclear Research (LIT JINR) and some JINR Member State organizations. It explains a motivation of that work, an approach it is based on, lists of its participants among which there are private entity “Nazarbayev University Library and IT services” (PE “NULITS”) Autonomous Education Organization “Nazarbayev University” (AO NU) and The Institute of Nuclear Physics’ (INP's) Astana branch.
Highlights
Service ImplementationTwo main components of the system can be marked out: front-end node (FN) which contains the system core and user interfaces to interact with the service; cluster nodes (CNs): the physical servers which host the users’ virtual machines (VMs) and containers (CTs)
The service uses two virtualization technologies to provide virtual instances (VIs): OpenVZ containers [3]; KVM virtual machines [4]
It explains a motivation of that work, an approach it is based on, lists of its participants among which there are private entity “Nazarbayev University Library and IT services” (PE “NULITS”) Autonomous Education Organization “Nazarbayev University” (AO NU) and The Institute of Nuclear Physics’ (INP’s) Astana branch
Summary
Two main components of the system can be marked out: front-end node (FN) which contains the system core and user interfaces to interact with the service; cluster nodes (CNs): the physical servers which host the users’ virtual machines (VMs) and containers (CTs). OpenNebula front-end (FN) consists of the following components: a core, a scheduler, a MySQL backend, a User (Web-GUI, CLI) and API (rOCCI) interfaces, OneGate and OneFlow services. The FN is deployed in OpenVZ container (CT) running on distributed replicated block device (DRBD) partition which is shared between two physical servers (marked on the Fig. 2 as HN1-FN, HN2-FN). They track each other’s status with help of Heartbeat service. To split external and internal traffic all CNs are connected to public and private networks whereas storage nodes (SNs) – to the private one only
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
