CN111880738A - A method for automatically creating and mounting LVM volumes in a K8s environment - Google Patents

Abstract

The invention particularly relates to a method for automatically creating and mounting LVM volumes in a K8s environment. The method of automatically creating and mounting LVM volumes in the K8s environment is based on the Kubernetes environment. First, create an image to automatically create and mount LVM volumes. Then, define the Configmap pipe and Job to manage the image created by the single-copy Pod operation, configure container permissions, Environment variables, required mounts, and node selection; finally, use the Kubernetes client to run the previously created yaml files, including Configmap and Deployment, to automatically create and mount LVM volumes for target node operation, which can be run repeatedly and support subsequent LVM volumes. An extension that provides node services to use local storage. The method of automatically creating and mounting LVM volumes in the K8s environment uses the Kubernetes Job to read the relevant configuration to complete the conversion of the target disk to the LVM volume, and mount it to the target directory for service use, which is similar to the manual completion of the disk initialization and mounting process. It greatly improves ease of use and manageability, and can meet the needs of local storage for Kubernetes services in production environments.

Description

A method for automatically creating and mounting LVM volumes in a K8s environment

technical field

The invention relates to the technical field of cloud computing, in particular to a method for automatically creating and mounting LVM volumes in a K8s environment.

Background technique

Kubernetes, or K8s for short, is an acronym for replacing the eight-character "ubernete" with eight. As an open source for managing containerized applications on multiple hosts in a cloud platform, Kubernetes aims to make deploying containerized applications simple and efficient. Kubernetes provides a mechanism for resource application deployment, planning, updating and maintenance.

The workload of a Kubernetes cluster can use a variety of storage methods. Most disk plug-ins use remote storage to keep persistent data independent of computing nodes. However, remote storage usually cannot provide the excellent read and write performance of local storage. LVM (Logical Volume Management) represents a local disk directly bound to the computing node, but the premise of use is that the process of creating and mounting directories needs to be completed manually. Currently, the mainstream way to implement local directories is LVM. As a mechanism for managing disk partitions in a Linux environment, users can easily adjust the size of each partition without downtime.

In order to improve the usability of creating and mounting directories, the present invention proposes a method for automatically creating and mounting LVM volumes in a K8s environment.

SUMMARY OF THE INVENTION

In order to make up for the defects of the prior art, the present invention provides a simple and efficient method for automatically creating and mounting LVM volumes in the K8s environment.

The present invention is achieved through the following technical solutions:

A method for automatically creating and mounting LVM volumes in a K8s environment, characterized in that: based on the Kubernetes environment, the method includes the following steps:

The first step is to create an image that automates the creation and mounting of LVM volumes. Install the lvm2 package on the basis of the native base image, and execute the relevant Linux commands required to automatically create and mount LVM volumes;

The second step is to define five basic operations implemented by the Configmap management shell script, including reading the disk to create PV (physical volume), creating VG (volume group) and adding PV to it, reading size, creating or expanding LV (logical volume) , format LV or extend LV, read target path and mount LV;

The third step is to define the image created by the Job management single-copy Pod operation, configure container permissions, environment variables, required mounts, and node selection;

The fourth step is to use the Kubernetes client to run the previously created yaml file, including Configmap and Deployment, to automatically create and mount LVM volumes for target node operation, which can be run repeatedly and support subsequent expansion of LVM volumes, providing node services using local storage .

In the first step, relevant Linux commands include but are not limited to pvcreate, vgcreate, vgextend, lvcreate, lvextend, mkfs, and resize2fs commands.

In the second step, the process of automatically creating and mounting LVM is defined using Configmap, including configuring PV, configuring VG, configuring LV, formatting LV, and configuring mounting.

Among them, the process of configuring PV is as follows: cyclically read the disk parameter list, first check if fdisk-l exists for each disk, if there is no error and exit, otherwise continue to execute; then pvs checks whether the disk has done PV, if not Execute the pvcreate command to create the PV, otherwise exit normally until all disks are processed.

The process of configuring the VG is as follows: first, vgs checks whether the VG already exists. If the vgcreate command is not executed, the VG is generated according to the created PV; otherwise, the disk parameter list is read in a loop to check whether the PV is in the VG. If the vgextend command is not executed, the PV is added to the VG. VG, otherwise exit normally until all disks are processed.

The process of configuring LV is as follows: First, lvs checks whether the LV already exists. If the planned LV size is not read, execute the lvcreate command to create an LV. If the execution fails, it means that the planned size exceeds the actual size of the VG, then use the available size of the VG to create the LV, otherwise exit normally; Otherwise, read the planned LV size and execute the lvextend command to expand the LV. If the execution fails, judge according to the command output. If match is included, it means that the current LV size is equal to the planned size. If Insufficient is included, it means that the current planned size exceeds the actual size of the VG, and the LV is extended using the available size of the VG. Otherwise, it means that the current LV size exceeds the planned size and exits normally.

The process of formatting LV is as follows: First, df checks whether the LV has been mounted. If it is not mounted, execute the mkfs.ext4 command to format the LV; otherwise, judge the size of the LV and the size of the mounted directory. If the former exceeds the latter, execute resize2fs to extend the LV.

The process of configuring the mount is as follows: first grep to check whether there is an LV in /etc/fstab, if the target directory is not read, add the mount configuration to /etc/fstab, otherwise exit normally; then execute mount-a, the target directory is already Mounted successfully.

In the third step, the environment variables include the stored disk list, the planned LV size and the target mount path; the required mounts include /run, /etc/fstab, /dev, Configmap and the target path; the configuration node selection guarantees Pod runs on the target node.

When the business requirements of the node need to expand the size of the local storage volume, adjust the environment variable configuration in the third step, such as the disk list and the planned LV size, and then delete the job through the Kubernetes client, and then perform the fourth step. The expansion of the local storage volume size is done automatically.

The beneficial effects of the present invention are: the method for automatically creating and mounting LVM volumes in the K8s environment, with the help of KubernetesJob reading the relevant configuration to complete the conversion of the target disk to the LVM volume, and mounting it on the target directory to provide service use, and manually completing the disk Compared with the initialization and mounting process, the ease of use and manageability are greatly improved, and it can meet the needs of using local storage for Kubernetes services in the production environment.

Description of drawings

In order to illustrate the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are For some embodiments of the present invention, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative efforts.

FIG. 1 is a schematic diagram of the method for automatically creating and mounting LVM volumes in the K8s environment of the present invention.

Detailed ways

In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the embodiments of the present invention. Obviously, the described embodiments are only some, but not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The method for automatically creating and mounting LVM volumes in the K8s environment is based on the Kubernetes environment, including the following steps:

The first step is to create an image that automates the creation and mounting of LVM volumes. Install the lvm2 package on the basis of the native base image, and execute the relevant Linux commands required to automatically create and mount LVM volumes;

The second step is to define five basic operations implemented by the Configmap management shell script, including reading disk to create PV, creating VG and adding PV to it, reading size, creating or extending LV, formatting LV or extending LV, and reading target path mount LV;

The third step is to define the image created by the Job management single-copy Pod operation, configure container permissions, environment variables, required mounts, and node selection;

The fourth step is to use the Kubernetes client to run the previously created yaml file, including Configmap and Deployment, to automatically create and mount LVM volumes for target node operation, which can be run repeatedly and support subsequent expansion of LVM volumes, providing node services using local storage .

In the first step, relevant Linux commands include but are not limited to pvcreate, vgcreate, vgextend, lvcreate, lvextend, mkfs, and resize2fs commands.

In the second step, the process of automatically creating and mounting LVM is defined using Configmap, including configuring PV, configuring VG, configuring LV, formatting LV, and configuring mounting.

Among them, the process of configuring PV is as follows: cyclically read the disk parameter list, first check if fdisk-l exists for each disk, if there is no error and exit, otherwise continue to execute; then pvs checks whether the disk has done PV, if not Execute the pvcreate command to create the PV, otherwise exit normally until all disks are processed.

The process of configuring the VG is as follows: first, vgs checks whether the VG already exists. If the vgcreate command is not executed, the VG is generated according to the created PV; otherwise, the disk parameter list is read in a loop to check whether the PV is in the VG. If the vgextend command is not executed, the PV is added to the VG. VG, otherwise exit normally until all disks are processed.

The process of configuring LV is as follows: First, lvs checks whether the LV already exists. If the planned LV size is not read, execute the lvcreate command to create an LV. If the execution fails, it means that the planned size exceeds the actual size of the VG, then use the available size of the VG to create the LV, otherwise exit normally; Otherwise, read the planned LV size and execute the lvextend command to expand the LV. If the execution fails, judge according to the command output. If match is included, it means that the current LV size is equal to the planned size. If Insufficient is included, it means that the current planned size exceeds the actual size of the VG, and the LV is extended using the available size of the VG. Otherwise, it means that the current LV size exceeds the planned size and exits normally.

The process of formatting LV is as follows: First, df checks whether the LV has been mounted. If it is not mounted, execute the mkfs.ext4 command to format the LV; otherwise, judge the size of the LV and the size of the mounted directory. If the former exceeds the latter, execute resize2fs to extend the LV.

The process of configuring the mount is as follows: first grep to check whether there is an LV in /etc/fstab, if the target directory is not read, add the mount configuration to /etc/fstab, otherwise exit normally; then execute mount-a, the target directory is already Mounted successfully.

In the third step, the environment variables include the stored disk list, the planned LV size and the target mount path; the required mounts include /run, /etc/fstab, /dev, Configmap and the target path; the configuration node selection guarantees Pod runs on the target node.

When the business requirements of the node need to expand the size of the local storage volume, adjust the environment variable configuration in the third step, such as the disk list and the planned LV size, and then delete the job through the Kubernetes client, and then perform the fourth step. The expansion of the local storage volume size is done automatically. When the Pod status is Completed, the available size of the target directory of the configuration mount has been adjusted.

In the fourth step, use the Kubernetes client to run Configmap and Job, and view the node when the Pod status is Completed. At this time, the local disk has been automatically converted into an LVM volume and mounted to the target directory, which can provide services for node operation;

Compared with the current existing technology, the method for automatically creating and mounting LVM volumes in the K8s environment has the following characteristics:

First, with the help of shell scripts, the process of automatically creating and mounting LVM volumes can be flexibly customized;

Second, using the Job object in the Kubernetes cluster can automatically complete the steps required for the task at one time, no longer rely on any manual operation process, ensure the controllability of configuration, avoid manual operation errors, and greatly improve node creation And the ease and manageability of mounting LVM volumes.

The above-mentioned embodiment is only one of the specific embodiments of the present invention, and the usual changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. a method for automatically creating and mounting LVM volumes in a K8s environment, characterized in that: based on the Kubernetes environment, comprising the following steps: The first step is to create an image that automates the creation and mounting of LVM volumes. Install the lvm2 package on the basis of the native base image, and execute the relevant Linux commands required to automatically create and mount LVM volumes; The second step is to define five basic operations implemented by the Configmap management shell script, including reading disk to create PV, creating VG and adding PV to it, reading size, creating or extending LV, formatting LV or extending LV, and reading target path mount LV; The third step is to define the image created by the Job management single-copy Pod operation, configure container permissions, environment variables, required mounts, and node selection; The fourth step is to use the Kubernetes client to run the previously created yaml file, including Configmap and Deployment, to automatically create and mount LVM volumes for target node operation, which can be run repeatedly and support subsequent expansion of LVM volumes, providing node services using local storage . 2. K8s environment according to claim 1 automatically creates and mounts the method for LVM volume, it is characterized in that: in the described first step, relevant Linux commands include but are not limited to pvcreate, vgcreate, vgextend, lvcreate, lvextend, mkfs , resize2fs command. 3. the method for automatic creation and mount LVM volume of K8s environment according to claim 2, is characterized in that: in the described second step, utilize Configmap to define the process of automatic creation and mount LVM, comprise configuration PV, configuration VG , configure LV, format LV and configure mount. 4. K8s environment according to claim 3 automatically creates and mounts the method for LVM volume, it is characterized in that: the process of configuring PV is as follows: read disk parameter list circularly, to each disk first fdisk-1 checks whether there is, If there is no error and exit, otherwise continue to execute; then pvs checks whether the disk has already done PV, if the pvcreate command is not executed to create a PV, otherwise exit normally until all disks are processed. 5. K8s environment according to claim 3 automatically creates and mounts the method for LVM volume, it is characterized in that: the process of configuring VG is as follows: at first vgs checks whether VG already exists, if not executing vgcreate command, generate VG according to the PV created ; Otherwise, read the disk parameter list in a loop, check whether the PV is in the VG, if the vgextend command is not executed, add the PV to the VG, otherwise exit normally until all the disks are processed. 6. the method for automatically creating and mounting LVM volume in K8s environment according to claim 3, it is characterized in that: the process of configuring LV is as follows: at first lvs checks whether LV already exists, if there is no read planning LV size, execute lvcreate command to create LV, if the execution fails, it means that the planned size exceeds the actual size of the VG, use the available size of the VG to create the LV, otherwise exit normally; otherwise, read the planned LV size and execute the lvextend command to expand the LV. If the execution fails, judge according to the command output. If it contains match, it means the current The LV size is equal to the planned size. If Insufficient is included, it means that the current planned size exceeds the actual size of the VG, and the LV is extended with the available size of the VG. Otherwise, the current LV size exceeds the planned size and exits normally. 7. K8s environment according to claim 3 automatically creates and mounts the method for LVM volume, it is characterized in that: the process of formatting LV is as follows: at first df checks whether LV has been mounted, if not mounted, execute mkfs.ext4 command Format the LV; otherwise, judge the size of the LV and the size of the mounted directory. If the former exceeds the size of the latter, execute resize2fs to extend the LV. 8. K8s environment according to claim 3 automatically creates and mounts the method for LVM volume, it is characterized in that: the process of configuration mount is as follows: at first grep checks /etc/fstab whether there is LV, if not read target directory add Mount the configuration to /etc/fstab, otherwise exit normally; then execute mount-a, and the target directory has been successfully mounted. 9. K8s environment according to claim 1 automatically creates and mounts the method for LVM volume, it is characterized in that: in the described 3rd step, environment variable comprises the disk list of ground storage, planning LV size and target mount path; The required mounts include /run, /etc/fstab, /dev, Configmap, and the target path; the configuration node selection ensures that the Pod runs on the target node. 10. The method for automatically creating and mounting an LVM volume in a K8s environment according to claim 1 or 9, wherein: when the business requirement of the node needs to expand the size of the local storage volume, the environment variable in the third step is adjusted Configuration, then delete the job through the Kubernetes client, and then perform the fourth step to automatically complete the expansion of the size of the local storage volume.

Images