WO2024174717A1

WO2024174717A1 - Dynamic storage allocation method and apparatus, electronic device, and storage medium

Info

Publication number: WO2024174717A1
Application number: PCT/CN2023/141624
Authority: WO
Inventors: 赵波; 魏健
Original assignee: 苏州元脑智能科技有限公司
Priority date: 2023-02-24
Filing date: 2023-12-25
Publication date: 2024-08-29
Also published as: CN116088768A; CN116088768B

Abstract

Embodiments of the present application relate to the technical field of computers, and provide a dynamic storage allocation method and apparatus, an electronic device, and a non-volatile readable storage medium, applicable to a container cluster management system. The method comprises: acquiring a target storage type; according to the target storage type, generating a storage class template by using a template adapter, so as to create a storage class on the basis of the storage class template; acquiring a persistent volume claim request created by a user; provisioning a new persistent volume in the created storage class according to the persistent volume claim request, creating the new persistent volume, and binding the new persistent volume to the persistent volume claim request to allocate the persistent volume for the persistent volume claim request. The present application uses a template adapter to generate a storage class template so as to create a storage class, so that a user can more accurately define a required persistent volume, and the problems of persistent volume creation errors and application startup failure caused by parameter configuration errors of different storage types and the problems of application reconstruction failure due to loss of important data generated by an application and caused by misdeletion of data are avoided.

Description

Dynamic storage allocation method, device, electronic device and storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to a Chinese patent application filed with the China Patent Office on February 24, 2023, with application number 202310165351.7 and application name “Dynamic storage allocation method, device, electronic device and storage medium”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of computer technology, and in particular to a dynamic storage allocation method, a dynamic storage allocation device, an electronic device, and a computer non-volatile readable storage medium.

Background Art

Kubernetes, also known as K8s, is an open source system that can be used to automate the deployment, expansion and management of containerized applications. It can provide a solution for dynamic storage allocation (Dynamic Provisioning) as opposed to static storage allocation. When resource provisioning uses dynamic mode, the Kubernetes system can automatically create a PV (Persistent Volume) and complete the binding with PVC after finding a suitable Storage Class for PVC (Persistent Volume Claim).

Kubernetes can support multiple PV types, each with its own characteristics, and needs to be set according to their respective parameters when in use. Since Kubernetes supports many storage types and the parameters provided by different storage types vary greatly, it is easy to cause the corresponding StorageClass parameter configurations to be different, and some parameters are not displayed, which makes the administrator's configuration work cumbersome. Often, due to different storage type parameters, configuration errors occur, resulting in PV creation errors and application startup failures until the administrator makes the correct changes.

Summary of the invention

In view of the above problems, embodiments of the present application are proposed to provide a dynamic storage allocation method, a dynamic storage allocation device, an electronic device and a computer non-volatile readable storage medium that overcome the above problems or at least partially solve the above problems.

In order to solve the above problems, an embodiment of the present application discloses a dynamic storage allocation method, which is applied to a container cluster management system and includes:

Get the target storage type;

According to the target storage type, a storage class template is generated by using a template adapter to create a storage class based on the storage class template;

Get the persistent volume claim request created by the user to apply for storage resources;

Based on the persistent volume claim request, a new persistent volume is provisioned in the created storage class, and a new persistent volume is created and bound to the persistent volume claim request to allocate a persistent volume for the persistent volume claim request.

In some embodiments, before obtaining the target storage type, the method further includes:

Determine whether the persistent volume provisioner has been deployed;

If the persistent volume provisioner is not deployed, the not deployed message is returned to allow the cluster administrator to deploy the persistent volume provisioner.

In some embodiments, when deploying the persistent volume provisioner, the method further comprises:

The template adapter is triggered to obtain storage definition parameters corresponding to each storage type, generate template configuration information corresponding to each storage type and save it in the database.

In some embodiments, the trigger template adapter obtains storage definition parameters corresponding to each storage type, including:

Trigger the template adapter to obtain storage definition parameters corresponding to each storage type provided by the persistent volume provisioner.

In some embodiments, the template configuration information includes template generation rules and template parameter recommendations, and the template configuration information corresponding to each storage type is generated and saved in a database, including:

Generate template generation rules and template parameter recommendations corresponding to each storage type and save them in the database.

In some embodiments, obtaining the target storage type includes:

At least one target storage type corresponding to at least one target storage provision object is obtained, where the storage provision object is an object used to provide persistent volume resources.

In some embodiments, according to the target storage type, a template adapter is used to generate a storage class template, including:

A template adapter is used to query the database for template generation rules and template parameter recommendations corresponding to the target storage type, and a storage class template is generated according to the template generation rules and template parameter recommendations corresponding to the target storage type.

In some embodiments, a template adapter is used to query a database for template generation rules and template parameter recommendations corresponding to the target storage type, and a storage class template is generated according to the template generation rules and template parameter recommendations corresponding to the target storage type, including:

The target storage type input by the cluster administrator is sent to the template adapter, so that after receiving the target storage type, the template adapter queries the database for the template generation rules and template parameter recommendations corresponding to the target storage type, and generates a storage class template based on the template generation rules and template parameter recommendations corresponding to the target storage type.

In some embodiments, before creating a storage class based on the storage class template, the method further includes:

In response to the template configuration information modification instruction input by the user, the template generation rules and template parameter recommendations corresponding to the target storage type are modified.

In some embodiments, creating a storage class based on a storage class template includes:

Based on the storage class template, at least one storage class is created that corresponds one-to-one to at least one target storage type.

In some embodiments, creating a storage class based on a storage class template further includes:

Sets a default storage class that is applied to persistent volume claim requests that do not specify a storage class.

In some embodiments, the storage class template includes at least one of a storage provision object, a resource recovery policy, whether storage expansion is allowed, a mount option, a storage binding mode, and a storage parameter. Creating a storage class based on the storage class template includes:

A storage class is created based on at least one of a storage provision object, a resource recovery policy, whether storage expansion is allowed, a mount option, a storage binding mode, and a storage parameter.

In some embodiments, obtaining a persistent volume claim request created by a user for applying for storage resources includes:

Gets a user-created persistent volume claim request that references a target storage class in at least one storage class.

In some embodiments, provisioning a new persistent volume in the created storage class in accordance with the persistent volume claim request includes:

Find the target storage class;

Use the persistent volume provisioner to provision a new persistent volume in the target storage class based on the persistent volume claim request.

In some embodiments, the persistent volume claim request includes access mode information and storage size information, and a persistent volume provisioning procedure is used to provision a new persistent volume in a target storage class according to the persistent volume claim request, including:

A new persistent volume is provisioned in the target storage class using the persistent volume provisioner based on the access mode information, storage size information, and storage definition parameters corresponding to the target storage type.

In some embodiments, creating a new persistent volume, and binding the new persistent volume to the persistent volume claim request, includes:

Get the real storage specified by the persistent volume provisioner;

Create a new persistent volume in the real storage and bind the new persistent volume to the persistent volume claim request.

In some embodiments, the method further comprises:

Creates a data structure containing the persistent volume requested by referencing the persistent volume claim by name.

The embodiment of the present application also discloses a dynamic storage allocation device, which is applied to a container cluster management system, and includes:

An acquisition module is used to obtain the target storage type;

A template generation module, used to generate a storage class template using a template adapter according to a target storage type, so as to create a storage class based on the storage class template; the storage class template includes storage definition parameters corresponding to the target storage type;

The request acquisition module is used to obtain the persistent volume claim request created by the user to apply for storage resources;

An allocation module is used to provision a new persistent volume in the created storage class according to the storage definition parameters corresponding to the persistent volume claim request and the target storage type, create a new persistent volume, bind the new persistent volume to the persistent volume claim request, and allocate the persistent volume for the persistent volume claim request.

A determination module, used to determine whether a persistent volume provisioning program has been deployed;

The return module is used to return the undeployment information if the persistent volume provisioner is not deployed so that the cluster administrator can deploy the persistent volume provisioner.

In some embodiments, when deploying the persistent volume provisioning procedure, the apparatus further comprises:

The trigger module is used to trigger the template adapter to obtain the storage definition parameters corresponding to each storage type, generate the template configuration information corresponding to each storage type and save it in the database.

In some embodiments, the trigger module includes:

The definition parameter acquisition submodule is used to trigger the template adapter to obtain the storage definition parameters corresponding to each storage type provided by the persistent volume provisioning program.

In some embodiments, the template configuration information includes template generation rules and template parameter recommendations, and the trigger module includes:

The template parameter generation submodule is used to generate template generation rules and template parameter recommendations corresponding to each storage type and save them in the database.

In some embodiments, the acquisition module includes:

The storage type acquisition submodule is used to obtain at least one target storage type corresponding to at least one target storage provision object, where the storage provision object is an object used to provide persistent volume resources.

In some embodiments, the template generation module includes:

The storage class template generation submodule is used to use the template adapter to query the database for template generation rules and template parameter recommendations corresponding to the target storage type, and generate a storage class template based on the template generation rules and template parameter recommendations corresponding to the target storage type.

In some embodiments, the storage class template generation submodule includes:

The target storage type sending unit is used to send the target storage type input by the cluster administrator to the template adapter, so that after receiving the target storage type, the template adapter queries the database for template generation rules and template parameter recommendations corresponding to the target storage type, and generates a storage class template based on the template generation rules and template parameter recommendations corresponding to the target storage type.

The instruction response module is used to modify the template generation rules and template parameter recommendations corresponding to the target storage type in response to the template configuration information modification instruction input by the user.

In some embodiments, the template generation module includes:

A creation submodule is used to create at least one storage class corresponding to at least one target storage type based on the storage class template.

In some embodiments, the template generation module further includes:

The default storage class setting submodule is used to set a default storage class, which is applied to persistent volume claim requests that do not specify a storage class.

In some embodiments, the storage class template includes at least one of a storage provision object, a resource recovery policy, whether storage expansion is allowed, a mount option, a storage binding mode, and a storage parameter, and the template generation module includes:

The storage class creation submodule is used to create a storage class based on at least one of the storage provision object, resource recovery policy, whether storage expansion is allowed, mounting options, storage binding mode and storage parameters.

In some embodiments, the request acquisition module includes:

The persistent volume claim request acquisition submodule is used to obtain a persistent volume claim request created by a user that references a target storage class in at least one storage class.

In some embodiments, the allocation module includes:

The search submodule is used to search for the target storage class;

The provisioning submodule is used to use the persistent volume provisioner to provision new persistent volumes in the target storage class based on the persistent volume claim request.

In some embodiments, the persistent volume claim request includes access mode information and storage size information, and the provisioning submodule includes:

The persistent volume provisioning unit is used to use a persistent volume provisioning program to provision a new persistent volume in a target storage class according to the access mode information, the storage size information, and storage definition parameters corresponding to the target storage type.

In some embodiments, the allocation module includes:

The real storage acquisition submodule is used to obtain the real storage specified by the persistent volume provisioning program;

The binding submodule is used to create a new persistent volume in the real storage and bind the new persistent volume to the persistent volume claim request.

In some embodiments, the apparatus further comprises:

A data structure creation module that creates a data structure containing a persistent volume that references a persistent volume claim request by name.

An embodiment of the present application also discloses an electronic device, including: a processor, a memory, and a computer program stored in the memory and capable of running on the processor, and the computer program implements the steps of the above dynamic storage allocation method when executed by the processor.

The embodiment of the present application also discloses a computer non-volatile readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above dynamic storage allocation method are implemented.

The embodiments of the present application include the following advantages:

In an embodiment of the present application, the target storage type can be obtained, and according to the target storage type, a storage class template can be generated using a template adapter to create a storage class based on the storage class template; a persistent volume claim request created by a user for applying for storage resources is obtained; according to the persistent volume claim request, a new persistent volume is provisioned in the created storage class, and a new persistent volume is created, and the new persistent volume is bound to the persistent volume claim request to allocate the persistent volume for the persistent volume claim request. By using a template adapter to generate a storage class template to create a storage class based on a storage class template, the embodiment of the present application can facilitate users to define the required persistent volumes more finely and accurately, and avoid the problem that the user misconfigures parameters of different storage types, resulting in persistent volume creation errors and application startup failures; in addition, it can also ensure that the persistent volume is recycled in the manner required by the user, avoiding accidental deletion of data, affecting the data preservation of stateful container applications or applications with data persistence requirements, and losing important data generated by the application, resulting in application reconstruction failure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flowchart of a method for dynamic storage allocation provided by an embodiment of the present application;

FIG2 is a flowchart of another method for dynamic storage allocation provided by an embodiment of the present application;

FIG3 is a schematic diagram of a dynamic storage allocation process based on Kubernetes provided in an embodiment of the present application;

FIG4 is a structural block diagram of a dynamic storage allocation device provided in an embodiment of the present application;

FIG. 5 is a schematic diagram of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

Kubernetes, also known as K8s, is an open source system for automating the deployment, scaling, and management of containerized applications. In Kubernetes, storage resources are managed in a completely different way from computing resources (CPU (Central Processing Unit)/memory). In order to shield the details of the underlying storage implementation and make it easier for users to use and administrators to manage, Kubernetes introduced two resource objects, Persistent Volume (PV) and Persistent Volume Claim (PVC), to implement the storage management subsystem.

PV (persistent volume) is an abstraction of storage resources, defining storage as a resource that can be used by container applications. PV is created and configured by the administrator, and is directly related to the specific implementation of the storage provider, such as GlusterFS, iSCSI (Internet Small Computer System Interface), RBD (RADOS Block Device, a storage service middle layer built on the RADOS cluster that provides a block device interface to the client), or GCE (Google Public Cloud) or AWS (Amazon Web Services) public cloud shared storage. Shared storage is managed through a plug-in mechanism for application access and use. Except for EmptyDir type storage volumes, the life cycle of PV is independent of the Pod that uses it.

PVC is a user's application for storage resources. Just like Pod consumes Node resources, PVC consumes PV resources. PVC can apply for the size of storage space and access mode (such as ReadWriteOnce, ReadOnlyMany or ReadWriteMany).

The storage space requested using PVC may still not meet the various requirements of applications for storage devices. In many cases, applications have different requirements for the characteristics and performance of storage devices, including read and write speed, concurrency performance, data redundancy, etc. Kubernetes introduced a new resource object StorageClass (SC) from version 1.4 to mark the characteristics and performance of storage resources and dynamically supply appropriate PV resources according to the needs of PVC. By Kubernetes version 1.6, the mechanism of StorageClass and dynamic supply of storage resources has been improved, enabling on-demand creation of storage volumes, which is an important step in the process of automated management of shared storage.

Through the definition of StorageClass, administrators can define storage resources as a certain category (Class), just like the configuration description (Profile) of storage devices, such as fast storage, slow storage, with data redundancy, without data redundancy, etc. Users can intuitively know the characteristics of various storage resources based on the description of StorageClass and apply for storage resources based on the application's demand for storage resources.

After the user defines the PVC, the system will select a PV that meets the PVC requirements from the existing PVs based on the PVC's request for storage resources (storage space and access mode). Once found, the PV will be bound to the user-defined PVC, and the user's application can use this PVC. This will cause two problems:

1. If there is no PV that meets the PVC requirements in the system, the PVC will remain in the Pending state indefinitely until the system administrator creates a PV that meets the requirements, affecting business deployment;

2. In addition, once a PV is bound to a PVC, it will be exclusively used by this PVC and cannot be bound to other PVCs. The binding relationship between PVC and PV is one-to-one, and there will not be a one-to-many situation. If the storage space requested by the PVC is less than the space owned by the PV, the entire PV space can be used by the PVC, which may cause a waste of resources. For example, a PersistentVolumeClaim requires 3GB of storage capacity, and Kubernetes currently only has one 5GB PersistentVolume. At this time, Kubernetes has to bind this PersistentVolume to the PersistentVolumeClaim that applied for the resource, wasting 2GB of space. Assuming that there is another PersistentVolumeClaim that applies for 2GB of storage space later, it can only wait for the administrator to allocate a new PersistentVolume, or other PersistentVolumes are recycled before it can be successfully allocated.

When dynamic provisioning mode is enabled, once the user deletes the PVC, the PV bound to it will also be deleted due to its default recycling policy "Delete". If you need to retain the PV that stores user data, after the dynamic binding is successful, the user needs to change the recycling policy of the PV automatically generated by the system from "Delete" to "Retain". However, if the user forgets to make the change, data will be accidentally deleted, affecting the data preservation of stateful container applications or applications with data persistence requirements, losing important data generated by the application, and causing application reconstruction failure.

Kubernetes can support multiple PV types. Each storage type has its own characteristics and needs to be set according to their respective parameters when used. The large difference in numbers can easily lead to different configurations of the corresponding StorageClass parameters, and some parameters are not displayed, which makes the administrator's configuration work cumbersome. Often, due to different storage type parameters, configuration errors occur, resulting in PV creation errors and application startup failures until the administrator makes the correct changes.

One of the core concepts of the embodiment of the present application is that the target storage type can be obtained, and according to the target storage type, a storage class template can be generated using a template adapter to create a storage class based on the storage class template; a persistent volume claim request created by a user for applying for storage resources is obtained; according to the persistent volume claim request, a new persistent volume is provisioned in the created storage class, and a new persistent volume is created, and the new persistent volume is bound to the persistent volume claim request to allocate the persistent volume for the persistent volume claim request. The embodiment of the present application uses a template adapter to generate a storage class template to create a storage class based on a storage class template, which can facilitate users to define the required persistent volumes more finely and accurately, and avoid the problem that the user misconfigures parameters of different storage types, resulting in persistent volume creation errors and application startup failures; in addition, it can also ensure that the persistent volume is recycled in the manner required by the user, avoiding accidental deletion of data, affecting the data preservation of stateful container applications or applications with data persistence requirements, and losing important data generated by the application, resulting in application reconstruction failure.

1 , a flowchart of a method for dynamic storage allocation provided by an embodiment of the present application is shown. The method is applied to a container cluster management system, and the method may specifically include the following steps:

Step 101, obtaining the target storage type.

In an embodiment of the present application, an administrator can specify at least one target storage type, and the container cluster management system can support multiple persistent volume types, for example:

◎AWSElasticBlockStore: Elastic Block Store provided by AWS public cloud.

◎AzureFile: File provided by Azure public cloud.

◎AzureDisk: Disk provided by Azure public cloud.

◎CephFS: an open source shared storage system.

◎Cinder：OpenStack block storage system.

◎FC (Fibre Channel): optical fiber storage device.

◎FlexVolume: A plug-in storage mechanism.

◎Flocker: An open source shared storage system.

◎GCEPersistentDisk: Persistent Disk provided by GCE public cloud.

◎Glusterfs: an open source shared storage system.

◎HostPath: Host directory, only used for single-machine testing.

◎iSCSI: iSCSI storage device.

◎Local: Local storage device, introduced in Kubernetes version 1.7 and reached a stable version in version 1.14. Currently, Local PV can be provided by specifying a block device (Block Device), or the life cycle of Local PV can be managed through the sig-storage-local-static-provisioner plug-in developed by the community.

◎NFS: Network File System.

◎Portworx Volumes: Storage services provided by Portworx.

◎Quobyte Volumes: Storage services provided by Quobyte.

◎RBD (Ceph Block Device): Ceph block storage.

◎ScaleIO Volumes: DellEMC's storage devices.

◎StorageOS: Storage services provided by StorageOS.

◎VsphereVolume: Storage system provided by VMWare.

Step 102: Generate a storage class template using a template adapter according to the target storage type, so as to create a storage class based on the storage class template.

In an embodiment of the present application, after obtaining at least one target storage type specified by an administrator, a storage class template can be generated using a template adapter according to the at least one target storage type to create a storage class based on the storage class template.

Step 103: Obtain a persistent volume claim request created by a user for applying for storage resources.

In an embodiment of the present application, a user may create a persistent volume claim request for applying for storage resources, and the system may obtain the persistent volume claim request created by the user for applying for storage resources.

Step 104, according to the persistent volume claim request, provision a new persistent volume in the created storage class, create a new persistent volume, bind the new persistent volume to the persistent volume claim request, and allocate a persistent volume for the persistent volume claim request.

In an embodiment of the present application, a new persistent volume can be provisioned in the created storage class according to the persistent volume claim request created by the user, and a new persistent volume can be created and bound to the persistent volume claim request, thereby allocating a persistent volume for the persistent volume claim request.

2, a flowchart of a method for dynamic storage allocation provided by an embodiment of the present application is shown. The method is applied to a container cluster management system. The method may specifically include the following steps:

Step 201, determining whether a persistent volume provisioning program has been deployed;

In an embodiment of the present application, it may be first determined whether a persistent volume provisioning program has been deployed.

Step 202: If the persistent volume provisioning program is not deployed, then return the non-deployment information to enable the cluster administrator to deploy the persistent volume provisioning program.

In the specific implementation, if the persistent volume provisioning program is not installed, the cluster administrator can set up the persistent volume provisioning program for the actual creation, deletion, and other operations of a specific type of storage. The container cluster management system can provide a unified standard, and the persistent volume provisioning program can provide storage definition parameters according to the standard.

In one embodiment, when deploying the persistent volume provisioning program, the method may further include: triggering the template adapter to obtain storage definition parameters corresponding to each storage type, generating template configuration information corresponding to each storage type, and saving the template configuration information to a database.

In one embodiment, triggering the template adapter to obtain storage definition parameters corresponding to each storage type may include: triggering the template adapter to obtain storage definition parameters corresponding to each storage type provided by the persistent volume provisioning program.

In one embodiment, the template configuration information includes template generation rules and template parameter recommendations. Generating template configuration information corresponding to each storage type and saving it in a database may include: generating template generation rules and template parameter recommendations corresponding to each storage type and saving them in a database.

In a specific implementation, when installing the persistent volume provisioning program, the template adapter can be triggered to obtain storage definition parameters corresponding to each storage type provided by the persistent volume provisioning program, and at the same time generate template generation rules and template parameter recommendations and save them in the database.

Step 203, obtaining the target storage type.

In one embodiment, step 203 may include: obtaining at least one target storage type corresponding to at least one target storage provision object, where the storage provision object is an object for providing persistent volume resources.

In the specific implementation, the administrator can specify one or more storage provider objects to describe the provider objects of storage resources, which are used to provide specific persistent volume resources and can also be regarded as backend storage drivers.

Step 204: Generate a storage class template using a template adapter according to the target storage type, so as to create a storage class based on the storage class template.

In one embodiment, a storage class template is generated using a template adapter according to a target storage type, which may include: using a template adapter to query a database for template generation rules and template parameter recommendations corresponding to the target storage type, and generating a storage class template according to the template generation rules and template parameter recommendations corresponding to the target storage type.

In one embodiment, a template adapter is used to query a database for template generation rules and template parameter recommendations corresponding to a target storage type, and generate a storage class template based on the template generation rules and template parameter recommendations corresponding to the target storage type, including: sending the target storage type input by a cluster administrator to the template adapter, so that after receiving the target storage type, the template adapter queries the database for template generation rules and template parameter recommendations corresponding to the target storage type, and generates a storage class template based on the template generation rules and template parameter recommendations corresponding to the target storage type.

In a specific implementation, after receiving the storage provision object input by the administrator, the template adapter can query the database for template generation rules and template parameter recommendations of the corresponding type, and generate one or more storage class templates according to the queried information.

In one embodiment, before creating a storage class based on the storage class template, the process may further include: modifying the template generation rules and template parameter recommendations corresponding to the target storage type in response to a template configuration information modification instruction input by a user.

In one embodiment, creating a storage class based on a storage class template may include: creating at least one storage class corresponding to at least one target storage type based on the storage class template.

In one embodiment, creating a storage class based on a storage class template may also include: setting a default storage class, where the default storage class is applied to persistent volume claim requests that do not specify a storage class.

In the specific implementation, the administrator can modify the corresponding parameters according to the actual needs based on the generated template, create one or more storage volumes, and set a default storage volume at the cluster level for persistent volume claim requests that do not specify a storage volume.

In one embodiment, the storage class template includes at least one of a storage provision object, a resource recovery policy, whether storage expansion is allowed, a mount option, a storage binding mode, and a storage parameter. Creating a storage class based on the storage class template may include:

In a specific implementation, a storage class template may include information and recommended configurations of different dimensions, such as storage providers, resource recovery policies, whether storage expansion is allowed, mount options, storage binding modes, and storage parameters. A storage class may be created based on information and recommended configurations of different dimensions, such as storage providers, resource recovery policies, whether storage expansion is allowed, mount options, storage binding modes, and storage parameters.

Step 205: Obtain a persistent volume claim request created by a user for applying for storage resources.

In one embodiment, step 205 may include: obtaining a persistent volume claim request created by a user that references a target storage class in at least one storage class.

In a specific implementation, a user can create a persistent volume claim request that references one of the storage classes, and the system can obtain the persistent volume claim request created by the user for applying for storage resources.

Step 206, according to the persistent volume claim request, provision a new persistent volume in the created storage class, create a new persistent volume, bind the new persistent volume to the persistent volume claim request, and allocate a persistent volume for the persistent volume claim request.

In one embodiment, provisioning a new persistent volume in a created storage class according to a persistent volume claim request may include: searching for a target storage class; and using a persistent volume provisioning program to provision a new persistent volume in the target storage class according to the persistent volume claim request.

In one embodiment, a persistent volume claim request includes access mode information and storage size information, and a persistent volume provisioning program is used to provision a new persistent volume in a target storage class according to the persistent volume claim request. This may include: using a persistent volume provisioning program to provision a new persistent volume in a target storage class according to the access mode information, storage size information, and storage definition parameters corresponding to the target storage type.

In a specific implementation, the container cluster management system can find the storage class and provisioner referenced therein, and require the provisioner to provision a new persistent volume in the storage class according to the access mode and storage size requested by the persistent volume claim, as well as the parameters.

In one embodiment, creating a new persistent volume and binding the new persistent volume to a persistent volume claim request may include: obtaining real storage specified by a persistent volume provisioning program; creating a new persistent volume in the real storage, and binding the new persistent volume to the persistent volume claim request.

In the implementation, the provisioner specifies the actual storage, creates a persistent volume, and binds it to the persistent volume claim request.

In one embodiment, the method may further include: creating a data structure containing a persistent volume that references the persistent volume claim request by name.

In a specific implementation, a user can create a data structure containing the storage volume requested by referencing the persistent volume claim by name.

In order to enable those skilled in the art to better understand the embodiments of the present application, the embodiments of the present application are described below. Referring to FIG3 , a schematic diagram of a dynamic storage allocation process based on a container cluster management system provided in the embodiments of the present application is shown.

Step 1: If the persistent volume provisioning program has not yet been deployed, the cluster administrator sets up the persistent volume provisioning program.

Step 2: The administrator specifies the storage provider (storage type).

Step 3: The template adapter generates one or more storage class templates based on the storage type.

Step 4: The administrator creates one or more storage classes based on the template and marks them as default.

Step 5: The user creates a persistent volume claim request that applies one of the storage classes.

Step 6: The container cluster management system finds the referenced storage class and provisioner, and asks the provisioner to provision a new persistent volume in the storage class according to the access mode and storage size and parameters requested by the persistent volume claim.

Step 7: The provisioner specifies the actual storage, creates a persistent volume, and binds it to the persistent volume claim request.

Step 8: The user creates a data structure containing the storage volume requested by the persistent volume claim by name.

It should be noted that, for the method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification all belong to the embodiments of the present application, and the actions involved are not necessarily required by the embodiments of the present application.

4 shows a block diagram of a dynamic storage allocation device provided in an embodiment of the present application. The device is applied to a container cluster management system and may specifically include the following modules:

An acquisition module 401 is used to acquire a target storage type;

The template generation module 402 is used to generate a storage class template using a template adapter according to the target storage type, so as to create a storage class based on the storage class template; the storage class template includes storage definition parameters corresponding to the target storage type;

The request acquisition module 403 is used to acquire a persistent volume claim request created by a user for applying for storage resources;

The allocation module 404 is used to provision a new persistent volume in the created storage class according to the storage definition parameters corresponding to the persistent volume claim request and the target storage type, create a new persistent volume, bind the new persistent volume to the persistent volume claim request, and allocate the persistent volume for the persistent volume claim request.

In one embodiment, before obtaining the target storage type, the method further includes:

In one embodiment, when deploying the persistent volume provisioning procedure, the apparatus further includes:

In one embodiment, the trigger module includes:

In one embodiment, the template configuration information includes template generation rules and template parameter recommendations, and the trigger module includes:

In one embodiment, the acquisition module includes:

In one embodiment, the template generation module includes:

In one embodiment, the storage class template generation submodule includes:

The target storage type sending unit is used to send the target storage type input by the cluster administrator to the template adapter, so that after receiving the target storage type, the template adapter queries the database for the template generation rules and template parameter recommendations corresponding to the target storage type, and generates a storage class template based on the template generation rules and template parameter recommendations corresponding to the target storage type.

In one embodiment, before creating a storage class based on the storage class template, the method further includes:

In one embodiment, the template generation module includes:

In one embodiment, the template generation module further includes:

In one embodiment, the storage class template includes at least one of a storage provision object, a resource recovery policy, whether storage expansion is allowed, a mount option, a storage binding mode, and a storage parameter, and the template generation module includes:

In one embodiment, the request acquisition module includes:

In one embodiment, the allocation module includes:

The search submodule is used to search for the target storage class;

In one embodiment, the persistent volume claim request includes access mode information and storage size information, and the provisioning submodule includes:

In one embodiment, the allocation module includes:

In one embodiment, the apparatus further comprises:

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

The present application also provides an electronic device. Referring to FIG. 5 , which is a schematic diagram of an electronic device provided in the present application, the electronic device includes: a processor 51, a memory 52, and a memory stored in the memory 52 and capable of being used in the processor The computer program 53 running on 51 implements each process of the above-mentioned dynamic storage allocation method embodiment when the computer program is executed by the processor, and can achieve the same technical effect. To avoid repetition, it will not be described here.

The embodiment of the present application also provides a computer non-volatile readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned dynamic storage allocation method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

The present application embodiment is described with reference to the flowchart and/or block diagram of the method, terminal device (system) and computer program product according to the embodiment of the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, and the combination of the process and/or box in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device produce a device for realizing the function specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce computer-implemented processing, so that the instructions executed on the computer or other programmable terminal device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Although the embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the embodiments of the present application and all changes and modifications that fall within the scope of the embodiments of the present application.

Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements for such process, method, article or terminal. Elements inherent to the terminal device. In the absence of more restrictions, elements defined by the phrase "comprising a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device comprising the elements.

The dynamic storage allocation method, device, electronic device and non-volatile readable storage medium provided by the present application are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

A dynamic storage allocation method, characterized in that the method is applied to a container cluster management system, and the method comprises:

Get the target storage type;

According to the target storage type, using a template adapter to generate a storage class template, so as to create a storage class based on the storage class template;

Get the persistent volume claim request created by the user to apply for storage resources;

According to the persistent volume claim request, a new persistent volume is provisioned in the created storage class, the new persistent volume is created, and the new persistent volume is bound to the persistent volume claim request to allocate a persistent volume for the persistent volume claim request.
The method according to claim 1 is characterized in that, before obtaining the target storage type, it also includes: determining whether a persistent volume provisioning program has been deployed;

If the persistent volume provisioner is not deployed, the not deployed message is returned to allow the cluster administrator to deploy the persistent volume provisioner.
The method according to claim 2, characterized in that, when deploying the persistent volume provisioning program, the method further comprises:

The template adapter is triggered to obtain storage definition parameters corresponding to each storage type, generate template configuration information corresponding to each storage type and save it in the database.
The method according to claim 3 is characterized in that the triggering template adapter obtains the storage definition parameters corresponding to each storage type, including:

The template adapter is triggered to obtain storage definition parameters corresponding to each storage type provided by the persistent volume provisioning program.
The method according to claim 3, characterized in that the template configuration information includes template generation rules and template parameter recommendations, and the step of generating template configuration information corresponding to each storage type and saving it in a database comprises:

Generate template generation rules and template parameter recommendations corresponding to each storage type and save them in the database.
The method according to claim 4, characterized in that the obtaining the target storage type comprises:

At least one target storage type corresponding to at least one target storage provision object is obtained, where the storage provision object is an object for providing persistent volume resources.
The method according to claim 5, characterized in that the step of generating a storage class template using a template adapter according to the target storage type comprises:

A template adapter is used to query the database for template generation rules and template parameter recommendations corresponding to the target storage type, and a storage class template is generated according to the template generation rules and template parameter recommendations corresponding to the target storage type.
The method according to claim 7 is characterized in that the adopting of the template adapter to query the database for template generation rules and template parameter recommendations corresponding to the target storage type, and generating a storage class template according to the template generation rules and template parameter recommendations corresponding to the target storage type, comprises:

The target storage type input by the cluster administrator is sent to the template adapter, so that after receiving the target storage type, the template adapter queries the database for template generation rules and template parameter recommendations corresponding to the target storage type, and generates a storage class template according to the template generation rules and template parameter recommendations corresponding to the target storage type.
The method according to claim 8, characterized in that before creating a storage class based on the storage class template, it also includes:

In response to a template configuration information modification instruction input by a user, the template generation rule and template parameter recommendation corresponding to the target storage type are modified.
The method according to claim 6, characterized in that the creating a storage class based on the storage class template,

include:

Based on the storage class template, at least one storage class is created corresponding to the at least one target storage type.
The method according to claim 10, characterized in that the step of creating a storage class based on the storage class template further comprises:

Sets a default storage class that is applied to persistent volume claim requests that do not specify a storage class.
The method according to claim 1, characterized in that the storage class template includes at least one of a storage provision object, a resource recovery strategy, whether storage expansion is allowed, a mount option, a storage binding mode, and a storage parameter.

The creating a storage class based on the storage class template includes:

A storage class is created based on at least one of a storage provision object, a resource recovery policy, whether storage expansion is allowed, a mount option, a storage binding mode, and a storage parameter.
The method according to claim 10, characterized in that the obtaining of a persistent volume claim request created by a user for applying for storage resources comprises:

A persistent volume claim request created by a user referencing a target storage class in the at least one storage class is obtained.
The method according to claim 13, wherein the step of provisioning a new persistent volume in the created storage class according to the persistent volume claim request comprises:

Find the target storage class;

The persistent volume provisioning procedure is used to provision a new persistent volume in the target storage class according to the persistent volume claim request.
The method according to claim 14, characterized in that the persistent volume claim request includes access mode information and storage size information, and the adopting the persistent volume provisioning program to provision a new persistent volume in the target storage class according to the persistent volume claim request comprises:

The persistent volume provisioning program is used to provision a new persistent volume in the target storage class according to the access mode information, the storage size information, and the storage definition parameters corresponding to the target storage type.
The method according to claim 15, characterized in that the creating the new persistent volume and binding the new persistent volume to the persistent volume claim request comprises:

Obtaining the real storage specified by the persistent volume provisioner;

The new persistent volume is created in the real storage, and the new persistent volume is bound to the persistent volume claim request.
The method according to claim 1, characterized in that the method further comprises:

Creates a data structure containing the persistent volume requested by referencing the persistent volume claim by name.
A dynamic storage allocation device, characterized in that the device is applied to a container cluster management system, and the device comprises:

An acquisition module is used to obtain the target storage type;

A template generation module, configured to generate a storage class template using a template adapter according to the target storage type, so as to create a storage class based on the storage class template; the storage class template includes storage definition parameters corresponding to the target storage type;

The request acquisition module is used to obtain the persistent volume claim request created by the user to apply for storage resources;

An allocation module is used to provision a new persistent volume in the created storage class according to the persistent volume declaration request and the storage definition parameters corresponding to the target storage type, create the new persistent volume, bind the new persistent volume to the persistent volume declaration request, so as to allocate a persistent volume for the persistent volume declaration request.
An electronic device, characterized in that it includes: a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the steps of the dynamic storage allocation method as described in any one of claims 1 to 17 are implemented.
A computer non-volatile readable storage medium, characterized in that a computer program is stored on the computer non-volatile readable storage medium, and when the computer program is executed by a processor, the steps of the dynamic storage allocation method as described in any one of claims 1 to 17 are implemented.