main| new issue| archive| editorial board| for the authors| publishing house|
Ðóññêèé
Main page
New issue
Archive of articles
Editorial board
For the authors
Publishing house

 

 


ABSTRACTS OF ARTICLES OF THE JOURNAL "INFORMATION TECHNOLOGIES".
No. 12. Vol. 27. 2021

DOI: 10.17587/it.27.619-625

I. V. Bychkov, Academician of RAS, Professor, e-mail: idstu@icc.ru, S. A. Gorsky, Ph.D., Senior Researcher, e-mail: gorskysergey@mail.ru, A. G. Feoktistov, Ph.D., Assistant Professor, e-mail: agf@icc.ru, R. O. Kostromin, Junior Researcher, e-mail: kostromin@icc.ru, Matrosov Institute for System Dynamics and Control Theory of SB RAS, Irkutsk, 664033, Russian Federation

Support for Computing in Distributed Environments Based on Continuous Integration

Nowadays, tools for designing scientific applications often do not implement the required continuous integration capabilities of the applied software. Therefore, such overheads as the application development time and experiment execution makespan are substantially increased. In this regard, we propose a new approach to developing scientific applications and carrying out experiments with them. It is based on applying continuous integration to both the applied and system software in developing distributed applied software packages with a modular architecture using the Orlando Tools framework. Within the proposed approach, we provide integrating the Orlando Tools subsystems with the GitLab system and automating the development of package modules. At the same time, Orlando Tools fully support constructing and testing problem-solving schemes (workflows) that combine package modules located on environment resources with different computational characteristics. To this end, Orlando Tools provides the necessary configuring and setting up of computational resources. The practical significance of our study is substantial reduction overheads needed to experiment fulfillments and increase of the resource use efficiency.
Keywords: distributed computing, software, packages, continuous integration, GitLab

P. 619–625

To the contents