CN116661686A - Data storage method, device, equipment and storage medium - Google Patents

Data storage method, device, equipment and storage medium Download PDF

Info

Publication number
CN116661686A
CN116661686A CN202310573947.0A CN202310573947A CN116661686A CN 116661686 A CN116661686 A CN 116661686A CN 202310573947 A CN202310573947 A CN 202310573947A CN 116661686 A CN116661686 A CN 116661686A
Authority
CN
China
Prior art keywords
target
volume
logical volume
storage
application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310573947.0A
Other languages
Chinese (zh)
Inventor
李祥哲
赵建星
樊建刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jingdong Technology Information Technology Co Ltd
Original Assignee
Jingdong Technology Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jingdong Technology Information Technology Co Ltd filed Critical Jingdong Technology Information Technology Co Ltd
Priority to CN202310573947.0A priority Critical patent/CN116661686A/en
Publication of CN116661686A publication Critical patent/CN116661686A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
    • G06F3/0656—Data buffering arrangements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0662—Virtualisation aspects
    • G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Memory System Of A Hierarchy Structure (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the invention discloses a data storage method, a device, equipment and a storage medium. The method is applied to a target node server in a container orchestration system, and comprises the following steps: creating a target deployment unit based on the target persistent storage volume declaration; responding to a binding operation declared by a target persistent storage volume in the creation process of a target deployment unit, and dividing a first logic volume in a first volume group converted by a solid state disk and a second logic volume in a second volume group converted by a mechanical hard disk by calling a target container storage plug-in; taking the first logic volume as a cache disk and the second logic volume as a storage disk; and in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume. By the technical scheme provided by the embodiment of the invention, the use cost can be reduced while the high performance is ensured.

Description

Data storage method, device, equipment and storage medium
Technical Field
Embodiments of the present invention relate to computer technologies, and in particular, to a data storage method, apparatus, device, and storage medium.
Background
With the rapid development of computer technology and cloud-based technology, a container orchestration system can be utilized to conduct full life-cycle efficient orchestration and management of containerized applications in a cloud platform. For example, the Kubernetes system is utilized to manage the containerized applications on a plurality of node servers in the cloud platform, so that the containerized applications are simpler and more efficient to deploy.
At present, when a containerized application is deployed, a solid state disk or a mechanical hard disk is generally directly used as a storage hard disk of the application, so that local storage of application data is realized.
However, in the process of implementing the present invention, the inventors found that at least the following problems exist in the prior art:
in the existing local storage mode, the performance of the solid state disk is very high, but the solid state disk is expensive and deficient, and the use cost is increased. However, mechanical hard disks are inexpensive, but have low performance and cannot meet the requirements for high IO performance.
Disclosure of Invention
The embodiment of the invention provides a data storage method, a data storage device, data storage equipment and a data storage medium, so that high performance is ensured and the use cost is reduced.
In a first aspect, an embodiment of the present invention provides a data storage method, applied to a target node server in a container arrangement system, including:
Acquiring a target persistence storage volume statement corresponding to a containerized target application, and creating a target deployment unit corresponding to the target application in the target node server based on the target persistence storage volume statement;
responding to a binding operation of the target persistent storage volume declaration in a target deployment unit creation process, and dividing a first logic volume in a first volume group of the target node server and a second logic volume in a second volume group based on the target persistent storage volume declaration by calling a target container storage plug-in the target node server, wherein the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical disk;
taking the first logical volume as a cache disk of the target application, and taking the second logical volume as a storage disk of the target application;
and in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume.
In a second aspect, an embodiment of the present invention further provides a data storage device, integrated in a target node server in a container orchestration system, including:
the target deployment unit creation module is used for acquiring a target persistent storage volume statement corresponding to the containerized target application, and creating a target deployment unit corresponding to the target application in the target node server based on the target persistent storage volume statement;
the logical volume creation module is used for responding to the binding operation of the target persistent storage volume declaration in the creation process of the target deployment unit, and dividing a first logical volume in a first volume group of the target node server and a second logical volume in a second volume group based on the target persistent storage volume declaration by calling a target container storage plug-in the target node server, wherein the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical hard disk;
the logic volume processing module is used for taking the first logic volume as a cache disk of the target application and taking the second logic volume as a storage disk of the target application;
And the logic volume mounting module is used for mounting the first logic volume and the second logic volume to the created target deployment unit in response to the creation completion operation of the target deployment unit so as to store application data generated by the target application in the running process into the first logic volume and the second logic volume.
In a third aspect, an embodiment of the present invention further provides an electronic device, including:
one or more processors;
a memory for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the data storage methods as provided by any of the embodiments of the present invention.
In a fourth aspect, embodiments of the present invention also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a data storage method as provided by any of the embodiments of the present invention.
One embodiment of the above invention has the following advantages or benefits:
a target node server in the container arrangement system creates a target deployment unit corresponding to the target application by storing volume declarations based on target persistence corresponding to the containerized target application; responding to a binding operation of a target persistence storage volume statement in the creation process of a target deployment unit, dividing a first logic volume in a first volume group and a second logic volume in a second volume group of a target node server based on the target persistence storage volume statement by calling a target container storage plug-in, taking the first logic volume as a cache disk of a target application, and taking the second logic volume as a storage disk of the target application; and in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume, and local storage of the application data is realized. The first volume group is a volume group converted by the solid state disk, and the second volume group is a volume group converted by the mechanical hard disk, so that the first logical volume is a logical volume of a solid state disk type, the second logical volume is a logical volume of a mechanical hard disk type, and further the first logical volume is used as a cache disk of a target application, so that the target application has high performance, and the second logical volume is used as a storage disk of the target application, so that the target application has lower use cost. Compared with the solid state disk, the method and the device have the advantages that the high performance can be guaranteed and the use cost can be reduced by combining the solid state disk with the mechanical hard disk.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description will be given below of the drawings required for the embodiments or the prior art descriptions, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method of data storage according to one embodiment of the present invention;
FIG. 2 is an architectural example of a container orchestration system according to one embodiment of the present invention;
FIG. 3 is a flow chart of a method of data storage provided by one embodiment of the present invention;
FIG. 4 is a flow chart of a method of data storage provided by one embodiment of the present invention;
FIG. 5 is a schematic diagram of a data storage device according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Fig. 1 is a flowchart of a data storage method according to an embodiment of the present invention, where the embodiment may be suitable for a case where a containerized application is deployed and application data generated by the containerized application is locally stored. The method may be performed by a data storage device, which may be implemented in software and/or hardware, integrated in an electronic device. For example, the apparatus may be integrated with a target node server in the container orchestration system.
Wherein the container orchestration system may be an application system for orchestration management of the containerization. For example, the container orchestration system may refer to a Kubernetes system. Referring to fig. 2, the container orchestration system may include a cluster of node servers and a management server. Wherein the node server cluster comprises a plurality of node servers. Each node server is the server that actually deploys the containerized application. The management server is used for managing a plurality of node servers, such as container scheduling, node state detection and the like. For example, the management server may schedule the currently required to be deployed containerized application to a node server for deployment based on internal scheduling logic. The target node server refers to the node server to which the containerized application currently needs to be deployed. The internal architecture of each node server is the same. For example, referring to fig. 2, a target node server may include a proxy module, a target container storage plug-in (such as a CSI container storage interface), and a plug-in controller for supporting the implementation of plug-in functions. Where a proxy module (such as kubull) refers to a proxy running in the target node server to ensure that containers are all running in the deployment unit. The target container storage plug-in may be a newly added container storage interface plug-in, so as to create a first logical volume of the solid state disk type and a second logical volume of the mechanical hard disk type through the plug-in and combine the first logical volume and the second logical volume to cache data. The target container storage plugin is registered in the proxy module in advance, so that the proxy module can successfully call the target container storage plugin to carry out storage processing.
As shown in fig. 1, the method specifically includes the following steps:
s110, acquiring a target persistent storage volume statement corresponding to the containerized target application, and creating a target deployment unit corresponding to the target application in a target node server based on the target persistent storage volume statement.
The target application may refer to an application that currently needs to be deployed in the target node server after being containerized. The number of target applications may be one or more. One for each target application. The target persistent storage volume declaration (Persistent Volume Claim, PVC) is configuration information describing the persistent storage volume (Persistent Volume, PV) of the target application, which can be personalized based on the application requirements. The deployment unit Pod is the smallest deployment unit created and managed in the target node server. One container may be run in each deployment unit, or multiple containers may be run simultaneously. All containers in each deployment unit share network and storage space. The target deployment unit refers to a deployment unit containing a containerized target application.
Specifically, if the target application needs to be deployed and released at present, the target application is containerized, a target persistent storage volume statement corresponding to the containerized target application is configured, a target application deployment request containing the target persistent storage volume statement is generated, and the target application deployment request is sent to the management server. The management server responds to and dispatches the target application deployment request, so that the target application deployment request is dispatched to the target node server. Referring to fig. 2, after receiving a target application deployment request, an agent module in a target node server parses the target application deployment request to obtain a target persistent storage volume declaration PVC corresponding to the containerized target application, and creates a target deployment unit Pod corresponding to the target application in the target node server based on storage configuration information in the target persistent storage volume declaration.
S120, responding to a binding operation of a target persistent storage volume statement in the creation process of a target deployment unit, and dividing a first logic volume in a first volume group of a target node server and a second logic volume in a second volume group based on the target persistent storage volume statement by calling a target container storage plug-in the target node server, wherein the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical disk.
Wherein each node server has a container storage plug-in. The target container storage plugin is a container storage plugin in the target node server. A volume group is a storage pool made up of one or more physical volumes on which one or more logical volumes may be created. The physical volume refers to a solid state disk partition or a mechanical hard disk partition. The physical volumes are basic storage logical blocks of a logical volume manager (Logical Volume Manager, LVM). One hard disk partition may correspond to one physical volume. An LVM may logically aggregate one or more hard disk partitions, equivalent to one large hard disk usage. When the space of a certain hard disk is not enough, the partition of other hard disks can be continuously added, so that the dynamic management of the storage capacity can be realized, and the storage flexibility is improved. The first volume group is obtained by converting at least one solid state disk in the target node server. The solid state disk (Solid State Drives, SSD) is a hard disk made of a solid state electronic memory chip array, and the read-write speed is high. The second volume group is obtained by at least one mechanical hard disk translation in the target node server. The mechanical Hard Disk (HDD) mainly comprises a Disk, a magnetic head, a Disk rotating shaft, a control motor and the like, has low unit cost, and is suitable for mass storage. The first logical volume is a logical volume of a solid state disk type divided in a first volume group. The second logical volume is a logical volume of the mechanical hard disk type partitioned in the second volume group. A file system may be established on the first logical volume and the second logical volume. The first logical volume and the second logical volume are used as local storage media.
Specifically, referring to fig. 2, the proxy module has an operation of binding the target persistent storage volume declaration in the process of creating the target deployment unit, and when the operation is performed, the proxy module calls the target container storage plug-in to perform partition creation of the first logical volume and the second logical volume. For example, based on the storage configuration information in the target persistent storage volume declaration in the target container storage plugin, a first logical volume specifying a storage capacity and specifying a system file format may be partitioned in a first volume group of the target node server by the logical volume manager, and a second logical volume specifying a storage capacity and specifying a system file format may be partitioned in a second volume group, so that two different types of logical volumes, a first logical volume of a solid state disk type and a second logical volume of a mechanical hard disk type, respectively, may be obtained with the target container storage plugin.
It should be noted that, after the target persistent storage volume declaration is obtained, the target container storage plug-in is not called immediately to perform partition creation of the first logical volume and the second logical volume, but is called when the target deployment unit creates the target persistent storage volume declaration, so that when the target deployment unit determines that the target node server is scheduled, the target deployment unit can create the first logical volume and the second logical volume in the target node server, further, the first logical volume and the second logical volume can be mounted in the created target deployment unit, and the creation of the first logical volume and the second logical volume is completed before the target deployment unit is created, further, the success of mounting is ensured, the mounting error cannot be caused due to the scheduling problem, and further, the condition of application data loss is caused.
S130, taking the first logic volume as a cache disk of the target application, and taking the second logic volume as a storage disk of the target application.
Specifically, referring to fig. 2, after two different types of first logical volumes and second logical volumes are created for a target application, the first logical volumes and the second logical volumes which are independent of each other may be aggregated and cached in a cache manner, so that the first logical volumes of a solid state disk type are used as a cache disk of the target application, and the second logical volumes of a mechanical disk type are used as storage disks of the target application, so that application data generated by the target application may be cached on the first logical volumes and then written into the second logical volumes, thereby accelerating the read-write performance. By combining the first logical volume of the solid state disk type with the second logical volume of the mechanical hard disk type to store data, storage performance consistent with that of using only the solid state disk can be achieved. The second logic volume of the low-cost mechanical hard disk type is used as the storage disk, so that the use cost is lower than that of the solid state hard disk only, and the use cost can be controlled while the requirement of target application on high read-write performance is met, so that the cost is not too high.
Illustratively, S130 may include: and taking the first logic volume as a cache disk of the target application and the second logic volume as a storage disk of the target application in a flash cache mode.
The flash cache manner may refer to adding a primary cache layer between the file system and the device driver, where the primary cache layer may use a first logical volume of a solid state disk type as a cache disk of a second logical volume of a mechanical hard disk type, and the second logical volume of the mechanical hard disk type as a final data storage disk. That is, the flash cache manner may aggregate the first logical volume and the second logical volume that are independent of each other into a virtual block device with a cache. By using a flash cache mode, high-performance and low-cost local storage can be realized.
And S140, mounting the first logic volume and the second logic volume to the created target deployment unit in response to the creation completion operation of the target deployment unit, so that application data generated by the target application in the running process is stored in the first logic volume and the second logic volume.
Specifically, referring to fig. 2, after a target deployment unit is created through a target container storage plug-in, the target container storage plug-in mounts the aggregated first logical volume and the second logical volume (the first logical volume is used as a buffer disk at this time, and the second logical volume is used as a storage disk) into the created target deployment unit, so as to establish a corresponding relationship between the first logical volume and the second logical volume and the target deployment unit, and further based on the corresponding relationship, the application data generated by the target application in the target deployment unit in the running process can be cached in the first logical volume and then written back into the second logical volume, thereby realizing efficient storage of the application data.
According to the technical scheme of the embodiment, a target node server in a container arrangement system creates a target deployment unit corresponding to a target application by a target persistent storage volume statement corresponding to the containerized target application; responding to a binding operation of a target persistence storage volume statement in the creation process of a target deployment unit, dividing a first logic volume in a first volume group and a second logic volume in a second volume group of a target node server based on the target persistence storage volume statement by calling a target container storage plug-in, taking the first logic volume as a cache disk of a target application, and taking the second logic volume as a storage disk of the target application; and in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume, and local storage of the application data is realized. The first volume group is a volume group converted by the solid state disk, and the second volume group is a volume group converted by the mechanical hard disk, so that the first logical volume is a logical volume of a solid state disk type, the second logical volume is a logical volume of a mechanical hard disk type, and further the first logical volume is used as a cache disk of a target application, so that the target application has high performance, and the second logical volume is used as a storage disk of the target application, so that the target application has lower use cost. Compared with the solid state disk, the method and the device have the advantages that the high performance can be guaranteed and the use cost can be reduced by combining the solid state disk with the mechanical hard disk.
Based on the above technical solution, before S110, the method may further include: determining a target solid state disk in a target node server based on solid state disk configuration information corresponding to the target node server, and converting the target solid state disk into a first volume group; and determining a target mechanical hard disk in the target node server based on the mechanical hard disk configuration information corresponding to the target node server, and converting the target mechanical hard disk into a second volume group.
The configuration information of the solid state disk is configured in advance based on service requirements and is used for representing the vacant solid state disk which can be allowed to be converted into a volume group in the target node server. The mechanical hard disk configuration information is configured in advance based on service requirements and is used for representing the spare mechanical hard disk which can be allowed to be converted into a volume group in the target node server.
Specifically, before deploying a containerized target application, determining all target solid state disks specified in a target node server based on solid state disk configuration information corresponding to the target node server, and initializing all target solid state disks as a first volume group, so that all target solid state disks are converted into the first volume group. And similarly, determining all target mechanical hard disks designated in the target node server based on the mechanical hard disk configuration information corresponding to the target node server, and initializing all target mechanical hard disks into a second volume group so as to convert all target mechanical hard disks into the second volume group. By performing hard disk conversion in advance based on hard disk configuration information, a first logical volume can be directly created in a converted first volume group and a second logical volume can be created in a second volume group when target applications are deployed later, so that the creation efficiency of the logical volumes is improved, meanwhile, dynamic configuration of the volume groups is realized by utilizing the hard disk configuration information, and the storage flexibility is further improved.
Fig. 3 is a flowchart of a data storage method according to an embodiment of the present invention, where the step of "partitioning a first logical volume in a first volume group and a second logical volume in a second volume group of a target node server based on a target persistent storage volume declaration" is optimized based on the above embodiments. Wherein the explanation of the same or corresponding terms as those of the above embodiments is not repeated herein.
Referring to fig. 3, the data storage method provided in this embodiment specifically includes the following steps:
s310, acquiring a target persistent storage volume statement corresponding to the containerized target application, and creating a target deployment unit corresponding to the target application in a target node server based on the target persistent storage volume statement.
S320, responding to the binding operation of the target persistence storage volume statement in the creation process of the target deployment unit, and determining the target cache capacity based on the target cache proportion and the target storage capacity in the target persistence storage volume statement by calling a target container storage plug-in the target node server.
The target cache proportion may be a proportion between the cache capacity and the storage capacity, which is preconfigured in the target persistent storage volume declaration. For example, the target cache proportion is 50%. The target storage capacity may refer to the storage capacity of the target application storage disk, which is also pre-configured in the target persistent storage volume declaration. The target storage capacity may be greater than the total storage capacity of a single hard disk or a single hard disk partition, which is not limited by the total storage capacity of a single hard disk or a single hard disk partition.
Specifically, the proxy module has an operation of binding the statement of the target persistent storage volume in the process of creating the target deployment unit, and when the operation is executed, the proxy module can call the target container storage plugin to perform partition creation of the first logical volume and the second logical volume. For example, in the target container storage plugin, the target cache proportion in the target persistent storage volume statement is multiplied by the target storage capacity, and the obtained multiplication result is the target cache capacity.
S330, dividing a first logical volume with the target cache capacity in a first volume group of the target node server.
Specifically, in the target container storage plugin, a first logical volume having a target cache capacity is partitioned in a first volume group of the target node server by a logical volume manager.
Illustratively, S330 may include: dividing a basic logic volume with target cache capacity in a first volume group of a target node server; and formatting the basic logical volume based on the target file system format in the target persistent storage volume statement to obtain a first logical volume.
Wherein the target file system format refers to a file system format of a target application preconfigured in the target persistent storage volume declaration. For example, the file system format may be ext3, ext4, or xfs.
Specifically, when creating the first logical volume, the target container storage plugin may first partition the base logical volume with the target cache capacity in the first volume group of the target node server, and then format the base logical volume into the target file system format based on the target file system format in the target persistent storage volume declaration, thereby obtaining the first logical volume in the target file system format, so as to cache the application file data in the first logical volume.
S340, dividing a second logical volume with the target storage capacity in a second volume group of the target node server.
Specifically, in the target container storage plugin, a second logical volume having a target storage capacity is partitioned in a second volume group of the target node server by the logical volume manager.
Illustratively, S340 may include: dividing a base logical volume having a target storage capacity in a second volume group of the target node server; and formatting the basic logical volume based on the target file system format in the target persistent storage volume statement to obtain a second logical volume.
Specifically, similar to the first logical volume creation process, the target container storage plug-in may first partition a base logical volume having a target storage capacity in a second volume group of the target node server, and then format the base logical volume into a target file system format based on a target file system format in a target persistent storage volume declaration, thereby obtaining a second logical volume in the target file system format for storing application file data in the second logical volume.
S350, taking the first logic volume as a cache disk of the target application, and taking the second logic volume as a storage disk of the target application.
S360, in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume.
According to the technical scheme, the target cache capacity is determined based on the target cache proportion and the target storage capacity in the target persistent storage volume statement, the first logic volume with the target cache capacity is divided in the first volume group of the target node server, and the second logic volume with the target storage capacity is divided in the second volume group of the target node server, so that capacity spaces of the first logic volume and the second logic volume can be dynamically configured, and storage flexibility is further improved.
Fig. 4 is a flowchart of a data storage method according to an embodiment of the present invention, where the step of storing application data generated during the running process of the target application into the first logical volume and the second logical volume is optimized based on the foregoing embodiments. Wherein the explanation of the same or corresponding terms as those of the above embodiments is not repeated herein.
Referring to fig. 4, the data storage method provided in this embodiment specifically includes the following steps:
s410, acquiring a target persistent storage volume statement corresponding to the containerized target application, and creating a target deployment unit corresponding to the target application in a target node server based on the target persistent storage volume statement.
S420, responding to a binding operation of a target persistent storage volume statement in the creation process of the target deployment unit, and dividing a first logic volume in a first volume group and a second logic volume in a second volume group of the target node server based on the target persistent storage volume statement by calling a target container storage plug-in the target node server.
S430, taking the first logical volume as a cache disk of the target application, and taking the second logical volume as a storage disk of the target application.
S440, in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit.
S450, determining a target cache policy corresponding to the target application based on the cache policy configuration information in the target persistent storage volume statement.
The target cache policy may refer to a manner in which application data generated by the target application is cached and stored. For example, the target cache policy may be a write-back policy or a write-through policy.
Specifically, the configuration of the caching policy can be performed in the target persistent storage volume statement in advance, so that different caching policies can be configured for different applications, and therefore personalized requirements are met. For example, the cache policy configured by the cache policy configuration information in the target persistent storage volume declaration may be used as the target cache policy corresponding to the target application.
S460, storing application data generated in the running process of the target application into the first logic volume and the second logic volume based on the target caching strategy.
Specifically, when application data generated in the running process of the target application is stored, the cache storage of the application data can be performed based on the configured target cache policy, so that storage performance consistent with that of the solid state disk is obtained.
Illustratively, S460 may include: if the target cache policy is a write-back policy, storing all application data generated by the target application in the running process to the first logical volume, and storing all application data to the second logical volume when the write-back instruction is detected.
Specifically, the write-back strategy is to firstly cache all the generated application data into the first logical volume, when the operating system needs to write back, a write-back instruction is sent, and when the write-back instruction is received, all the application data cached in the cache disk are written back into the second logical volume, so that the write-back strategy has high read-write performance.
Illustratively, S460 may further include: and if the target cache policy is a write-through policy, storing all application data generated by the target application in the running process into the first logic volume and the second logic volume simultaneously.
Specifically, the write-through strategy is to cache all generated application data to the first logical volume, and store the cached application data to the second logical volume while caching, so that synchronous storage of the data is realized, and the storage performance is high.
According to the technical scheme, the target caching strategy corresponding to the target application is determined based on the caching strategy configuration information in the target persistence storage volume statement, and the application data generated in the running process of the target application are stored in the first logical volume and the second logical volume based on the target caching strategy, so that dynamic configuration of the caching strategy can be realized, and different personalized requirements can be met.
The following is an embodiment of a data storage device provided in the embodiment of the present invention, which belongs to the same inventive concept as the data storage method of the above embodiments, and reference may be made to the embodiments of the data storage method for details that are not described in detail in the embodiments of the data storage device.
Fig. 5 is a schematic structural diagram of a data storage device according to an embodiment of the present invention, where the embodiment is applicable to a case where a containerized application is deployed and application data generated by the containerized application is locally stored. As shown in fig. 5, the target node server integrated in the container arrangement system specifically includes: a target deployment unit creation module 510, a logical volume creation module 520, a logical volume processing module 530, and a logical volume mounting module 540.
The target deployment unit creation module 510 is configured to obtain a target persistent storage volume declaration corresponding to a containerized target application, and create a target deployment unit corresponding to the target application in the target node server based on the target persistent storage volume declaration;
a logical volume creation module 520, configured to respond to a binding operation of the target persistent storage volume declaration in a target deployment unit creation process, by calling a target container storage plugin in the target node server, and divide a first logical volume in a first volume group of the target node server and a second logical volume in a second volume group based on the target persistent storage volume declaration, where the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical disk;
A logical volume processing module 530, configured to use the first logical volume as a cache disk of the target application, and use the second logical volume as a storage disk of the target application;
and a logical volume mounting module 540, configured to mount the first logical volume and the second logical volume to the created target deployment unit in response to the creation completion operation of the target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume.
According to the technical scheme of the embodiment, a target node server in a container arrangement system creates a target deployment unit corresponding to a target application by a target persistent storage volume statement corresponding to the containerized target application; responding to a binding operation of a target persistence storage volume statement in the creation process of a target deployment unit, dividing a first logic volume in a first volume group and a second logic volume in a second volume group of a target node server based on the target persistence storage volume statement by calling a target container storage plug-in, taking the first logic volume as a cache disk of a target application, and taking the second logic volume as a storage disk of the target application; and in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume, and local storage of the application data is realized. The first volume group is a volume group converted by the solid state disk, and the second volume group is a volume group converted by the mechanical hard disk, so that the first logical volume is a logical volume of a solid state disk type, the second logical volume is a logical volume of a mechanical hard disk type, and further the first logical volume is used as a cache disk of a target application, so that the target application has high performance, and the second logical volume is used as a storage disk of the target application, so that the target application has lower use cost. Compared with the solid state disk, the method and the device have the advantages that the high performance can be guaranteed and the use cost can be reduced by combining the solid state disk with the mechanical hard disk.
Optionally, the logical volume creation module 520 includes:
a target cache capacity determining unit, configured to determine a target cache capacity based on a target cache proportion and a target storage capacity in the target persistent storage volume declaration;
a first logical volume creation unit configured to divide a first logical volume having the target cache capacity in a first volume group of the target node server;
a second logical volume creation unit configured to partition a second logical volume having the target storage capacity in a second volume group of the target node server.
Optionally, the first logical volume creation unit is specifically configured to:
dividing a basic logic volume with the target cache capacity in a first volume group of the target node server; and formatting the basic logical volume based on the target file system format in the target persistent storage volume statement to obtain a first logical volume.
Optionally, the logical volume processing module 530 is specifically configured to:
and taking the first logical volume as a cache disk of the target application and the second logical volume as a storage disk of the target application in a flash cache mode.
Optionally, the apparatus further comprises:
the target cache policy determining module is used for determining a target cache policy corresponding to the target application based on cache policy configuration information in the target persistent storage volume statement;
and the data storage module is used for storing application data generated by the target application in the running process into the first logic volume and the second logic volume based on the target cache policy.
Optionally, the data storage module is specifically configured to:
if the target cache policy is a write-back policy, storing all application data generated by the target application in the running process to the first logical volume, and storing all application data to the second logical volume when a write-back instruction is detected;
and if the target cache policy is a write-through policy, storing all application data generated by the target application in the running process into the first logical volume and the second logical volume simultaneously.
Optionally, the apparatus further comprises:
the hard disk conversion module is used for determining a target solid state disk in the target node server based on the solid state disk configuration information corresponding to the target node server before acquiring a target persistent storage volume statement corresponding to the containerized target application, and converting the target solid state disk into a first volume group; and determining a target mechanical hard disk in the target node server based on the mechanical hard disk configuration information corresponding to the target node server, and converting the target mechanical hard disk into a second volume group.
The data storage device provided by the embodiment of the invention can execute the data storage method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the data storage method.
It should be noted that, in the above embodiment of the data storage device, each unit and module included are only divided according to the functional logic, but not limited to the above division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. Fig. 6 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 6 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 6, the electronic device 12 is in the form of a general purpose computing device. Components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.
Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Electronic device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard disk drive"). Although not shown in fig. 6, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.
The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the electronic device 12, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 over the bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing a data storage method step provided by the present embodiment, the method comprising:
acquiring a target persistence storage volume statement corresponding to a containerized target application, and creating a target deployment unit corresponding to the target application in the target node server based on the target persistence storage volume statement;
responding to a binding operation of the target persistent storage volume declaration in a target deployment unit creation process, and dividing a first logic volume in a first volume group of the target node server and a second logic volume in a second volume group based on the target persistent storage volume declaration by calling a target container storage plug-in the target node server, wherein the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical disk;
taking the first logical volume as a cache disk of the target application, and taking the second logical volume as a storage disk of the target application;
and in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume.
Of course, those skilled in the art will appreciate that the processor may also implement the technical solution of the data storage method provided in any embodiment of the present invention.
The present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the data storage method steps as provided by any embodiment of the present invention, the method comprising:
acquiring a target persistence storage volume statement corresponding to a containerized target application, and creating a target deployment unit corresponding to the target application in the target node server based on the target persistence storage volume statement;
responding to a binding operation of the target persistent storage volume declaration in a target deployment unit creation process, and dividing a first logic volume in a first volume group of the target node server and a second logic volume in a second volume group based on the target persistent storage volume declaration by calling a target container storage plug-in the target node server, wherein the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical disk;
taking the first logical volume as a cache disk of the target application, and taking the second logical volume as a storage disk of the target application;
And in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume.
The computer storage media of embodiments of the invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations of the present invention may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
It will be appreciated by those of ordinary skill in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be centralized on a single computing device, or distributed over a network of computing devices, or they may alternatively be implemented in program code executable by a computer device, such that they are stored in a memory device and executed by the computing device, or they may be separately fabricated as individual integrated circuit modules, or multiple modules or steps within them may be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims (10)

1. A data storage method, for use in a destination node server in a container orchestration system, comprising:
acquiring a target persistence storage volume statement corresponding to a containerized target application, and creating a target deployment unit corresponding to the target application in the target node server based on the target persistence storage volume statement;
responding to a binding operation of the target persistent storage volume declaration in a target deployment unit creation process, and dividing a first logic volume in a first volume group of the target node server and a second logic volume in a second volume group based on the target persistent storage volume declaration by calling a target container storage plug-in the target node server, wherein the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical disk;
taking the first logical volume as a cache disk of the target application, and taking the second logical volume as a storage disk of the target application;
and in response to the creation completion operation of the target deployment unit, mounting the first logical volume and the second logical volume to the created target deployment unit, so that application data generated by the target application in the running process is stored in the first logical volume and the second logical volume.
2. The method of claim 1, wherein partitioning a first logical volume in a first volume group and a second logical volume in a second volume group of the target node server based on the target persistent storage volume declaration comprises:
determining a target cache capacity based on a target cache proportion and a target storage capacity in the target persistent storage volume declaration;
dividing a first logical volume with the target cache capacity in a first volume group of the target node server;
a second logical volume having the target storage capacity is partitioned in a second volume group of the target node server.
3. The method of claim 2, wherein partitioning the first logical volume having the target cache capacity in the first volume group of the target node server comprises:
dividing a basic logic volume with the target cache capacity in a first volume group of the target node server;
and formatting the basic logical volume based on the target file system format in the target persistent storage volume statement to obtain a first logical volume.
4. The method of claim 1, wherein the taking the first logical volume as a cache disk for the target application and the second logical volume as a storage disk for the target application comprises:
And taking the first logical volume as a cache disk of the target application and the second logical volume as a storage disk of the target application in a flash cache mode.
5. The method of claim 1, wherein the application data generated by the target application during run-time is stored in the first logical volume and the second logical volume, comprising:
determining a target cache policy corresponding to the target application based on the cache policy configuration information in the target persistent storage volume statement;
and storing application data generated by the target application in the running process into the first logic volume and the second logic volume based on the target caching strategy.
6. The method of claim 5, wherein storing application data generated by the target application during run-time into the first logical volume and the second logical volume based on the target cache policy comprises:
if the target cache policy is a write-back policy, storing all application data generated by the target application in the running process to the first logical volume, and storing all application data to the second logical volume when a write-back instruction is detected;
And if the target cache policy is a write-through policy, storing all application data generated by the target application in the running process into the first logical volume and the second logical volume simultaneously.
7. The method of any of claims 1-6, further comprising, prior to obtaining the target persistent storage volume declaration corresponding to the containerized target application:
determining a target solid state disk in the target node server based on the solid state disk configuration information corresponding to the target node server, and converting the target solid state disk into a first volume group;
and determining a target mechanical hard disk in the target node server based on the mechanical hard disk configuration information corresponding to the target node server, and converting the target mechanical hard disk into a second volume group.
8. A data storage device, characterized by a target node server integrated in a container orchestration system, comprising:
the target deployment unit creation module is used for acquiring a target persistent storage volume statement corresponding to the containerized target application, and creating a target deployment unit corresponding to the target application in the target node server based on the target persistent storage volume statement;
The logical volume creation module is used for responding to the binding operation of the target persistent storage volume declaration in the creation process of the target deployment unit, and dividing a first logical volume in a first volume group of the target node server and a second logical volume in a second volume group based on the target persistent storage volume declaration by calling a target container storage plug-in the target node server, wherein the first volume group is a volume group converted by a solid state disk, and the second volume group is a volume group converted by a mechanical hard disk;
the logic volume processing module is used for taking the first logic volume as a cache disk of the target application and taking the second logic volume as a storage disk of the target application;
and the logic volume mounting module is used for mounting the first logic volume and the second logic volume to the created target deployment unit in response to the creation completion operation of the target deployment unit so as to store application data generated by the target application in the running process into the first logic volume and the second logic volume.
9. An electronic device, the electronic device comprising:
One or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, causes the one or more processors to implement the data storage method of any of claims 1-7.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements a data storage method according to any of claims 1-7.
CN202310573947.0A 2023-05-19 2023-05-19 Data storage method, device, equipment and storage medium Pending CN116661686A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310573947.0A CN116661686A (en) 2023-05-19 2023-05-19 Data storage method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310573947.0A CN116661686A (en) 2023-05-19 2023-05-19 Data storage method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116661686A true CN116661686A (en) 2023-08-29

Family

ID=87712913

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310573947.0A Pending CN116661686A (en) 2023-05-19 2023-05-19 Data storage method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116661686A (en)

Similar Documents

Publication Publication Date Title
CN108537543B (en) Parallel processing method, device, equipment and storage medium for blockchain data
US20200073709A1 (en) Method and apparatus for scheduling task, device and medium
US9880886B2 (en) Framework to improve parallel job workflow
US10263907B2 (en) Managing virtual network ports
US9665154B2 (en) Subsystem-level power management in a multi-node virtual machine environment
US20140096139A1 (en) Workload management considering hardware reliability
US20120173653A1 (en) Virtual machine migration in fabric attached memory
CN103970520A (en) Resource management method and device in MapReduce framework and framework system with device
US8205207B2 (en) Method of automated resource management in a partition migration capable environment
CN111679911B (en) Management method, device, equipment and medium of GPU card in cloud environment
US8352702B2 (en) Data processing system memory allocation
CN103118073A (en) Virtual machine data persistence storage system and method in cloud environment
CN109032788B (en) Reserved resource pool dynamic dispatching method, device, computer equipment and storage medium
US9755986B1 (en) Techniques for tightly-integrating an enterprise storage array into a distributed virtualized computing environment
CN114510321A (en) Resource scheduling method, related device and medium
CN112995261A (en) Configuration method and device of service table, network equipment and storage medium
CN115576654A (en) Request processing method, device, equipment and storage medium
CN114490062A (en) Local disk scheduling method and device, electronic equipment and storage medium
CN113806097A (en) Data processing method and device, electronic equipment and storage medium
US11010149B2 (en) Shared middleware layer containers
CN116661686A (en) Data storage method, device, equipment and storage medium
US8543687B2 (en) Moving deployment of images between computers
US11893407B2 (en) Overlay container storage driver for microservice workloads
CN107656702A (en) Accelerate the method and its system and electronic equipment of disk read-write
CN116560578A (en) Data storage method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination