<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">INTEGRATION OF THE PARALLEL RESOURCES TO THE DISTRIBUTED CLOUD INFRASTRUCTURES FOR LARGE SCALE PROJECTS</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Sergey</forename><forename type="middle">D</forename><surname>Belov</surname></persName>
							<email>abelov@jinr.ru</email>
							<affiliation key="aff0">
								<orgName type="institution">Joint Institute for Nuclear Research</orgName>
								<address>
									<addrLine>6 Joliot-Curie St</addrLine>
									<postCode>141980</postCode>
									<settlement>Dubna, Moscow</settlement>
									<region>Region</region>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Plekhanov Russian University of Economics</orgName>
								<address>
									<addrLine>Stremyanny lane, 36</addrLine>
									<postCode>117997</postCode>
									<settlement>Moscow</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Ivan</forename><forename type="middle">S</forename><surname>Kadochnikov</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Joint Institute for Nuclear Research</orgName>
								<address>
									<addrLine>6 Joliot-Curie St</addrLine>
									<postCode>141980</postCode>
									<settlement>Dubna, Moscow</settlement>
									<region>Region</region>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Plekhanov Russian University of Economics</orgName>
								<address>
									<addrLine>Stremyanny lane, 36</addrLine>
									<postCode>117997</postCode>
									<settlement>Moscow</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Vladimir</forename><forename type="middle">V</forename><surname>Korenkov</surname></persName>
							<email>ckorenkov@jinr.ru</email>
							<affiliation key="aff0">
								<orgName type="institution">Joint Institute for Nuclear Research</orgName>
								<address>
									<addrLine>6 Joliot-Curie St</addrLine>
									<postCode>141980</postCode>
									<settlement>Dubna, Moscow</settlement>
									<region>Region</region>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Plekhanov Russian University of Economics</orgName>
								<address>
									<addrLine>Stremyanny lane, 36</addrLine>
									<postCode>117997</postCode>
									<settlement>Moscow</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Nikolay</forename><forename type="middle">A</forename><surname>Kutovskiy</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Joint Institute for Nuclear Research</orgName>
								<address>
									<addrLine>6 Joliot-Curie St</addrLine>
									<postCode>141980</postCode>
									<settlement>Dubna, Moscow</settlement>
									<region>Region</region>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Igor</forename><forename type="middle">S</forename><surname>Pelevanyuk</surname></persName>
							<email>pelevanyuk@jinr.ru</email>
							<affiliation key="aff0">
								<orgName type="institution">Joint Institute for Nuclear Research</orgName>
								<address>
									<addrLine>6 Joliot-Curie St</addrLine>
									<postCode>141980</postCode>
									<settlement>Dubna, Moscow</settlement>
									<region>Region</region>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Plekhanov Russian University of Economics</orgName>
								<address>
									<addrLine>Stremyanny lane, 36</addrLine>
									<postCode>117997</postCode>
									<settlement>Moscow</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Roman</forename><forename type="middle">N</forename><surname>Semenov</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Joint Institute for Nuclear Research</orgName>
								<address>
									<addrLine>6 Joliot-Curie St</addrLine>
									<postCode>141980</postCode>
									<settlement>Dubna, Moscow</settlement>
									<region>Region</region>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Plekhanov Russian University of Economics</orgName>
								<address>
									<addrLine>Stremyanny lane, 36</addrLine>
									<postCode>117997</postCode>
									<settlement>Moscow</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Petr</forename><forename type="middle">V</forename><surname>Zrelov</surname></persName>
							<email>gzrelov@jinr.ru</email>
							<affiliation key="aff0">
								<orgName type="institution">Joint Institute for Nuclear Research</orgName>
								<address>
									<addrLine>6 Joliot-Curie St</addrLine>
									<postCode>141980</postCode>
									<settlement>Dubna, Moscow</settlement>
									<region>Region</region>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Plekhanov Russian University of Economics</orgName>
								<address>
									<addrLine>Stremyanny lane, 36</addrLine>
									<postCode>117997</postCode>
									<settlement>Moscow</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">INTEGRATION OF THE PARALLEL RESOURCES TO THE DISTRIBUTED CLOUD INFRASTRUCTURES FOR LARGE SCALE PROJECTS</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">13B411E6EE11020C0C53BCA1D83FE310</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T11:00+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>cloud computing</term>
					<term>parallel computing</term>
					<term>DIRAC interware</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Cloud services and data centers use a distributed network architecture for data storage, queries, and search engines. Virtualization is used to improve reliability, reduce services cost, and increase flexibility in deploying services. It is also applied to provide for the ability to migrate from one physical server to another. This paper provides an overview of the Joint Institute's for Nuclear Research (JINR) international distributed cloud infrastructure and the Plekhanov Russian University of Economics (PRUE) cloud infrastructure as a part of the distributed cloud. The paper underlines the unique role of the DIRAC grid interware, which combines the cloud resources as from some JINR Member State organizations as PRUE cloud. A special section is devoted to the integration of the parallel resources of PRUE to the cloud.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>The experiments at the Large Hadron Collider (LHC) at CERN (Geneva, Switzerland) played a leading role in scientific research not only in High Energy Physics and Nuclear Physics but also in Big Data Analytics. Global distributed system for processing, storage, and analyzing data WLCG (Worldwide LHC Computing GRID) brings together the resources of about 180 computer centers in 50 countries; the total storage capacity is more than 1 Exabytes. Data processing and analysis are carried out using highperformance complexes (Grid), academic, national, and commercial cloud computing resources, supercomputers, and other resources. JINR is actively involved in integrating distributed heterogeneous resources and the development of Big Data technologies to provide modern megaprojects in such highintensity fields of science as high energy physics, astrophysics, bioinformatics, and others.</p><p>The Joint Institute for Nuclear Research (JINR) <ref type="bibr">[1]</ref> is an international intergovernmental organization. It is developing as a large multidisciplinary international scientific center incorporating basic research in modern nuclear physics, development and application of high technologies, and university education in the relevant fields of knowledge. Currently, JINR has 18 Member States and 6 countries participating in JINR activities based on bilateral agreements signed on the governmental level.</p><p>The research program of the JINR is aimed at conducting ambiguous and large-scale experiments on the Institute's basic facilities and in frames of worldwide cooperation. This program is connected with the implementation of the NICA (Nuclotron-based Ion Collider fAcility) megaproject <ref type="bibr" target="#b0">[2]</ref>, the construction of new experimental facilities, the JINR neutrino program, the modernization of the Large Hadron Collider (LHC) <ref type="bibr" target="#b1">[3]</ref> experimental facilities (CMS, ATLAS, Alice), programs on condensed matter physics and nuclear physics. The recent years' experience shows that the progress in obtaining research results depends directly on computing resources' performance and efficiency. JINR possesses an information-computational complex that has evolved into a set of stand-alone structures with a shared engineering and networking infrastructures. Support of this fully functional infrastructure is the central task of the Laboratory of Information Technologies.</p><p>The JINR computing infrastructure combines a broad spectrum of computing components and IT technologies, providing the opportunity to solve various scientific and engineering tasks facing the Institute, from theoretical studies to experimental data processing, storage, and analysis.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">JINR Cloud infrastructure</head><p>A cloud infrastructure at the Joint Institute for Nuclear Research (JINR) was created in 2013. The aim was to manage LIT IT services and servers more efficiently using modern technologies, to combine resources for solving common tasks, increase the efficiency of hardware utilization and service reliability, simplify access to application software and optimize the use of proprietary software as well as provide a modern computing facility for JINR users.</p><p>The JINR cloud infrastructure <ref type="bibr" target="#b2">[4]</ref> operates on the base of the OpenNebula (release 5.8), enabling relatively easy integration of supporting container virtualization based on OpenVZ, as well as its extensions and additions. It is compatible with the Linux operating system (OS). It has the possibility of running virtual machines with this OS, the required functionality and quality of the software product, the license that permits modification and free use, the availability of clear and accessible documentation, and support from developers when modifying the software. Besides, OpenNebula appears to be an optimal choice in terms of the interrelationship of the hardware functioning in the infrastructure on its basis and the effort required to develop and maintain the cloud.</p><p>The JINR cloud resources were increased up to 1,564 CPU cores and 8.54TB of RAM in total. Current hardware resources: 66 servers for VMs, 10 servers for ceph-based software-defined storage (SDS), 3 servers for front-end nodes in high availability setup. The JINR cloud grows not only in the capacity of resources but also in the number of activities. It is used for different system and application tasks, namely, COMPASS production system services <ref type="bibr" target="#b3">[5]</ref>, a data management system of the UNECE ICP Vegetation, a service for scientific and engineering computations, a service for data visualization based on Grafana, JupyterHub infrastructure for it, gitlab and its runners as well as some others. Along with it, there was a successful attempt to deploy a virtual machine in the JINR cloud with a GPU card transmitted from the server for developing and running machines and deep learning algorithms for the JUNO experiment.</p><p>The approach to cloud integration is based on the OpenNebula cloud platform's built-in mechanism and works well for a small number of joined clouds. However, it sufficiently increases the complexity of such infrastructure maintenance with a growing number of participating clouds.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 1. International distributed cloud infrastructure participants on the map</head><p>Another approach uses the possibility to combine clouds by integrating them using a distributed workload management system -DIRAC grid Interware <ref type="bibr" target="#b4">[6]</ref>. Different distributed heterogeneous computing and storage resources from clouds of the JINR Member State organizations combine with the help of this approach (Fig. <ref type="figure">1</ref>).</p><p>Fig. <ref type="figure" target="#fig_0">2</ref> shows the contribution of each cloud site to general number of the load test jobs executed by clouds, integrated into a common international JINR cloud infrastructure. Meanwhile, the total number of computational jobs on different clouds does not represent their performance but rather the availability of free resources for the tasks of the distributed cloud infrastructure.</p><p>At the moment, based on the experience of many completed tasks (within the framework of the Folding@Home project as well), the most reliable and effective are the JINR and PRUE clouds. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">PRUE Cloud infrastructure</head><p>Cloud infrastructure of the Scientific laboratory of cloud computing and Big Data analytics <ref type="bibr" target="#b5">[7]</ref> of Plekhanov Russian Economic University (after thisthe cloud, cloud service) operates based on software OpenNebula 5. As a storage system, it is used software-defined storage (SDS) based on Ceph version 12. All servers are running under Linux Centos 7 operating system.</p><p>Currently, the cloud service is deployed on eight servers. A single server takes the lead role and hosts the following main components:</p><p>• cloud infrastructure core (OpenNebula core),</p><p>• OpenNebula scheduler,</p><p>• MySQL database server,</p><p>• interfaces for accessing the cloud (user-defined web interface and command-line interface and the application programming interface).</p><p>Four servers operate as cloud worker nodes (CWNs) that directly host virtual machines (VMs). Three servers act as storage nodes and, at the same time, as cloud-based worker nodes.</p><p>The network part of the cloud consists of two subnets (Fig. <ref type="figure" target="#fig_1">3</ref>). One subnet is intended for virtual machines and has a connection to the network switch at 1 Gbit. Another subnet is dedicated to SDS traffic and is connected to the network switch at a speed of 10 Gbit. Internet access is provided with the network equipment of the Plekhanov Russian University of Economics. • computing resources, including as an extension of computing capabilities of grid infrastructures. In addition to processing requests from PRUE users, the cloud service is integrated with other clouds that are part of the computing resources of the JINR member organizations' clouds.</p><p>The integration of cloud infrastructures is carried out using the DIRAC grid platform (distributed infrastructure with remote Agency management). The reasons to chose this interware platform: provides all necessary functionality, including operation and data management; cloud as a computing base support; simplify the deployment and maintenance of services compared to other platforms with similar functionality (for example, EMI).</p><p>This approach also allows you to share the resources of each cloud between external network users and local non-network users.</p><p>Currently, the integration of JINR member states' clouds into a distributed DIRAC based platform is at various stages (the stages and locations of participants in the distributed cloud infrastructure are shown on the map in Fig. <ref type="figure">1</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Integration of parallel resources to the distributed cloud</head><p>The DIRAC Interware is a software framework for distributed computing, providing a complete solution to one or several user communities requiring access to distributed resources. The DIRAC software offers a common interface to a number of heterogeneous computing and storage resources. From the user's perspective, DIRAC is a system that accepts their computing jobs and uploads results to storage.</p><p>DIRAC uses a pilot mechanism to run jobs on heterogeneous resources. The general idea of the pilot is the following: jobs do not run on computing resources directly but through a special program called «Pilot».</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 4. Scheme of integration of geographically distributed heterogeneous resources based on the DIRAC Interware</head><p>The JINR DIRAC Installation has been installed and gradually improved since 2017. At present, the following computing resources of JINR are integrated into the JINR DIRAC Installation (Fig. <ref type="figure">4</ref>) <ref type="bibr" target="#b6">[8]</ref>: Tier1/Tier2, «Govorun» supercomputer, JINR cloud, NICA cluster, and dCache and EOS storage resources, JINR Member States clouds. A cluster of the National Autonomous University of Mexico (UNAM) has recently joined the system, the DIRAC-based unified environment, which includes both computing resources and data storage systems, is used to generate and reconstruct events of the MPD experiment, to study the SARS-CoV-2 virus within the Folding@Home project on available cloud resources and to integrate clouds of the JINR Member States' organizations into a distributed platform.</p><p>The load of the parallel cluster is not always 100%. That is natural that the load is not constant on this type of system. To improve resource utilization it is possible to use it for scientific projects which do not require dedicated resources but could benefit from opportunistic resources. Another possible use is introducing a parallel cluster to the studying process.</p><p>The parallel cluster was integrated into the DIRAC instance in the Joint Institute for Nuclear Research. This instance was supported and gradually improved since 2016. It supports educational and scientific groups of users: Multi-Purpose Detector, Baryonic Matter at Nuclotron, and Baikal-GVD collaboration groups. That allows getting scientific jobs by REA resources in case of scientific collaboration. To integrate REA parallel cluster the pilot jobs should be able to run on the resource. The pilot job works like a wrapper job for user workload. It checks the environment, operating system, software, RAM, and CPU performance. This information is sent to DIRAC to match the appropriate job for the pilot. Since SLURM is used as a batch system on the parallel cluster, a special DIRAC module has been used. An additional system user named "dirac" was created to represent jobs submitted by DIRAC users.</p><p>The first issue was related to the default Python version. On the parallel cluster, it is Python 3.6.5, but right now, DIRAC works only on Python 2.7 version. Special settings for DIRAC users allowed changing the default Python version to the correct one. The second issue with integration was related to time settings on the cluster. Since DIRAC is being oriented to distributed systems, it requires all resources to keep time precisely. After fixing time DIRAC was able to submit user jobs to pilots.</p><p>After these corrections, DIRAC was able to submit user jobs and get results. However, it took much time for pilots to start. The starting of DIRAC pilots means downloading the TAR archive with all python code and extracting it. This is IO intensive operation, and shared file systems usually do not perform it well. The shared file system on the parallel cluster is based on CEPH. To fix that issue DIRAC was instructed to set the working directory for pilots not on CEPH but disk. Whit that fixes DIRAC started to work effectively.</p><p>The second part of the integration was checking parallel cluster performance. The cluster has 32 slots for jobs and equipped with Intel Xeon Gold 6130 CPU. It is important to know the performance of an individual slot. DIRAC uses a special benchmark called DB12 for analysis of CPU performance. The benchmark showed results of around 25 HEP-SPEC06 for one slot. That is a good result which is better or comparable with most processors used in JINR distributed infrastructure up to now. Then the network was tested with a standard upload/download test. The result showed 100MB/s transfer speed. It is worth notice that jobs running through DIRAC may use GPU resources on the cluster. That makes it useful not only for CPU load but also for GPU load.</p><p>Provided numbers show that high computing power of the REA parallel cluster may be accessed now through DIRAC. This allows using it by students in the education process. Another possible use is the participation of the REA parallel cluster in international scientific experiments by providing computing power. And if some resources are idle they may be utilized in the Folding@HOME project or other projects.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusion</head><p>In the paper, we have discussed several perspectives on creating and maintaining the international distributed cloud infrastructure and underlying architecture, including network aspects. There were presented ways of gluing clouds together to provide system services for distributed computing, resources, and interfaces for application tasks. There is an overview of the international distributed cloud infrastructure of the Joint Institute for Nuclear Research (JINR) and the cloud infrastructure of the Plekhanov Russian University of Economics (PRUE) as a part of the distributed cloud. The paper emphasizes the unique role of the DIRAC grid interware in integrating cloud resources from some JINR Member State organizations as PRUE cloud. The particular part is about the integration of the highperformance parallel resources to the cloud.s</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 2 .</head><label>2</label><figDesc>Fig.2. Distribution of jobs by clouds of the Member States' organization</figDesc><graphic coords="3,223.60,499.20,169.90,149.55" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. The network structure of the PRUE cloud</figDesc><graphic coords="4,233.35,239.45,142.80,224.70" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="5,167.65,212.90,309.60,197.40" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_0">Proceedings of the Big data analysis tasks on the supercomputer GOVORUN Workshop (SCG2020)Dubna, Russia, September 16, 2020</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgement</head><p>The study was carried out at the expense of the Russian Science Foundation grant (project No. 19-71-30008).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<ptr target="http://nica.jinr.ru/" />
		<title level="m">NICA (Nuclotron-based Ion Collider fAсility</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<ptr target="https://home.cern/science/accelerators/large-hadron-collider" />
		<title level="m">Large Hadron Collider</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">A</forename><surname>Balashov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">V</forename><surname>Baranov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">A</forename><surname>Kutovskiy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">N</forename><surname>Makhalkin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ye</forename><forename type="middle">M</forename><surname>Mazhitova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">S</forename><surname>Pelevanyuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">N</forename><surname>Semenov</surname></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-2507/185-189-paper-32.pdf" />
		<title level="m">Proc. of the 27th International Symposium on Nuclear Electronics &amp; Computing (NEC&apos;2019)</title>
				<meeting>of the 27th International Symposium on Nuclear Electronics &amp; Computing (NEC&apos;2019)</meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title/>
		<author>
			<persName><forename type="first">A</forename><surname>Sh</surname></persName>
		</author>
		<author>
			<persName><surname>Petrosyan</surname></persName>
		</author>
		<idno type="DOI">10.1051/epjconf/201921403039</idno>
		<ptr target="https://doi.org/10.1051/epjconf/201921403039" />
	</analytic>
	<monogr>
		<title level="j">EPJ Web of Conf</title>
		<imprint>
			<biblScope unit="volume">214</biblScope>
			<biblScope unit="page">3039</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">A</forename><surname>Balashov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">I</forename><surname>Kuchumov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">A</forename><surname>Kutovskiy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">S</forename><surname>Pelevanyuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">N</forename><surname>Petrunin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Yu</surname></persName>
		</author>
		<author>
			<persName><surname>Tsaregorodtsev</surname></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-2507/256-260-paper-45.pdf" />
		<title level="m">Proc. of the 27th International Symposium on Nuclear Electronics &amp; Computing (NEC&apos;2019)</title>
				<meeting>of the 27th International Symposium on Nuclear Electronics &amp; Computing (NEC&apos;2019)</meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<ptr target="https://www.rea.ru/ru/org/managements/unitscires/Laboratorija-Oblachnykh-tekhnologijj-i-analitiki-Bolshikh-dannykh/Pages/lotiabd.aspx" />
		<title level="m">Scientific laboratory of cloud technologies and Big Data Analytics of Plekhanov Russian University of Economics</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Integration of the JINR Hybrid Computing Resources with the DIRAC Interware for Data Intensive Applications</title>
		<author>
			<persName><forename type="first">V</forename><surname>Korenkov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Pelevanyuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Tsaregorodtsev</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-51913-1_3</idno>
		<ptr target="https://doi.org/10.1007/978-3-030-51913-1_3" />
	</analytic>
	<monogr>
		<title level="m">Data Analytics and Management in Data Intensive Domains. DAMDID/RCDL 2019</title>
		<title level="s">Communications in Computer and Information Science</title>
		<editor>
			<persName><forename type="first">A</forename><surname>Elizarov</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">B</forename><surname>Novikov</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><surname>Stupnikov</surname></persName>
		</editor>
		<meeting><address><addrLine>Cham</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">1223</biblScope>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
