IT Home January 28 news, in January 2022, with the joint efforts of Kirin Software and Euler open source community, the NestOS Beta version that supports x86_64 and aarch64 architecture at the same time was finally released, at the same time, the NestOS official website was officially launched, you can go to the official website to download the experience.
NestOS official website: https://nestos.org.cn
In terms of hardware adaptation, NestOS has completed adaptation verification on devices such as Feiteng FT2000+, S2500 and Kunpeng Kunpeng920, and supports installation and deployment in bare metal and virtualization. In the future, it will continue to expand to support more platforms, bringing more possibilities to NestOS.
▲ NestOS Beta version architecture diagram
NestOS is equipped with common container engines such as docker, iSulad, podman, and cri-o, which provides a variety of basic operating environments suitable for cloud scenarios and is optimized for Kubernetes scenarios. At the same time, in terms of IaaS ecological construction, we will provide support for openStack, oVirt and other platforms; in terms of PaaS ecological construction, we will also provide relevant support for OKD (openShift), Rancher and other platforms.
▲ NestOS roadmap diagram
NestOS technical features
Out-of-the-box container platform: Container technology overcomes the problems of large-scale cluster service O&M difficulties caused by user modification of system configuration and conflicting dependencies of user services on system components, and can quickly install and deploy, expand and shrink according to service loads, and smooth migration of services during node O&M, which is the most important basic core in the cloud-native era. At present, the mainstream general server operating system needs to be installed and deployed again for cloud scene adaptation adjustment, and NestOS integrates and adapts mainstream container engines such as iSulad, Docker, Podman, cri-o, etc., which can be used out of the box and can provide users with a lightweight, customized cloud scene operating system.
Easy-to-use installation and configuration process: NestOS uses Ignition technology to easily configure high-volume cluster node installations with the same configuration. Ignition is a distribution-independent configuration utility for installing and configuring the system and initializing NestOS. Ignition configuration files can contain configurations for networking, storage, file systems, systemd units, and user authentication and rights management. During the installation phase, NestOS not only supports manually running the nestos-installer command after booting the installation image, loading the Ignition configuration file, and completing the local installation of NestOS, or adding the remote Ignition configuration access address to the boot boot parameters through PXE to achieve mass cluster node network boot mode installation.
Secure and reliable package management: NestOS uses rpm-ostree for package management, which can be seen as a combination of rpm and ostree. Rpm-ostree provides rpm-based package installation management on the one hand, and ostree-based operating system update upgrades on the other hand. Each time the user updates the system, it is like rpm-ostree committing a "Transaction", ensuring that the update process is all successful or all failed, and allowing the system to be rolled back to the pre-update state after the update system encounters an exception.
Friendly and controllable automatic update mechanism: NestOS provides automatic update service, which acts as a remote update service and rpm-ostree client, responsible for detecting whether the update server has an updated version, and implementing automatic node update and reboot. The service supports automatic update agent, user-defined configuration files and a variety of update policies, users can configure whether to automatically update, automatic update policies and other options, or combine with the upper-level cluster service to migrate the current node service load and then update, to achieve orderly upgrade of cluster nodes, to ensure that cluster services are not interrupted by node upgrades. When the cluster node needs to make unified configuration modifications or updates to the basic environment, the updated version after the modification has been fully verified can be released to the update server, and the cluster node will complete the unified upgrade through the automatic update mechanism.
Closely matched dual system partitioning: NestOS uses a dual system partition design, the two partitions are set to active mode and passive mode, and perform their duties during system operation. The active partition is responsible for system operation, the passive partition is responsible for system upgrade, and the active partition is set to a read-only state during system operation to ensure the integrity and security of NestOS during operation. When a new version of the operating system is released, a complete file system will be downloaded to the passive partition, and when the system reboots and boots from the new version of the partition, the original passive partition will be switched to the active partition, while the previous active partition will be switched to the passive partition, and the roles played by the two partitions will be reversed to each other, waiting for the next system update.
Note: The Euler open source community does not currently support podman, and the podman used by Nestos will be gradually merged into the Euler open source community community.
NestOS usage documentation
https://gitee.com/openeuler/NestOS