CN115421853A - Storage system management method and device based on container cluster and computer equipment - Google Patents

Abstract

The application provides a storage system management method and device based on a container cluster and computer equipment, and belongs to the technical field of computers. The method comprises the following steps: when an initial host machine fails, determining an initial local storage volume, wherein the initial local storage volume is a storage volume bound with the initial host machine and is created according to a storage statement of an initial container; acquiring configuration information of the initial local storage volume, and removing the initial local storage volume, wherein the configuration information is used for representing configuration parameters and a storage position of the initial local storage volume; creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host machine; the initial container is removed, a new target container is created, and the target local storage volume is mounted on the target container. The container can be restarted correctly under the condition that the host machine is down, and the container can work normally.

Description

Storage system management method and device based on container cluster and computer equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for managing a storage system based on a container cluster, and a computer device.

Background

With the development of computer technology, a container-cluster storage system brings great convenience to the working life of people, files in a container are generally temporarily stored on a disk, when the container is crashed, the container needs to be restarted, and data generated when an application program modifies the files in the container can be lost while the container is restarted. To retain such files or data that may be lost, a persistent storage volume is required.

In the related art, generally, a container is bound to a persistent volume, a file or a directory in the container can be mapped onto a host through the bound persistent volume, and when the container is reconstructed, a newly created container is still bound to a previously bound persistent volume, that is, the reconstructed container still mounts a previous persistent volume, and can continue to use a file previously stored on the host, so that an application program can retain data or a file before the container is reconstructed when calling the reconstructed container. After the persistent volume is bound to the container, the container must be dispatched to the host where the persistent volume is located when the container is rescheduled, that is, the container and the host have a binding relationship.

However, if a host is down, the persistent volume corresponding to the down host cannot work, and the container mounting the persistent volume cannot be restarted by scheduling the persistent volume to other available hosts, then the binding relationship between the container and the persistent volume on other available hosts cannot be established, and the binding relationship between the container and other available hosts cannot be established. Therefore, the scheme has the problem that the container cannot be restarted under the condition that the host machine is down, so that the container cannot work normally.

Disclosure of Invention

The application aims to provide a storage system management method and device based on a container cluster and computer equipment, which can achieve the effect of correctly restarting a container under the condition that a host is down and ensuring that the container can work normally.

The embodiment of the application is realized as follows:

in a first aspect of embodiments of the present application, a method for managing a storage system based on a container cluster is provided, where the method includes:

when the initial host machine fails, determining an initial local storage volume; the initial local storage volume is a storage volume bound with the initial host, and the initial local storage volume is created according to a storage statement of an initial container;

acquiring configuration information of the initial local storage volume, and removing the initial local storage volume, wherein the configuration information is used for representing configuration parameters and a storage position of the initial local storage volume;

creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host, wherein the target host is a host which does not have a fault;

and removing the initial container, creating a new target container, and mounting the target local storage volume on the target container.

Optionally, the step of determining an initial local storage volume includes:

determining an initial local storage volume bound with the initial host according to the initial mapping relation of each local storage volume;

each local storage volume comprises the initial local storage volume, and the initial mapping relationship is used for indicating a binding relationship between the local storage volume and each host.

Optionally, the configuration parameters include a storage type, a storage capacity, and an access mode of the initial local storage volume, and the storage location includes an initial working directory of the initial local storage volume on the initial host;

the creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host, including:

creating the target local storage volume according to the storage type, the storage capacity and/or the access mode of the initial local storage volume;

configuring a target working directory on the target host machine for the target local storage volume according to the initial working directory;

and binding the target local storage volume with the target host machine, and configuring a target mapping relation matched with the target host machine for the target local storage volume.

Optionally, configuring, according to the initial working directory, a target working directory on the target host for the target local storage volume includes:

reading the initial working catalog, and creating a target working catalog which is the same as the initial working catalog on the target host machine;

and configuring the target working catalog to the target local storage volume.

Optionally, the configuration information further includes node affinity (nodesaffinity) information of the initial local storage volume, where the node affinity information is used to determine a host that matches the initial local storage volume;

before configuring, according to the initial working directory, a target working directory on the target host for the target local storage volume, the method further includes:

and determining the host machine which is matched with the target local storage volume and does not have the fault according to the node affinity information, and taking the host machine which is matched with the target local storage volume and does not have the fault as the target host machine.

Optionally, before determining the initial local storage volume when the initial host fails, the method further includes:

monitoring the working state of the initial host machine in real time;

and determining whether the initial host machine fails according to the working state of the initial host machine.

Optionally, the determining whether the initial host fails according to the working state of the initial host includes:

determining the number of times that the initial host machine enters a fault state within a preset time length, wherein the starting time of the preset time length is the time when the working state of the initial host machine is monitored to change;

and determining that the initial host machine fails according to the frequency of the initial host machine entering the failure state.

Optionally, the determining whether the initial host fails according to the working state includes:

determining the working states of the initial host machine at a first moment and a second moment;

and if the working states of the initial host machine at the first moment and the second moment are fault states, determining that the initial host machine is in fault.

Optionally, before determining the initial local storage volume when the initial host fails, the method further includes:

creating the initial local storage volume according to a storage statement of the initial container, wherein the storage statement is used for indicating configuration parameters of the initial local storage volume;

determining the initial host machine matched with the initial local storage volume, binding the initial local storage volume with the initial host machine, and configuring an initial working catalog of the initial local storage volume on the initial host machine.

Optionally, the creating the initial local storage volume according to the storage declaration of the initial container includes:

generating a storage statement of the initial container according to the storage capacity and/or the access mode storage type required by the initial container;

writing the storage type of the local storage volume needing to be mounted in the initial container into a storage statement of the initial container;

and creating the initial local storage volume according to the storage statement of the initial container.

Optionally, the determining the initial host machine in the storage system that matches the initial local storage volume and binding the initial local storage volume with the initial host machine includes:

determining the initial host machine matched with the initial local storage volume according to the node affinity information of the initial local storage volume;

and binding the initial local storage volume with the initial host machine, and configuring an initial mapping relation matched with the initial host machine for the initial local storage volume.

In a second aspect of the embodiments of the present application, there is provided a storage system management apparatus based on a container cluster, where the storage system management apparatus based on a container cluster includes:

the determining module is used for determining an initial local storage volume when the initial host machine fails; the initial local storage volume is a storage volume bound with the initial host, and the initial local storage volume is created according to a storage statement of an initial container;

the acquisition and removal module is used for acquiring configuration information of the initial local storage volume and removing the initial local storage volume, wherein the configuration information is used for representing configuration parameters and a storage position of the initial local storage volume;

the creating and configuring module is used for creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host machine, wherein the target host machine is a host machine which does not have a fault;

and the mounting creating module is used for removing the initial container, creating a new target container and mounting the target local storage volume on the target container.

In a third aspect of the embodiments of the present application, a computer device is provided, where the computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when executed by the processor, the computer program implements the method for managing a storage system based on a container cluster according to the first aspect.

In a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided, where a computer program is stored, and when executed by a processor, the computer program implements the method for managing a storage system based on a container cluster according to the first aspect.

The beneficial effects of the embodiment of the application include:

according to the storage system management method based on the container cluster, the initial local storage volume is determined under the condition that the initial host machine fails, so that each initial local storage volume needing to be processed can be accurately determined, and the initial container needing to be processed can be conveniently and accurately determined due to the fact that the initial local storage volume is bound with the initial container.

The configuration information of the initial local storage volume is acquired, and the initial local storage volume is removed, so that the configuration parameters and the storage position of the initial local storage volume can be accurately acquired, and by removing the initial local storage volume, the binding relationship between the initial container and the initial local storage volume or the binding relationship between the initial host and the initial local storage volume can be released, and further the binding relationship between the initial container and the initial host can be released.

And creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host, wherein the configuration parameters of the target local storage volume are the same as those of the initial local storage volume since the target local storage volume is created and configured according to the configuration information, and after the target local storage volume is bound with the target host, the storage position of the target local storage volume on the target host is matched with that of the initial local storage volume on the initial host, so that a target local storage volume with the same configuration information as that of the initial local storage volume can be created, and the target local storage volume is bound with the target host which is not failed.

The initial container is removed, a new target container is created, the target local storage volume is mounted on the target container, the storage declaration of the target container is the same as that of the initial container, the initial local storage volume is created according to the storage declaration of the initial container, and the target local storage volume is created according to the configuration information of the initial local storage volume, so that the storage declarations of the target local storage volume and the target container are matched. Thus, after the target local storage volume is mounted on the target container, it can be ensured that the target container can be correctly matched with the target local storage volume, and it can also be ensured that the target container can store files or data stored in the initial container before the initial host is down.

In addition, after the target local storage volume is mounted on the target container, the target container is bound with the target local storage volume, and since the target local storage volume is bound with the target host, the binding between the target container and the target host can be achieved, that is, in case of a downtime of an initial host, the binding relationship between the target container, the target local storage volume and the target host which are re-established is the same as the binding relationship between the initial container, the initial local storage volume and the initial host, and since the data stored among the hosts in the storage system can be the same, after the target local storage volume is mounted on the target container, the target container can obtain the same data or files stored in the initial container from the target host.

Therefore, the effect of correctly restarting the container under the condition that the host is down and ensuring that the container can work normally can be achieved.

Drawings

To more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.

Fig. 1 is a schematic structural diagram of a container cluster-based storage system according to an embodiment of the present disclosure;

fig. 2 is a flowchart of a first container cluster-based storage system management method according to an embodiment of the present application;

fig. 3 is a flowchart of a second container cluster-based storage system management method according to an embodiment of the present application;

FIG. 4 is a flowchart of a third container cluster-based storage system management method according to an embodiment of the present application;

fig. 5 is a flowchart of a fourth container cluster-based storage system management method according to an embodiment of the present application;

fig. 6 is a flowchart of a fifth container cluster-based storage system management method according to an embodiment of the present application;

fig. 7 is a flowchart of a sixth method for managing a storage system based on container clusters according to an embodiment of the present application;

fig. 8 is a flowchart of a seventh container cluster-based storage system management method according to an embodiment of the present application;

fig. 9 is a flowchart of an eighth container cluster-based storage system management method according to an embodiment of the present application;

fig. 10 is a flowchart of a ninth container cluster-based storage system management method according to an embodiment of the present application;

fig. 11 is a flowchart of a tenth method for managing a storage system based on a container cluster according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a storage system management apparatus based on a container cluster according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.

Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the related art, generally, a container is bound to a persistent volume, a file or a directory in the container can be mapped onto a host through the bound persistent volume, when the container is reconstructed, a newly created container is still bound to a previously bound persistent volume, that is, the reconstructed container still mounts a previous persistent volume, and a file previously stored on the host can be continuously used, so that an application program can also retain data or a file before the container is reconstructed when calling the reconstructed container. After the persistent volume is bound to the container, the container must be dispatched to the host where the persistent volume is located when the container is rescheduled, that is, the container and the host have a binding relationship.

However, if a host is down, the persistent volume corresponding to the down host cannot work, and the container mounting the persistent volume cannot be restarted by scheduling the persistent volume to other available hosts, then the binding relationship between the container and the persistent volume on other available hosts cannot be established, and the binding relationship between the container and other available hosts cannot be established. Therefore, the scheme has the problem that the container cannot be restarted under the condition that the host machine is down, so that the container cannot work normally.

In addition, under the condition that a host is down, containers running on the host all have faults, if relevant technical personnel manually troubleshoot each container, the persistent volumes mounted on each container need to be found one by one and the actual mounting positions of the persistent volumes are confirmed, and then a plurality of new persistent volumes corresponding to the containers are created on other available hosts manually, so that a large amount of time is needed, and the container restarting efficiency is reduced.

Therefore, the embodiment of the present application provides a storage system management method based on a container cluster, where when an initial host fails, an initial local storage volume is determined, configuration information of the initial local storage volume is obtained, the initial local storage volume is removed, a target local storage volume is created and configured according to the configuration information, the target local storage volume is bound with a target host, the initial container is removed, a new target container is created, and the target local storage volume is mounted on the target container, so that a container can be correctly restarted under the condition that the host is down, and an effect that the container can normally work is ensured.

The embodiment of the present application describes a storage system management method applied to a storage system based on a container cluster as an example. It is not intended that the embodiments of the present application be applicable to storage system management in a container cluster-based storage system.

The method for managing a storage system based on a container cluster provided in the embodiment of the present application may be applied to any storage system based on a container cluster, and an application scenario of the method for managing a storage system based on a container cluster provided in the embodiment of the present application is described below.

In one possible approach, the storage system may include a controller, a plurality of hosts, and a plurality of container groups. Each container group may include at least one container therein, and each container may include at least one file or data therein.

All host machines can communicate with each other and realize functions of data transmission, data synchronization and the like.

Each host may bind multiple storage volumes simultaneously, and each storage volume may be a persistent storage volume created locally on the storage system.

In addition, each storage volume may be a virtual storage area created or opened up on a storage device on each host.

Each container can be bound to one host respectively, so that files in each container are stored in a storage volume or a disk of the host bound to each container.

Specifically, each container may be bound by the storage volume bound to each host to achieve the purpose of binding each container to a host.

Each host can represent a node in the storage system, and each container can be bound with the host by representing that each container is bound with the node in the storage system.

The controller may be configured to determine, modify, remove, and/or store binding relationships between containers and hosts, create, configure, or remove storage volumes in hosts, and remove or restart containers. In addition, the controller can also be used for realizing functions of creating storage statements of containers, monitoring hosts and the like.

In addition, the files or data in each container may be called by an external program, or may also be modified or deleted by the external program.

The external program may have a function of calling each container, a function of reading and writing a file or data in each container, or any other function of adjusting each container, and may be, for example, a kubernets program. The embodiment of the present application does not limit this.

Fig. 1 is a schematic structural diagram of a storage system based on a container cluster according to an embodiment of the present disclosure, and specifically, referring to fig. 1, fig. 1 illustrates a storage system XT, and the storage system XT includes a controller K, a host S1, a host S2, a container group Z1, and a container group Z2 as an example.

The storage system XT may be a storage system based on Remote Dictionary service (Redis), an Etcd cluster, a Cassandra-based storage system, any storage system with multiple copies, or a storage system in which data synchronization between nodes may be performed, which is not limited in the embodiments of the present application.

The host machine S1 may be connected to the host machine S2 to implement functions such as data synchronization and data exchange between the host machine S1 and the host machine S2.

In addition, the files and data stored in the hosts S1 and S2 may be the same, so that when the files or data in the hosts S1 are lost or damaged, the files or data can be synchronized with the hosts S2 to obtain complete files or data.

The container group Z1 may be connected to the host S1 to store the file or data in the container group Z1 in the storage volume of the host S1. The container group Z2 may be connected to the host S2 to store the files or data in the container group Z2 in the storage volume of the host S2.

The host machine S1, the host machine S2, the container group Z1 and the container group Z2 are respectively connected with the controller K.

Optionally, the container group Z1 may include a container R1 and a container R2, the container group Z2 may include a container R3 and a container R4, and in addition, the container group Z1 and/or the container group Z2 may further include one, three, or more than three containers, which is not limited in this application.

It should be noted that the storage system XT shown in fig. 1 is only an example, and does not represent that there are only two hosts in the storage system XT, or that each container, each host, and the controller K in the storage system XT can only be connected and communicated in the manner shown in fig. 1, which is not limited in this embodiment of the present invention.

The following explains the container cluster-based storage system management method provided in the embodiment of the present application in detail.

Fig. 2 is a flowchart of a method for managing a storage system based on a container cluster according to the present application, where the method may be applied to a computer device, and the computer device may be a controller in the storage system or any electronic device connected to the storage system and having a processing function. Referring to fig. 2, an embodiment of the present application provides a storage system management method based on a container cluster, including:

step 1001: when the initial host fails, the initial local storage volume is determined.

Optionally, the initial local storage volume is a storage volume bound to the initial host.

The initial host may be any of the hosts in the storage system described above.

The initial local storage volume may refer to any storage volume in the storage system that is bound to the initial host, which is not limited in this embodiment of the present application.

Optionally, the initial local storage volume is created according to a storage declaration of the initial container. That is, there is a binding relationship between the initial local storage volume and the initial container.

The storage declaration may refer to a place-occupying instruction issued by the computer device to the memory to indicate information such as the size of the memory to be allocated when the initial local storage volume is created and the memory space needs to be called.

The storage volume may refer to a virtual storage space in the host, may indicate a directory in a local file system of the host, and may establish a binding relationship between the directory in the local file system of the host and the directory on the file system of each container.

It is noted that, since the initial local storage volume is created according to the storage declaration of the initial container, the initial local storage volume is bound to the storage declaration of the initial container, so that the initial local storage volume is bound to the initial container. Moreover, when the initial host fails, all the storage volumes on the initial host fail, and the initial local storage volume fails because the initial local storage volume is a storage volume bound to the initial host. Therefore, each initial local storage volume needing to be processed can be accurately determined, and because the initial local storage volume is bound with the initial container, the initial container needing to be processed is conveniently and accurately determined, and subsequent operations are conveniently executed.

Step 1002: and acquiring configuration information of the initial local storage volume, and removing the initial local storage volume.

Optionally, the configuration information is used to characterize configuration parameters and storage locations of the initial local storage volume.

The configuration parameters may refer to parameters set when the initial local storage volume is created or provisioned, such as storage capacity, access patterns, storage type, etc. of the initial local storage volume. The storage location may represent a real working directory or storage path of the initial local storage volume on the initial host, which is not limited in this embodiment of the present application.

In addition, the configuration information may be stored in each host in the storage system, may be stored in a controller of the storage system, or may be stored in any other storage device that can communicate with the computer device.

Optionally, the operation of removing the initial local storage volume may refer to deleting the initial local storage volume from the storage system, or may refer to releasing a binding relationship between the initial local storage volume and the initial host, or may release a binding relationship between the initial local storage volume and the initial container or a storage statement of the initial local storage volume and the initial container, which is not limited in this embodiment of the present application.

It is noted that if terminators (finizers) are also deployed in the storage system, the terminators need to be removed before the initial local storage volume is removed to prevent the terminators from blocking the removal of the initial local storage volume.

It is worth noting that, the configuration parameters and the storage position of the initial local storage volume can be accurately obtained, and subsequent operations can be conveniently carried out according to the configuration parameters and the storage position of the initial local storage volume. After the initial local storage volume is removed, the binding relationship between the initial container and the initial local storage volume or the binding relationship between the initial host and the initial local storage volume can be released, so that the binding relationship between the initial container and the initial host can be released, and subsequent operations can be conveniently executed.

Step 1003: and creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host.

Alternatively, the target local storage volume may refer to a local persistent storage volume that is newly created or developed in the storage system.

Optionally, the target host is a non-failed host. Specifically, the target host may be any host that does not fail in the storage system, or may be any host that does not fail in the storage system and is matched with the target local storage volume, which is not limited in this embodiment of the present application.

Specifically, the target local storage volume may be created and configured according to the configuration parameters and the storage location of the initial local storage volume.

It should be noted that, since the target local storage volume is created and configured according to the configuration information, the configuration parameters of the target local storage volume are the same as those of the initial local storage volume, and after the target local storage volume is bound to the target host, the storage location of the target local storage volume on the target host is matched with the storage location of the initial local storage volume on the initial host, so that a target local storage volume having the same configuration information as that of the initial local storage volume can be created and bound to the target host without failure.

Step 1004: the initial container is removed, a new target container is created, and the target local storage volume is mounted on the target container.

Alternatively, the target container may be a new container that is redrawn in the storage system, and the storage declaration of the target container is the same as the storage declaration of the original container.

It should be noted that, since the storage declaration of the target container is the same as that of the initial container, the initial local storage volume is created according to the storage declaration of the initial container, and the target local storage volume is created according to the configuration information of the initial local storage volume, the storage declarations of the target container and the target local storage volume are matched. In this way, after the target local storage volume is mounted on the target container, it is ensured that the target container can be correctly matched with the target local storage volume, and in addition, it is ensured that the target container can store the files or data stored in the initial container before the initial host machine is down.

In the embodiment of the present application, the initial local storage volume is determined when the initial host fails, so that each initial local storage volume that needs to be processed can be accurately determined, and the initial local storage volume is bound to the initial container, which is convenient for accurately determining the initial container that needs to be processed.

The configuration information of the initial local storage volume is obtained, and the initial local storage volume is removed, so that the configuration parameters and the storage position of the initial local storage volume can be accurately obtained, and by removing the initial local storage volume, the binding relationship between the initial container and the initial local storage volume or the binding relationship between the initial host and the initial local storage volume can be released, and further the binding relationship between the initial container and the initial host can be released.

Creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host, wherein since the target local storage volume is created and configured according to the configuration information, the configuration parameters of the target local storage volume are the same as those of the initial local storage volume, and after the target local storage volume is bound with the target host, the storage location of the target local storage volume on the target host is matched with that of the initial local storage volume on the initial host, so that a target local storage volume with the same configuration information as that of the initial local storage volume can be opened, and the target local storage volume is bound on the target host which is not failed.

The initial container is removed, a new target container is created, the target local storage volume is mounted on the target container, the storage declaration of the target container is the same as that of the initial container, the initial local storage volume is created according to the storage declaration of the initial container, and the target local storage volume is created according to the configuration information of the initial local storage volume, so that the storage declarations of the target local storage volume and the target container are matched. Thus, after the target local storage volume is mounted on the target container, it can be ensured that the target container can be correctly matched with the target local storage volume, and it can also be ensured that the target container can store files or data stored in the initial container before the initial host is down.

In addition, after the target local storage volume is mounted on the target container, the target container is bound with the target local storage volume, and since the target local storage volume is bound with the target host, the binding between the target container and the target host can be achieved, that is, in case of a downtime of an initial host, the binding relationship between the target container, the target local storage volume and the target host which are re-established is the same as the binding relationship between the initial container, the initial local storage volume and the initial host, and since the data stored among the hosts in the storage system can be the same, after the target local storage volume is mounted on the target container, the target container can obtain the same data or files stored in the initial container from the target host.

Therefore, the effect of correctly restarting the container under the condition that the host is down and ensuring that the container can work normally can be achieved.

In order to accurately determine an initial local storage volume that needs to be processed, embodiments of the present application provide a possible implementation manner, and the specific step of determining the initial local storage volume may be:

and determining the initial local storage volume bound with the initial host according to the initial mapping relation of each local storage volume.

Optionally, each local storage volume comprises the initial local storage volume.

The initial mapping relationship is used for indicating the binding relationship between the local storage volume and each host.

For example, a corresponding tag may be configured in each local storage volume to characterize the initial mapping relationship, or the tag characterizing the initial mapping relationship may be stored in each host, a controller, or any other storage device that can communicate with the computer device in the storage system, which is not limited in this embodiment of the present application.

For example, if a local storage volume is bound to host S1 in the storage system XT, and the name or code of host S1 is node1, then the local storage volume may be configured with a label with the name or code of host S1, for example, the label may be "orcast.

The mark may be any other mark, and the embodiment of the present application is not limited to this.

Therefore, the initial local storage volume bound with the initial host and needing to be processed can be accurately determined, and the reliability of the storage system management method based on the container cluster can be improved.

In a possible implementation manner, the configuration parameters may specifically include a storage type, a storage capacity, and an access pattern of the initial local storage volume, and the storage location may specifically include an initial working directory of the initial local storage volume on the initial host, so that the target local storage volume may be created and configured according to the storage type, the storage capacity, the access pattern of the initial local storage volume and the initial working directory of the initial local storage volume on the initial host.

Referring specifically to fig. 3, creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host includes:

step 1005: the target local storage volume is created according to the storage type, storage capacity, and/or access pattern of the initial local storage volume.

Optionally, the storage type of the initial local storage volume may be a storage class predefined by a related technician, and the storage class may specifically refer to an interface for each container set by the related technician to apply for creating a storage volume in the storage system. In addition, the relevant technician can also set a corresponding name for the storage class.

For example, the storage type of the initial local storage volume may include an emptyDir type, a hostPath type, an nfs type, a glusterfs type, a cephfs type, a ceph rbd type, and any other possible type, which may be specifically defined by related technical personnel according to actual needs, and is not limited in this embodiment of the present application.

Optionally, the storage capacity of the initial local storage volume may be used to indicate the size of the storage space of the initial local storage volume, and the access mode of the initial local storage volume may include a readable mode, a writable mode, a read-write mode, and the like.

In addition, the configuration parameters may further include a name and an allocation manner of the initial local storage volume, where the allocation manner includes a single continuous allocation manner, a fixed partition allocation manner, a dynamic relocation partition allocation manner, and any other possible allocation manner, and this is not limited in this embodiment of the present application.

Then, the target local storage volume may be created according to the name and the allocation manner of the initial local storage volume.

Therefore, the created target local storage volume and the initial local storage volume can be ensured to have the same configuration parameters, so that the target local storage volume and the target host can be conveniently bound, and the binding relationship between the target local storage volume and the target container can be reconstructed on the target host.

Step 1006: and configuring a target working directory on the target host machine for the target local storage volume according to the initial working directory.

Optionally, the initial working directory refers to a directory in which the file system of the initial local storage volume is located in the initial local storage volume, and in a case that the initial local storage volume provides a service or work, the initial working directory and subdirectories of the initial working directory may be operated.

Then, the target working directory refers to a directory in which the target local storage volume file system is located in the target local storage volume, and when the target local storage volume provides services or works, the target working directory and the subdirectories of the target working directory may be operated.

In this way, the homogeneity of the target local storage volume and the initial local storage volume can be further ensured, so that the target local storage volume is subsequently bound with the target host, and the binding relationship between the target local storage volume and the target container is reconstructed on the target host.

Step 1007: and binding the target local storage volume with the target host machine, and configuring a target mapping relation matched with the target host machine for the target local storage volume.

Optionally, the target mapping relationship may be used to indicate a binding relationship with the target local storage volume and the target host.

Illustratively, a corresponding tag may be configured in the target local storage volume to characterize the table mapping relationship. For example, if the target host is the host S2 in the storage system XT and the name or code of the host S2 is node2, the target local storage volume may be configured with a label with the name or code of the host S2, for example, the label may be "orcast.

The mark representing the target mapping relationship may be stored in each host, a controller, or any other storage device that can communicate with the computer device in the storage system, which is not limited in this embodiment of the present application.

In this way, a target local storage volume that is the same as the configuration information of the original local storage volume can be created and bound to the target host that has not failed. And after the target local storage volume is configured with the target mapping relation matched with the target host, the target local storage volume can be determined according to the target mapping relation under the condition that the target host is down, so that the reliability of the storage system management method based on the container cluster can be further improved.

In one possible implementation, referring to fig. 4, configuring a target working directory on the target host for the target local storage volume according to the initial working directory includes:

step 1008: and reading the initial working catalog, and creating a target working catalog identical to the initial working catalog on the target host.

Step 1009: the target working directory is configured to the target local storage volume.

In this way, the homogeneity of the target local storage volume and the initial local storage volume can be further ensured, so that the target local storage volume is subsequently bound with the target host, and the binding relationship between the target local storage volume and the target container is reconstructed on the target host.

In a possible implementation manner, the configuration information may further include node affinity information of the initial local storage volume, where the node affinity information may be used to determine a host that matches the initial local storage volume, and then, according to the node affinity information, a target host may be selected from a plurality of non-failed hosts in the storage system.

Referring to fig. 5, according to the initial working directory, before configuring the target working directory on the target host for the target local storage volume, the method further includes:

step 1010: and determining the host machine which is matched with the target local storage volume and does not have the fault according to the node affinity information, and taking the host machine which is matched with the target local storage volume and does not have the fault as the target host machine.

Optionally, the node affinity information may be a preference or a hard requirement of the target local storage volume or the initial container, and a specific type of node that is more matched with the target local storage volume or the initial container may be determined by the node affinity information.

For example, the node affinity information may be used to indicate the target local storage volume or the initial container preference or the characteristics of the hosts that need to be selected.

In the storage system, two hosts which do not have faults exist, wherein one host stores a large amount of text data, the other host stores a large amount of image data, and the node affinity information can be used for indicating that the target local storage volume or the initial container needs to select a host which can store file data types, so that the host which stores a large amount of text data can be determined to be matched with the target local storage volume according to the node affinity information, and the host which stores a large amount of text data can be used as the target host.

For another example, in the storage system, there are three non-failed hosts, where 20 containers are bound to the first host, 100 containers are bound to the second host, and 50 containers are bound to the third host, and the node affinity information may be used to indicate that the target local storage volume or the initial container needs to select the host with the fewest current bound containers, so that the first host may be used as the target host according to the node affinity information.

Therefore, the determined target host machine is the host machine which is matched with the target local storage volume and does not have a fault, the target host machine is determined according to the node affinity information, the target local storage volume can be bound with the specific host machine, and then the target container can be subsequently bound with the specific host machine.

In order to accurately determine whether the initial host fails, the present application further provides a possible implementation manner, referring to fig. 6, when the initial host fails, before determining the initial local storage volume, the method further includes:

step 1011: and monitoring the working state of the initial host machine in real time.

The operating state may include a normal state or a fault state.

Step 1012: and determining whether the initial host machine fails according to the working state of the initial host machine.

Illustratively, with continued reference to fig. 7 on the basis of fig. 6, determining whether the initial host fails according to the operating status of the initial host includes:

step 1013: and determining the times of the initial host machine entering the fault state within a preset time length.

Optionally, the starting time of the preset duration is a time when the working state of the initial host is monitored to be changed, and the time when the working state of the initial host is changed may specifically be a time when the working state of the initial host is changed from a normal state to a fault state.

The time length of the preset duration can be adjusted according to actual needs, and the embodiment of the application does not limit the time length.

Step 1014: and determining that the initial host machine fails according to the frequency of the initial host machine entering the failure state.

Specifically, it may be determined that the initial host fails when the number of times that the initial host enters the failure state is greater than or equal to a preset number threshold.

The preset number threshold may be 1, may also be 2, and may also be any other positive integer, and the preset number threshold may be adjusted according to actual needs, which is not limited in this application embodiment.

In this way, the flexibility of the container cluster-based storage system management method can be improved.

Illustratively, with continued reference to fig. 8 on the basis of fig. 6, determining whether the initial host fails according to the operating status includes:

step 1015: and determining the working states of the initial host machine at the first time and the second time.

Alternatively, the first time may refer to a time when the operating state of the initial host machine is changed from a normal state to a fault state.

The second time is arranged after the first time, and the time length between the second time and the first time can be adjusted according to actual needs.

Step 1016: and if the working states of the initial host machine at the first moment and the second moment are fault states, determining that the initial host machine is in fault.

In addition, the length of time between the first time and the second time may be defined as a fault tolerance time.

It should be noted that, since each host in the storage system may automatically recover to the normal state after a failure or downtime occurs, that is, after each host enters the failure state, each host may be provided with a reasonable fault tolerance time for attempting to automatically recover to the normal state. However, if the working states of the initial host at the first time and the second time are both failure states, it means that the initial host does not recover to a normal state after the fault tolerance time has elapsed, and it is necessary to confirm that the initial host fails.

Therefore, the flexibility of determining whether the initial host computer fails can be improved, and the flexibility of the storage system management method based on the container cluster can be further improved.

In one possible implementation manner, referring to fig. 9, when the initial host fails and before determining the initial local storage volume, the method further includes:

step 1017: the initial local storage volume is created according to the storage declaration of the initial container.

Optionally, the storage declaration may be used to indicate configuration parameters of the initial local storage volume, and may also include the name of the storage class predefined by the related technical personnel.

It is noted that, since the initial local storage volume is created according to the storage declaration of the initial container, there is a binding relationship between the initial local storage volume and the initial container, that is, the initial local storage volume can be mounted on the initial container.

Step 1018: determining the initial host machine matched with the initial local storage volume, binding the initial local storage volume with the initial host machine, and configuring an initial working catalog of the initial local storage volume on the initial host machine for the initial local storage volume.

It should be noted that, since the initial local storage volume is bound to the initial host and the initial local storage volume can be mounted on the initial container, the purpose of binding the initial container to the initial host can be achieved, so that the initial container can be ensured to work normally, and the reliability and stability of the container cluster-based storage system management method can be further improved.

In one possible implementation, with reference to fig. 10 in continuation from fig. 9, creating the initial local storage volume according to the storage declaration of the initial container includes:

step 1019: and generating the storage declaration of the initial container according to the required storage capacity and/or the access mode of the initial container.

The storage capacity, the access mode and/or the storage type required by the initial container may be determined by the computer device according to the state or the attribute of the initial container, or may be set by a related person according to actual needs, which is not limited in this embodiment of the present application.

Step 1020: and writing the storage type of the local storage volume needing to be mounted in the initial container into the storage declaration of the initial container.

The storage type of the local storage volume that the initial container needs to mount may refer to the storage class defined by the related art person in advance.

Step 1021: the initial local storage volume is created according to the storage declaration of the initial container.

Notably, since the storage declaration for the initial container includes the storage capacity and/or access pattern required by the initial container, it is ensured that the initial local storage volume created from the storage declaration may store all of the data or files that the initial container needs to store. In addition, since the storage declaration of the initial container includes the storage type of the local storage volume that the initial container needs to mount, it is ensured that the initial local storage volume created according to the storage declaration can be successfully mounted on the initial container.

In one possible implementation, referring to fig. 11, determining the initial host in the storage system that matches the initial local storage volume, and binding the initial local storage volume with the initial host includes:

step 1022: and determining the initial host matched with the initial local storage volume through the node affinity information of the initial local storage volume.

Step 1023: and binding the initial local storage volume with the initial host, and configuring an initial mapping relation matched with the initial host for the initial local storage volume.

Therefore, the initial local storage volume can be bound with a specific host, and then the initial container can be bound with the specific host, so that the flexibility of the storage system management method based on the container cluster can be improved.

It should be noted that, generally, in the storage system, there may be multiple containers or multiple storage volumes that have a binding relationship with the same host, and then, in a case that the host is down, the storage system management method based on a container cluster provided according to the foregoing embodiments needs to recreate the target containers and the target local storage volumes corresponding to the containers on other non-failed target hosts and establish the binding relationships between the corresponding target containers, the target local storage volumes, and other non-failed target hosts, so as to ensure that, in a case that one host is down or fails, all containers bound to the host in the storage system can be restarted and run normally on other non-failed target hosts.

The following describes a device, an apparatus, and a computer-readable storage medium for executing the method for managing a storage system based on a container cluster provided in the present application, and specific implementation processes and technical effects thereof are referred to above, and will not be described again below.

Fig. 12 is a schematic structural diagram of a storage system management apparatus based on container clusters according to an embodiment of the present application, and referring to fig. 12, the apparatus includes:

a determining module 201, configured to determine an initial local storage volume when the initial host fails; the initial local storage volume is a storage volume bound with the initial host, and the initial local storage volume is created according to the storage statement of the initial container;

an obtaining and removing module 202, configured to obtain configuration information of the initial local storage volume, where the configuration information is used to characterize configuration parameters and a storage location of the initial local storage volume, and remove the initial local storage volume;

a creating and configuring module 203, configured to create and configure a target local storage volume according to the configuration information, and bind the target local storage volume with a target host, where the target host is a host that has not failed;

a create mount module 204 to remove the initial container, create a new target container, and mount the target local storage volume on the target container.

The above-mentioned apparatus is used for executing the method provided by the foregoing embodiment, and the implementation principle and technical effect are similar, which are not described herein again.

The above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors, or one or more Field Programmable Gate Arrays (FPGAs), etc. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. As another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

Fig. 13 is a schematic structural diagram of a computer device according to an embodiment of the present application. Referring to fig. 13, the computer apparatus includes: a memory 301 and a processor 302, wherein the memory 301 stores a computer program operable on the processor 302, and the processor 302 executes the computer program to implement the steps of any of the above-mentioned method embodiments.

The embodiments of the present application also provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

Optionally, the present application further provides a program product, such as a computer-readable storage medium, including a program, which when executed by a processor, is configured to perform any of the above embodiments of the container cluster-based storage system management method.

In the several embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a portable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall cover the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (14)

1. A method for managing a storage system based on a container cluster, the method comprising:

when an initial host machine fails, determining an initial local storage volume, wherein the initial local storage volume is a storage volume bound with the initial host machine and is created according to a storage statement of an initial container;

acquiring configuration information of the initial local storage volume, and removing the initial local storage volume, wherein the configuration information is used for representing configuration parameters and a storage position of the initial local storage volume;

creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host machine, wherein the target host machine is a host machine which does not have a fault;

and removing the initial container, creating a new target container, and mounting the target local storage volume on the target container.

2. The container cluster-based storage system management method of claim 1, wherein the step of determining an initial local storage volume comprises:

determining an initial local storage volume bound with the initial host according to the initial mapping relation of each local storage volume;

each local storage volume comprises the initial local storage volume, and the initial mapping relation is used for indicating the binding relation between the local storage volume and each host.

3. The container cluster-based storage system management method of claim 1, wherein the configuration parameters include a storage type, a storage capacity, an access pattern of the initial local storage volume, and the storage location comprises an initial working directory of the initial local storage volume on the initial host;

the creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host, including:

creating the target local storage volume according to the storage type, the storage capacity and/or the access mode of the initial local storage volume;

configuring a target working directory on the target host machine for the target local storage volume according to the initial working directory;

and binding the target local storage volume with the target host machine, and configuring a target mapping relation matched with the target host machine for the target local storage volume.

4. The method for container cluster-based storage system management of claim 3, wherein said configuring a target working directory on said target host for said target local storage volume according to said initial working directory comprises:

reading the initial working catalog, and creating a target working catalog which is the same as the initial working catalog on the target host machine;

and configuring the target working catalog to the target local storage volume.

5. The container cluster-based storage system management method of claim 3, further comprising node affinity information of the initial local storage volume in the configuration information, the node affinity information being used to determine a host that matches the initial local storage volume;

before configuring the target working directory on the target host machine for the target local storage volume according to the initial working directory, the method further includes:

and determining the host machine which is matched with the target local storage volume and does not have the fault according to the node affinity information, and taking the host machine which is matched with the target local storage volume and does not have the fault as the target host machine.

6. The method for container cluster-based storage system management according to any of claims 1-5, wherein before determining the initial local storage volume when the initial host fails, the method further comprises:

monitoring the working state of the initial host machine in real time;

and determining whether the initial host machine fails according to the working state of the initial host machine.

7. The method of container cluster-based storage system management of claim 6, wherein said determining whether the initial host fails based on the operational status of the initial host comprises:

determining the number of times that the initial host machine enters a fault state within a preset time length, wherein the starting time of the preset time length is the time when the working state of the initial host machine is monitored to change;

and determining that the initial host machine fails according to the frequency of the initial host machine entering the fault state.

8. The container cluster-based storage system management method of claim 6, wherein said determining whether said initial host fails based on said operational status comprises:

determining the working states of the initial host machine at a first moment and a second moment;

and if the working states of the initial host machine at the first moment and the second moment are both fault states, determining that the initial host machine has a fault.

9. The method for container cluster-based storage system management according to any of claims 1-5, wherein before determining the initial local storage volume when the initial host fails, the method further comprises:

creating the initial local storage volume according to a storage statement of the initial container, wherein the storage statement is used for indicating configuration parameters of the initial local storage volume;

determining the initial host machine matched with the initial local storage volume, binding the initial local storage volume with the initial host machine, and configuring an initial working catalog of the initial local storage volume on the initial host machine.

10. The method of container cluster-based storage system management as claimed in claim 9, wherein said creating the initial local storage volume according to the storage declaration of the initial container comprises:

generating a storage statement of the initial container according to a storage capacity access mode required by the initial container;

writing the storage type of the local storage volume needing to be mounted in the initial container into a storage statement of the initial container;

and creating the initial local storage volume according to the storage statement of the initial container.

11. The method of container cluster-based storage system management of claim 9, wherein said determining the initial host in the storage system that matches the initial local storage volume, binding the initial local storage volume with the initial host comprises:

determining the initial host machine matched with the initial local storage volume according to the node affinity information of the initial local storage volume;

and binding the initial local storage volume with the initial host machine, and configuring an initial mapping relation matched with the initial host machine for the initial local storage volume.

12. An apparatus for managing a storage system based on a container cluster, the apparatus comprising:

the determining module is used for determining an initial local storage volume when the initial host machine fails; the initial local storage volume is a storage volume bound with the initial host, and the initial local storage volume is created according to a storage statement of an initial container;

the acquisition and removal module is used for acquiring configuration information of the initial local storage volume and removing the initial local storage volume, wherein the configuration information is used for representing configuration parameters and a storage position of the initial local storage volume;

the creating and configuring module is used for creating and configuring a target local storage volume according to the configuration information, and binding the target local storage volume with a target host machine, wherein the target host machine is a host machine which does not have a fault;

and the mounting creating module is used for removing the initial container, creating a new target container and mounting the target local storage volume on the target container.

13. A computer device, comprising: memory in which a computer program is stored which is executable on the processor, and a processor which, when executing the computer program, carries out the steps of the method according to any one of the preceding claims 1 to 11.

14. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method of one of claims 1 to 11.

Images