It has the characteristics of compact, flexible and convenient customization. This paper introduces the function and structure of ovirt-node, as well as the acquisition, installation, customization of Ovirt-node.
Ovirt-node is the client part of the open source virtualization management platform Ovirt, a customized minimized fedora system that acts as a virtual Machine Manager (Hypervisor) host, and a virtualization management platform with the management end Overt-engine. Ovirt-node with its small, flexible features, can be easily developed and customized.
Ovirt-node Introduction
Ovirt-node is an open source project in the Ovirt community, designed to build a streamlined, robust operating system image that can use minimized resources to provide the virtual machines that control the virtual machine's ability to run on it.
Simply put, Ovirt-node is a small host mirror that provides LIBVIRT/VDSM (Virtual http://www.aliyun.com/zixun/aggregation/16493.html ">desktop Server manager) and virtualization services such as KVM (Kernel based virtual machine), use LIBVIRT/VDSM to manage KVM virtual machines.
The difference between Ovirt-node and regular Linux distributions is that Ovirt-node focuses on providing virtualization functionality, which contains only the software and virtual machine management software needed to minimize the operating system, about 200 RPM installation packages, and an API with a good management interface. Compared to the ordinary Linux distribution, ovirt-node only need a very small operating environment, its installation image is less than 150M, installed to disk space is less than 1G, Runtime storage only 500M, in addition, can also be customized according to the requirements of virtual machine management software, such as libvirt/ Vdsm.
Because Ovirt-node is customized based on the minimal Fedora system, the Ovirt-node installation image is very small, in addition to the need to install some necessary system management software, network management software, etc., but also need to include a KVM module, together to manage the KVM Libvirt or VDSM. Therefore, it is entirely possible to ignore the overhead of the resources that are generated by running Ovirt-node, so that more resources can be allocated to the virtual machines in the node.
Figure 1. Shows the components of the entire virtualization platform
Composition of the Overt-node
Ovirt-node are usually published in ISO and RPM, and the main included RPM has two types:
Ovirt-node related RPM Package: 1 A user-friendly installation and configuration of the TUI interface, the user can easily configure the graphical polyamide, 2, automated installation and configuration scripts, 3 custom Sysinit scripts.
ovit-node-tools:1) some kickstart files; 2 minimal the list of installation packages and some tools for creating image.
The difference between Ovirt-node's ISO and normal Linux distributions is that it can be installed on a local hard drive, flash memory or SD card, Ovir-node only save some basic configuration information, is a stateless system, any changes in the root directory after the system reboot will be lost.
For Ovirt-node upgrades, we can choose to start with a new image or save image to a specified place, add upgrade parameters to the boot parameter to upgrade.