China
Africa
Explore chapters and articles related to this topic
The System of the Supervision and the Visualization of Multimedia Data for BG
Published in Adam Weintrit, Marine Navigation, 2017
M. Blok, B. Czaplewski, S. Kaczmarek, J. Litka, M. Narloch, M. Sac
Within each of the three archive management servers virtual environments have been set up, which are used for creating functional clusters. The virtualization utilizes method called LXC (Linux Containers). The LXC is not an independent operating system running on the machine, but is a separate space within the operating system. It allows allocation of CPU, memory, disk space and network interfaces. For programs running in LXC containers processes, network access, user privileges and access to the files are separated. From the point of resource commitment the LXC virtualizes only the application and not the entire operating system, therefore it does not need a separate virtual machine with its own operating system. This means that the LXC generates little overhead because all the applications use standard libraries for system calls, I/O and networking.
A Container-Based Technique to Improve Virtual Machine Migration in Cloud Computing
Published in IETE Journal of Research, 2022
Aditya Bhardwaj, C. Rama Krishna
Similarly, Martin et al. [24] extended this study with emerging container alternative technology namely CoreOS Rkt which is owned by Red Hat Linux in 2018 [25]. This container technology focuses on ease of application development. The authors investigated the performance of Rkt container by running compute and data-intensive applications. To compare the results obtained, they considered LXC, Docker as the representative of alternative container technologies. From their results obtained, it is found that Docker container causes performance degradation because time sharing algorithm in Docker create frequent context switching overhead. However, LXC container shows better performance for data-intensive environment and Rkt container gives promising results in compute-intensive scenarios.
Versatile IT-system architecture for smart manufacturing solutions: the example for green manufacturing
Published in International Journal of Computer Integrated Manufacturing, 2021
Martin Plank, Sebastian Thiede, Christoph Herrmann
As previously shown, the decoupling between functions and user-programmable entities is achieved by the use of an abstraction layer (Figure 4). This can be achieved by two basic types of abstraction. A first type pursues the goal of unification. This includes interpreter languages (e.g. JavaScript, Python or Pearl) and runtime environments (e.g. Java or .NET) that are available for different platforms and systems. Likewise, the use of a common operating system can serve this purpose. A second type uses virtualization to provide the functions with the required resources and dependencies. Examples are virtual machines or container virtualizations (e.g. Docker, rkt or LXC). The selection of a suitable abstraction type and a specific implementation as an abstraction layer strongly depends on complexity and the functional scope of the functions concerned. Because of the low overhead, the unification by interpreters or runtime environments is primarily suitable for function blocks with a low complexity. For complex function blocks or existing software systems, virtualization approaches are better suited to adapt to the various requirements. The use of a uniform operating system relates to special challenges in the practical application, as the availability of an operating system suitable for all system levels of a factory is missing. Therefore, these are not considered further in the context of this paper.
Incorporating the Raft consensus protocol in containers managed by Kubernetes: an evaluation
Published in International Journal of Parallel, Emergent and Distributed Systems, 2020
Hylson Netto, Caio Pereira Oliveira, Luciana de Oliveira Rech, Eduardo Alchieri
The Linux operating system has some components that enable virtualisation at the system level. Containers are VMs instantiated from static images. When a container turns off, its state1 is lost. Usually, containers also do not maintain session data about specific clients. Consequently, containers are known as stateless VMs. Images of containers are usually small because only files that do not exist in its host are effectively stored in the container image. This is possible with the use of a layered file system, e.g. aufs. Therefore, the creation of containers is fast and resource provisioning becomes more efficient, in comparison to the traditional VMs [32]. The Linux kernel containment features is more known as LXC,2 which gain popularity since Docker [13,14] extended it and became the most popular container implementation.