WO2022001203A1 - 镜像分发方法、电子设备及存储介质 - Google Patents

镜像分发方法、电子设备及存储介质 Download PDF

Info

Publication number
WO2022001203A1
WO2022001203A1 PCT/CN2021/081632 CN2021081632W WO2022001203A1 WO 2022001203 A1 WO2022001203 A1 WO 2022001203A1 CN 2021081632 W CN2021081632 W CN 2021081632W WO 2022001203 A1 WO2022001203 A1 WO 2022001203A1
Authority
WO
WIPO (PCT)
Prior art keywords
image
storage location
data
file
layer
Prior art date
Application number
PCT/CN2021/081632
Other languages
English (en)
French (fr)
Inventor
王党华
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to JP2022581580A priority Critical patent/JP2023532138A/ja
Priority to EP21833429.0A priority patent/EP4174645A1/en
Priority to US18/003,972 priority patent/US20230269295A1/en
Publication of WO2022001203A1 publication Critical patent/WO2022001203A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to an image distribution method, a server, and a storage medium.
  • the image warehouse is an important network element in the virtualization technology, and its function is to store various image files (Image) of the user. Images are stored in layers in the image repository, and different images are identified through different reference relationships (links). That is to say, an image is not stored in the image warehouse as a file, but as a series of layers and links. This is a special file structure, which can share data at all layers and reduce storage space.
  • image distribution is often based on an open source application container engine, that is, the docker system: first, from the source image repository Pull an image file, tag the image, and then push the image file to the target image repository corresponding to the new tag. Since the image distribution in this way needs to pull the complete image file to the local, it occupies a high network bandwidth and the distribution efficiency is low; When two distribution tasks correspond to the same image file, conflict of image files is likely to occur.
  • an open source application container engine that is, the docker system: first, from the source image repository Pull an image file, tag the image, and then push the image file to the target image repository corresponding to the new tag. Since the image distribution in this way needs to pull the complete image file to the local, it occupies a high network bandwidth and the distribution efficiency is low; When two distribution tasks correspond to the same image file, conflict of image files is likely to occur.
  • the purpose of the embodiments of the present application is to provide an image distribution method, a server, and a storage medium, and through the new image distribution method, the efficiency and stability of the image distribution process are improved.
  • the embodiments of the present application provide a method for distributing an image, including: obtaining a distribution request for an image file; identifying the storage location of the image file from the source image repository of the image file; according to the storage location of the image file Distribute the image file to the target mirror repository.
  • Embodiments of the present application also provide a server, including: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor.
  • the processor executes to enable at least one processor to execute the application distribution method described above.
  • Embodiments of the present application further provide a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the foregoing application distribution method is implemented.
  • FIG. 1 is a flowchart of an image distribution method according to the first embodiment of the present application.
  • FIG. 2 is a flowchart of a method for distributing an image according to a second embodiment of the present application.
  • FIG. 3 is a flowchart of a method for distributing an image according to a third embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an image distribution apparatus according to a fourth embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an image distribution apparatus according to a fourth embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a server according to a fifth embodiment of the present application.
  • the first embodiment of the present application relates to a method for distributing an image, obtaining a distribution request of an image file; identifying the first storage location of data of each layer of the image file in the source image warehouse; The technical means of distributing the data of each layer from the source mirror warehouse to the target mirror warehouse.
  • the mirror distribution is performed after identifying the storage location of the data of each layer of the mirror file, so that the mirror does not need to be pulled to the local.
  • Pushing to the target image repository significantly improves the efficiency of image distribution, avoids file conflicts that may occur after pulling image files to the local area, and improves the stability of the image distribution process.
  • FIG. 1 The specific process of this embodiment is shown in FIG. 1 , and specifically includes the following steps.
  • Step 101 obtaining a distribution request of the image file.
  • the image file mentioned in this embodiment is the image file requested in the distribution request, that is, the image file to be distributed.
  • IDServer Image Distribute Server, server of image distribution system
  • DClient Image Distribute Client, client of image distribution system.
  • the IDClient that can be used includes: Web (web client), App (mobile terminal application), command line binary program, command line script, etc.
  • the execution body in this embodiment is the IDServer, which can be deployed on the same virtual node or the same virtual machine node as the IDClient, and has the function of managing and controlling the mirror warehouse.
  • the image distribution request carries at least the name of the image file to be distributed or an image list including the names of multiple image files to be distributed, as well as the address of the source image repository and the address of the target image repository.
  • Step 102 Identify the first storage location of the data of each layer of the image file in the source image repository.
  • the image identification is performed in the source image warehouse, that is, the name of the image file in the distribution request and the address of the source image warehouse are parsed.
  • the storage structure identifies, from the mirror warehouse, the storage locations of the data of each layer of the image file to be distributed in the source mirror warehouse, that is, the first storage location.
  • the data of each layer of the image file, that is, the underlying data is determined by the special storage structure of the image file in the image warehouse, and the underlying data includes but is not limited to repositories, blobs, layers, manifests, etc.
  • repositories are used to store the basic information of the image, including tenants, labels, reference relationships, etc.; blobs are used to store the actual data of each layer of the image; layers are used to store the reference relationship of an image to the actual data layer; manifests are used to store a certain image. The label of the mirror and the reference relationship of each label to the actual data layer. After identifying the underlying data of the image file in the source image warehouse, the underlying data of the image file is locked, that is, the underlying data is saved.
  • the storage of the underlying data may be temporary, for example, the underlying data is written into the random access memory RAM of the server, that is, the volatile memory, which is released after the current image distribution operation is performed.
  • the memory space occupied; in addition, the underlying data can also be persistent, such as writing the underlying data to non-volatile storage such as the database, local disk of the server, cloud storage space, etc., so as to make the subsequent verification process of the image file Or other distribution operations of the image file do not need to identify the storage location of the image file again, thereby improving the efficiency of image file distribution.
  • Step 103 Distribute the data of each layer of the image file from the source image repository to the target image repository according to the first storage location.
  • the file data distributed to the target image repository still conforms to the specific structure of image storage, that is, the image files distributed to the target image repository are consistent with the storage structure of the image files in the source image repository.
  • the underlying data is also consistent.
  • the first embodiment of the present application provides a method for distributing an image, by obtaining a distribution request of an image file; identifying the first storage location of data of each layer of the image file in the source image warehouse; The technical means of distributing the data of each layer of the image file from the source image warehouse to the target image warehouse.
  • the image distribution is performed after identifying the storage location of the data of each layer of the image file, so that the image does not need to be pulled. It is pushed to the target mirror warehouse after being local, so that when the tasks of multiple mirror distribution requests are carried out at the same time, the processing efficiency of the mirror distribution system server for the distribution request is significantly improved, and at the same time, it avoids the possibility of pulling the mirror file to the local.
  • File conflicts improve the stability of the image distribution process.
  • the second embodiment of the present application relates to an image distribution method.
  • the second embodiment is substantially the same as the first embodiment.
  • FIG. 2 A specific flow chart of the electronic seal application method in this embodiment is shown in FIG. 2 , which specifically includes the following steps.
  • Step 201 obtaining a distribution request of an image file.
  • Step 202 Identify the first storage location of the data of each layer of the image file in the source image repository.
  • Steps 201 and 202 in this embodiment are the same as steps 101 and 102 in the first embodiment of the present application, and the relevant implementation details have been specifically described in the first embodiment, which will not be repeated here.
  • Step 203 judging whether there is a mirror file identical to the mirror file in the target mirror warehouse; if there is no mirror file identical to the mirror file in the target mirror warehouse, then step 204 is executed, according to the first storage location, the mirror file is stored. The data of each layer of the file is distributed from the source mirror warehouse to the target mirror warehouse; otherwise, the mirror distribution process ends.
  • the transmission resource reduces the bandwidth occupation and further improves the speed of image distribution.
  • the specific manner of determining that the image file identical to the image file does not exist in the target image repository is as follows:
  • the image name of the image file to be distributed is retrieved in the target image repository, that is, it is identified whether there is an image file with the same name as the image file to be distributed in the target image repository.
  • the target image repository When there is no mirror file with the same name as the mirror file in the target mirror warehouse, it is determined that there is no mirror file with the same name as the mirror file to be distributed in the target mirror warehouse.
  • the file characteristics of the image file are obtained from the data of each layer of the image file.
  • the file characteristics compared here include, but are not limited to, the data quantity, size, md5 code, sha256 code, etc. of the image file.
  • the specific operation of distributing the data of each layer of the image file from the source image repository to the target image repository can be as follows: Copy each layer of the image file to be distributed from the first storage location. layer data, and store each layer data of the copied mirror file in the second storage location in an overwriting manner.
  • image distribution is performed in this way, the data distributed to the target image repository still automatically conforms to the specific structure of image storage.
  • the present embodiment provides a method for distributing an image.
  • the image file in the target image warehouse with the same name as the image file to be distributed is identified, and when the exact same image file exists, the image distribution operation is not performed. , thereby reducing the bandwidth occupied by data transmission, significantly improving the processing efficiency when multiple distribution requests are concurrent, and avoiding the file conflict problem of the same image file in the target image warehouse after the distribution is completed.
  • the third embodiment of the present application relates to an image distribution method, and the third embodiment is substantially the same as the first embodiment.
  • the third storage location and the first storage location of the data of each layer of the distributed mirror file are checked. If they match, it indicates that the image distribution is successful, and the image distribution process ends; if the two do not match, it means that an error occurred in the distribution process of the image file.
  • Distributed to the target mirror repository This embodiment ensures the accuracy of image file distribution by verifying the distributed files, and further improves the stability of the image distribution process.
  • FIG. 3 A specific flowchart of the image distribution method in this embodiment is shown in FIG. 3 , and specifically includes the following steps.
  • Step 301 obtaining a distribution request of the image file.
  • Step 302 identifying the first storage location of the data of each layer of the image file in the source image repository.
  • Step 303 it is judged whether a mirror file identical to the mirror file exists in the target mirror warehouse. If the image file identical to the image file does not exist in the target image warehouse, step 304 is executed, and according to the first storage location, the data of each layer of the image file is distributed from the source image warehouse to the target image warehouse; otherwise, the image distribution process ends. .
  • Steps 301 to 304 in this embodiment are substantially the same as steps 301 to 304 in the second embodiment, and the relevant implementation details have been specifically described in the second embodiment, which will not be repeated here.
  • Step 305 Verify whether the data of each layer stored in the third storage location of the distributed image file matches the data of each layer stored in the first storage location. If it is verified that the data of each layer stored in the third storage location does not match the data of each layer stored in the first storage location, the distribution process ends; The data of each layer is distributed from the source mirror warehouse to the target mirror warehouse.
  • the third storage location of the data of each layer of the distributed image file in the target image repository is identified. Then, it is checked whether the data of each layer stored in the third storage location is consistent with the data of each layer stored in the first storage location. If it is verified that the data of each layer stored in the third storage location does not match the data of each layer stored in the first storage location, step 304 is performed again.
  • the verification of the data of each layer of the mirror file in this embodiment is similar to the verification process in the second embodiment, and the file characteristics of the two mirror files are also compared, such as the data quantity, size, md5 code, sha256 code, etc.
  • the distributed image file in the target image repository is different from the image file in the source image repository in any file characteristic, it means that the stored data of the two do not match.
  • the user can set the upper limit of the number of times to redistribute images in the image distribution system server.
  • an error message is sent to the administrator for the administrator to check whether the system exists. Other errors avoid the image distribution process falling into a loop error and wasting system resources.
  • the storage address information of the image file needs to be persisted, after identifying the first storage location of the data of each layer of the image file in the source image repository, and after identifying the image file with the same name After the data of each layer of the image file is in the second storage location in the target mirror warehouse, write the first storage location and the second storage location into non-volatile storage, such as database, server local disk, cloud storage space, etc. .
  • step 304 when step 304 is re-executed after the judgment is made after step 305, the first storage location that is saved is first obtained from the non-volatile memory.
  • the first storage location that is saved is first obtained from the non-volatile memory.
  • the data distribution process ends; otherwise, step 304 is executed again.
  • the present embodiment provides a method for distributing an image. After the image distribution is completed, it is checked whether the data of each layer of the distributed image file in the target image repository is consistent with the data of each layer of the image file in the source image repository to ensure that the image is mirrored. The accuracy of file distribution further improves the stability of the image distribution process.
  • the fourth embodiment of the present application provides an image distribution apparatus, as shown in FIG. 4 , including:
  • the receiving module 401 is configured to obtain the distribution request of the image file, and send the image name to the control module after parsing the image name.
  • the control module 402 is configured to identify the first storage location of the data of each layer of the image file to be distributed in the source image repository.
  • it is also used to identify the second storage location in the target mirror repository for the data of each layer of the image file with the same name as the image file to be distributed.
  • it is also used to identify the third storage location of the data of each layer of the distributed image file in the target image repository.
  • the first storage location and the second storage location are respectively written into non-volatile memory, such as a database, a local disk of the server, a cloud storage space, and the like.
  • the verification module 403 is configured to determine, according to the first storage location and the second storage location identified by the control module 402 , that there is no mirror file identical to the mirror file in the target mirror warehouse, and send the verification result to the distribution module 404 .
  • it is also used to obtain the first storage location and/or the second storage location from the non-volatile memory.
  • it is also used to verify whether the third storage location of the data of each layer of the distributed image file matches the first storage location, and send the verification result to the distribution module 404 .
  • the distribution module 404 is configured to distribute the data of each layer of the image file from the source image repository to the target image repository according to the verification result sent by the verification module and the first storage location.
  • the receiving module 501 is connected to the client, and is used for receiving the image distribution request issued by the user through the client.
  • control module 502, the verification module 503 and the distribution module 504 are all connected in communication with the source mirror repository and the target mirror repository at the same time.
  • this embodiment is a device embodiment corresponding to the first, second or third embodiment, and this embodiment can be implemented in cooperation with the first or second embodiment.
  • the related technical details mentioned in the first, second or third embodiments are still valid in this embodiment, and are not repeated here in order to reduce repetition.
  • the relevant technical details mentioned in this embodiment can also be applied in the first, second or third embodiment.
  • a logical unit may be a physical unit, a part of a physical unit, or multiple physical units.
  • a composite implementation of the unit in order to highlight the innovative part of the present application, this embodiment does not introduce units that are not closely related to solving the technical problem raised by the present application, but this does not mean that there are no other units in this embodiment.
  • the fifth embodiment of the present application relates to a server, as shown in FIG. 6 , comprising: at least one processor 601; and a memory 602 connected in communication with the at least one processor 601; wherein the memory 602 stores data that can be processed by the at least one processor 601.
  • the instructions are executed by the processor 601, and the instructions are executed by the at least one processor 601, so that the at least one processor 601 can execute the above-mentioned electronic seal application method.
  • the memory and the processor are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors and various circuits of the memory.
  • the bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface between the bus and the transceiver.
  • a transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium.
  • the data processed by the processor is transmitted on the wireless medium through the antenna, and in this embodiment, the antenna also receives the data and transmits the data to the processor.
  • the processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Instead, memory may be used to store data used by the processor in performing operations.
  • the fifth embodiment of the present application relates to a computer-readable storage medium storing a computer program.
  • the above method embodiments are implemented when the computer program is executed by the processor.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例涉及通信技术领域，公开了一种镜像分发方法、服务器及存储介质。通过获取镜像文件的分发请求；识别出镜像文件的各层数据在源镜像仓库中的第一存储位置；根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库的技术手段，在需要进行镜像分发时，对镜像文件的各层数据的存储位置进行识别后进行镜像分发，无需将镜像拉取到本地后再推送至目标镜像仓库。

Description

镜像分发方法、电子设备及存储介质 技术领域
本申请实施例涉及通信领域，特别涉及一种镜像分发方法、服务器及存储介质。
背景技术
随着IT技术日新月异的发展，由于具有方便、简单、成本低、安全性高的特点，虚拟化技术在计算机领域应用的范围越来越广泛。其中，镜像仓库便是虚拟化技术中一个重要的网元，它的作用是用来存储用户的各类镜像文件(Image)。镜像在镜像仓库中是分层(Layers)存储的，并通过不同的引用关系(link)来识别不同的镜像。也就是说，一个镜像并不是以一个文件、而是以一系列Layers和links存放在镜像仓库，这是一种特殊的文件结构，它可以使各层数据进行共享，减少存储空间。
在镜像的使用过程中，用户常常需要在多个镜像仓库之间进行镜像分发，在一些情形下常常是基于一种开源的应用容器引擎，即docker系统来完成镜像分发：首先从源镜像仓库中拉取一个镜像文件，给镜像打上标签后再将镜像文件推送到新标签对应的目标镜像仓库。由于采用这种方式来进行镜像分发需要将完整的镜像文件拉取到本地，因此对网络带宽的占用较高，分发效率较低；此外，由于镜像文件往往在本地需要存储一定的时间，当多个分发任务对应于同一镜像文件时，容易发生镜像文件的冲突。
发明内容
本申请实施例的目的在于提供一种镜像分发方法、服务器及存储介质，通过新的镜像分发方法，提高镜像分发过程的效率与稳定性。
为解决上述技术问题，本申请的实施例提供了一种镜像分发方法，包括：获取镜像文件的分发请求；从镜像文件的源镜像仓库中识别出镜像文件的存储位置；根据镜像文件的存储位置将镜像文件分发至目标镜像仓库。
本申请的实施例还提供了一种服务器，包括：至少一个处理器；以及，与至少一个处理器通信连接的存储器；其中，存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行上述的应用分发方法。
本申请的实施例还提供了一种计算机可读存储介质，存储有计算机程序，计算机程序被处理器执行时实现上述的应用分发方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定。
图1是根据本申请第一实施例中的镜像分发方法的流程图。
图2是根据本申请第二实施例中的镜像分发方法的流程图。
图3是根据本申请第三实施例中的镜像分发方法的流程图。
图4是根据本申请第四实施例中的镜像分发装置的结构示意图。
图5是根据本申请第四实施例中的镜像分发装置的结构示意图。
图6是根据本申请第五实施例中的服务器的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施例进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施例中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施例的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
本申请的第一实施例涉及一种镜像分发方法，获取镜像文件的分发请求；识别出镜像文件的各层数据在源镜像仓库中的第一存储位置；根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库的技术手段，在需要进行镜像分发时，对镜像文件的各层数据的存储位置进行识别后进行镜像分发，从而无需将镜像拉取到本地后再推送至目标镜像仓库，使得镜像分发的效率显著提升，同时避免了拉取镜像文件到本地后可能产生的文件冲突，提高了镜像分发过程的稳定性。
下面对本实施例的电子印章应用方法的实现细节进行说明，以下内容仅为方便理解而提供的实现细节，并非实施本方案的必须。
本实施例的具体流程如图1所示，具体包括以下步骤。
步骤101，获取镜像文件的分发请求。
具体地说，本实施例中提到的镜像文件为分发请求中请求的镜像文件，即待分发的镜像文件。当用户需要在多个镜像仓库间进行镜像分发时，通过DClient(Image Distribute Clien，镜像分发系统客户端)发送镜像文件的分发请求给IDServer(Image Distribute Server，镜像分发系统服务端)。可以使用的IDClient包括：Web(网页客户端)、App(移动终端应用程序)、命令行二进制程序、命令行脚本等。本实施例中的执行主体为IDServer，可以与IDClient部署在相同的虚拟节点上或相同的虚机节点上，起到对镜像仓库进行管理与控制的功能。其中，镜像分发请求中至少携带有待分发的镜像文件的名称或包括多个待分发镜像文件的名称的镜像列表，以及源镜像仓库的地址和目标镜像仓库的地址。
步骤102，识别出镜像文件的各层数据在源镜像仓库中的第一存储位置。
具体地说，在接收到来自IDServer的镜像文件的分发请求后，在源镜像仓库进行镜像识别，即解析分发请求中的镜像文件名称以及源镜像仓库的地址，同时结合镜像在镜像仓库中特殊的存储结构，从镜像仓库中识别出待分发的镜像文件的各层数据在源镜像仓库中的存储位置，即第一存储位置。其中，镜像文件的各层数据，即底层数据，是由镜像文件在镜像仓库中特殊的存储结构来确定的，底层数据包括但不限于repositories、blobs、layers、manifests等。其中，repositories用于存放镜像的基础信息，包括租户、标签、引用关系等；blobs用于存储镜像各层的实际数据；layers用于存储某镜像对实际数据层的引用关系； manifests用于存储某镜像的标签及各标签对实际数据层的引用关系。在识别出源镜像仓库中镜像文件的底层数据后，对镜像文件的底层数据进行锁定，即对底层数据进行保存。
在一个例子中，对底层数据的保存可以是临时性的，例如将底层数据写入服务器的随机存取存储器RAM中，即易失性存储器，在执行完本次的镜像分发操作后就释放其占用的内存空间；此外，对底层数据也可以是持久性的，例如将底层数据写入数据库、服务器本地的磁盘、云端存储空间等非易失性存储器，从而使得后续对镜像文件的校验过程或对该镜像文件的其他分发操作无需再次对镜像文件的存储位置进行识别，从而提高镜像文件分发的效率。
步骤103，根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库。
具体的说，对镜像文件进行分发时，分发到目标镜像仓库的文件数据仍然符合镜像存储的特定结构，即分发至目标镜像仓库的镜像文件与源镜像仓库中镜像文件的存储结构保持一致，其底层数据也是一致的。
由此，本申请第一实施例提供了一种镜像分发方法，通过获取镜像文件的分发请求；识别出镜像文件的各层数据在源镜像仓库中的第一存储位置；根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库的技术手段，在需要进行镜像分发时，对镜像文件的各层数据的存储位置进行识别后进行镜像分发，从而无需将镜像拉取到本地后再推送至目标镜像仓库，使得当多个镜像分发请求的任务同时进行时镜像分发系统服务端对于分发请求的处理效率得到显著提升，同时避免了拉取镜像文件到本地后可能产生的文件冲突，提高了镜像分发过程的稳定性。
本申请的第二实施例涉及镜像分发方法，第二实施例与第一实施例大致相同，在本实施例中，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库之前，识别目标镜像仓库中是否不存在与待分发的镜像文件相同的镜像文件，当识别结果为是则执行将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库；否则不执行镜像文件的分发操作。通过对目标镜像仓库中镜像文件的审核，避免了镜像分发时进行不必要的数据传输操作。
本实施例中的电子印章应用方法的具体流程图如图2所示，具体包括以下步骤。
步骤201，获取镜像文件的分发请求。
步骤202，识别出镜像文件的各层数据在源镜像仓库中的第一存储位置。
本实施例中的步骤201和步骤202与本申请第一实施例中的步骤101和步骤102相同，相关的实施细节已在第一实施例中进行具体说明，在此不再赘述。
步骤203，判断目标镜像仓库中是否存在与所述镜像文件相同的镜像文件；若目标镜像仓库中不存在与所述镜像文件相同的镜像文件，则执行步骤204，根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库；否则结束镜像分发流程。
具体地说，当目标镜像仓库中存在与待分发的镜像文件相同的镜像文件时，表示镜像仓库中已经存在用户所请求的镜像文件，因此无需进行镜像分发的操作，节省了虚机环境下的传输资源，减少了带宽占用从而进一步地提高了镜像分发的速度，当多个镜像分发请求的任务同时进行时，显著提高镜像分发系统服务端对于分发请求的处理效率。
在一个例子中，确定目标镜像仓库中不存在与所述镜像文件相同的镜像文件的方式具体 如下：
首先在目标镜像仓库中检索待分发的镜像文件的镜像名称，即识别目标镜像仓库中是否存在与待分发的镜像文件同名的镜像文件。当目标镜像仓库中不存在与镜像文件同名的镜像文件，则确定目标镜像仓库中不存在与待分发的镜像文件相同的镜像文件，此时执行根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库。
当目标镜像仓库中存在与镜像文件同名的镜像文件时，则需要进一步地识别与镜像文件同名的镜像文件的各层数据在目标镜像仓库中的存储位置，即第二存储位置。然后比较第二存储位置与第一存储位置中存储的各层数据，若第二存储位置存储的各层数据与第一存储位置存储的各层数据不匹配，则确定目标镜像仓库中不存在与待分发的镜像文件相同的镜像文件，此时执行根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库；否则最终确定目标镜像仓库中存在与待分发的镜像文件相同的镜像文件，结束镜像分发的流程。
在本实施例中，从镜像文件的各层数据中获取镜像文件的文件特征，当目标镜像仓库中与待分发的镜像文件同名的镜像文件的文件特征与待分发的镜像文件的文件特征一致时，则判定两者为相同的镜像文件。这里所比较的文件特征包括但不限于镜像文件的数据数量、大小、md5码、sha256码等。当其中任一项文件特征存在差异时，则判定两者为不同的镜像文件。
在一个例子中根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库这一具体的具体操作可以采用以下方式：从第一存储位置复制待分发的镜像文件的各层数据，并将复制的镜像文件的各层数据以覆盖方式存储在所述第二存储位置。通过此种方式进行镜像分发时，分发到目标镜像仓库的数据仍然自动符合镜像存储的特定结构。
由此，本实施例提供了一种镜像分发方法，在镜像分发之前对目标镜像仓库中与待分发的镜像文件的同名镜像文件进行识别，当存在完全相同的镜像文件时，不进行镜像分发操作，从而减少数据传输所占用的带宽，使得多分发请求并发时的处理效率得到显著提高，同时也能够避免分发完成后，相同镜像文件在目标镜像仓库中发生的文件冲突问题。
此外，本领域技术人员可以理解，上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请第三实施例涉及一种镜像分发方法，第三实施例与第一实施例大致相同。在本实施例中，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库后，对分发后的镜像文件的各层数据的第三存储位置与第一存储位置进行校验，若两者匹配则标识镜像分发成功，结束镜像分发流程；若两者不匹配，表示镜像文件在分发过程中发生了错误，则重新执行根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库。本实施例通过对分发后的文件进行校验，保证镜像文件分发的准确度，进一步地提高了镜像分发过程的稳定性。
本实施例中的镜像分发方法的具体流程图如图3所示，具体包括以下步骤。
步骤301，获取镜像文件的分发请求。
步骤302，识别出镜像文件的各层数据在源镜像仓库中的第一存储位置。
步骤303，判断目标镜像仓库中是否存在与所述镜像文件相同的镜像文件。若目标镜像仓库中不存在与所述镜像文件相同的镜像文件，则执行步骤304，根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库；否则结束镜像分发流程。
本实施例中的步骤301至步骤304与第二实施例中的步骤301至步骤304大致相同，相关的实施细节已在第二实施例中具体说明，在此不再赘述。
步骤305，校验分发后镜像文件在第三存储位置的存储的各层数据与第一存储位置存储的各层数据是否匹配。若校验出所述第三存储位置存储的各层数据与所述第一存储位置存储的各层数据不匹配，则结束分发流程；否则重新执行步骤304，根据第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库。
具体地说，在镜像文件的分发完成后，识别分发后的镜像文件的各层数据在目标镜像仓库中的第三存储位置。然后校验第三存储位置存储的各层数据与第一存储位置存储的各层数据是否一致。若校验出第三存储位置存储的各层数据与第一存储位置存储的各层数据不匹配，则重新执行步骤304。通过对分发后镜像文件的存储数据进行校验，保证了分发后镜像文件的数据不存在丢失或错误，进一步地提高了镜像分发过程中镜像文件的稳定性。
在本实施例中，本实施例中对镜像文件各层数据的校验与第二实施例中的校验过程类似，同样是比较两个镜像文件的文件特征，如文件的数据数量、大小、md5码、sha256码等。当目标镜像仓库中分发后的镜像文件与源镜像库中的镜像文件中的任一项文件特征存在差异时，则表示两者的存储数据不匹配。
另外，用户可以在镜像分发系统服务端中设置重新分发镜像的次数上限，当镜像分发多次发生错误时，考虑到可能是系统出现问题，向管理员推送错误消息，供管理员检查系统是否存在其他错误，避免镜像分发流程陷入循环错误中，浪费系统资源。
在一个例子中，当需要持久性地保存镜像文件的存储地址信息时，可以在识别出镜像文件的各层数据在源镜像仓库中的第一存储位置之后，以及，在识别出与镜像文件同名的镜像文件的各层数据在目标镜像仓库中的第二存储位置之后，分别将第一存储位置和第二存储位置写入非易失性存储器，如数据库、服务器本地的磁盘、云端存储空间等。
在本实施例中，当在步骤305后进行判断后重新执行步骤304时，首先从非易失性存储器中获取得到保存的第一存储位置。除了可以直接识别分发后的镜像文件在目标镜像仓库中的第三存储位置，还可以从非易失性存储器中获取之前保存的第二存储位置，然后校验在第一存储位置存储的各层数据与第二存储位置或第三存储位置存储的各层数据是否一致，从而完成分发后镜像文件的校验过程，当第一存储位置存储的各层数据与第二存储位置或第三存储位置存储的各层数据一致时，则结束数据分发流程；否则再次重新执行步骤304。
由此，本实施例提供了一种镜像分发方法，在镜像分发完成后，校验目标镜像仓库中分发后镜像文件的各层数据与源镜像仓库中镜像文件的各层数据是否一致，保证镜像文件分发的准确度，进一步地提高了镜像分发过程的稳定性。
本申请第四实施例提供一种镜像分发装置，如图4所示，包括。
接收模块401，用于获取镜像文件的分发请求，并在解析出镜像名称后将镜像名称发送至控制模块。
控制模块402，用于识别出待分发的镜像文件的各层数据在源镜像仓库中的第一存储位置。
在一个例子中，还用于识别与待分发的镜像文件同名的镜像文件的各层数据在目标镜像仓库中的第二存储位置。
在一个例子中，还用于识别分发后的镜像文件的各层数据在目标镜像仓库中的第三存储位置。
在一个例子中，还用于在识别出镜像文件的各层数据在源镜像仓库中的第一存储位置之后，以及，在识别出与镜像文件同名的镜像文件的各层数据在目标镜像仓库中的第二存储位置之后，分别将第一存储位置和第二存储位置写入非易失性存储器，如数据库、服务器本地的磁盘、云端存储空间等。
校验模块403，用于根据控制模块402识别出的第一存储位置以及第二存储位置来确定目标镜像仓库中不存在与镜像文件相同的镜像文件，并将校验结果发送至分发模块404。
在一个例子中，还用于从非易失性存储器中获取第一存储位置和/或第二存储位置。
在一个例子中，还用于校验分发后的镜像文件的各层数据的第三存储位置与第一存储位置是否匹配，并将校验结果发送至分发模块404。
分发模块404，用于根据校验模块发送的校验结果以及第一存储位置，将镜像文件的各层数据从源镜像仓库分发至目标镜像仓库。
在具体应用中，本实施例中镜像装置的结构与交互关系如图5所示。其中，接收模块501与客户端相连，用于接收用户通过客户端下发的镜像分发请求。
控制模块502、校验模块503以及分发模块504均同时与源镜像仓库和目标镜像仓库通信连接。
不难发现，本实施例为与第一、第二或第三实施例相对应的装置实施例，本实施例可与第一或第二实施例互相配合实施。第一、第二或第三实施例中提到的相关技术细节在本实施例中依然有效，为了减少重复，这里不再赘述。相应地，本实施例中提到的相关技术细节也可应用在第一、第二或第三实施例中。
值得一提的是，本实施例中所涉及到的各模块均为逻辑模块，在实际应用中，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现。此外，为了突出本申请的创新部分，本实施例中并没有将与解决本申请所提出的技术问题关系不太密切的单元引入，但这并不表明本实施例中不存在其它的单元。
本申请第五实施例涉及一种服务器，如图6所示，包括：至少一个处理器601；以及，与至少一个处理器601通信连接的存储器602；其中，存储器602存储有可被至少一个处理器601执行的指令，指令被至少一个处理器601执行，以使至少一个处理器601能够执行上述的电子印章应用方法。
其中，存储器和处理器采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器和存储器的各种电路连接在一起。总线还可以将诸如外围设备、稳 压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器处理的数据通过天线在无线介质上进行传输，在本实施例中，天线还接收数据并将数据传送给处理器。
处理器负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器可以被用于存储处理器在执行操作时所使用的数据。
本申请第五实施例涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施例是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (11)

  1. 一种镜像分发方法，包括：
    获取镜像文件的分发请求；
    识别出所述镜像文件的各层数据在源镜像仓库中的第一存储位置；
    根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库。
  2. 根据权利要求1所述的镜像分发方法，其中，所述根据上述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库，包括：
    从所述第一存储位置复制所述镜像文件的各层数据，并将复制的所述镜像文件的各层数据存储在所述目标镜像仓库。
  3. 根据权利要求1所述的镜像分发方法，其中，在所述根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库之前，还包括：
    确定所述目标镜像仓库中不存在与所述镜像文件相同的镜像文件。
  4. 根据权利要求1所述的镜像分发方法，其中，所述确定所述目标镜像仓库中不存在所述镜像文件，包括：
    识别所述目标镜像仓库中是否存在与所述镜像文件同名的镜像文件；
    若所述目标镜像仓库中不存在与所述镜像文件同名的镜像文件，确定所述目标镜像仓库中不存在与所述镜像文件相同的镜像文件。
  5. 根据权利要求4所述的镜像分发方法，其中，所述确定所述目标镜像仓库中不存在所述镜像文件，还包括：
    若所述目标镜像仓库中存在与所述镜像文件同名的镜像文件，识别出所述与所述镜像文件同名的镜像文件的各层数据在所述目标镜像仓库中的第二存储位置；
    若所述第二存储位置存储的各层数据与所述第一存储位置存储的各层数据不匹配，确定所述目标镜像仓库中不存在所述镜像文件。
  6. 根据权利要求1至4中任一项所述的镜像分发方法，其中，所述根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库之后，还包括：
    识别分发后的镜像文件的各层数据在所述目标镜像仓库中的第三存储位置；
    若校验出所述第三存储位置存储的各层数据与所述第一存储位置存储的各层数据不匹配，重新执行所述根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库的步骤。
  7. 根据权利要求6所述的镜像分发方法，其中，在所述识别出所述镜像文件的各层数据 在源镜像仓库中的第一存储位置之后，还包括：
    将所述第一存储位置写入非易失性存储器；
    所述重新执行所述根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库的步骤中，所述第一存储位置从所述非易失性存储器获取得到。
  8. 根据权利要求5所述的镜像分发方法，其中，所述根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库，包括：
    从所述第一存储位置复制所述镜像文件的各层数据，并将复制的所述镜像文件的各层数据以覆盖方式存储在所述第二存储位置。
  9. 根据权利要求8所述的镜像分发方法，其中，在所述识别出所述与所述镜像文件同名的镜像文件的各层数据在所述目标镜像仓库中的第二存储位置之后，还包括：
    将所述第二存储位置写入非易失性存储器；
    所述根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库之后，还包括：
    从所述非易失性存储器获取所述第二存储位置；
    若校验出所述第二存储位置存储的各层数据与所述第一存储位置存储的各层数据不匹配，重新执行所述根据所述第一存储位置，将所述镜像文件的各层数据从所述源镜像仓库分发至目标镜像仓库的步骤。
  10. 一种服务器，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至9中任一项所述的镜像分发方法。
  11. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至9中任一项所述的镜像分发方法。
PCT/CN2021/081632 2020-06-30 2021-03-18 镜像分发方法、电子设备及存储介质 WO2022001203A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2022581580A JP2023532138A (ja) 2020-06-30 2021-03-18 イメージ配布方法、電子機器及び記憶媒体
EP21833429.0A EP4174645A1 (en) 2020-06-30 2021-03-18 Mirror image distribution method, electronic device, and storage medium
US18/003,972 US20230269295A1 (en) 2020-06-30 2021-03-18 Image distribution method, electronic device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010618603.3 2020-06-30
CN202010618603.3A CN113872999A (zh) 2020-06-30 2020-06-30 镜像分发方法、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2022001203A1 true WO2022001203A1 (zh) 2022-01-06

Family

ID=78981645

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/081632 WO2022001203A1 (zh) 2020-06-30 2021-03-18 镜像分发方法、电子设备及存储介质

Country Status (5)

Country Link
US (1) US20230269295A1 (zh)
EP (1) EP4174645A1 (zh)
JP (1) JP2023532138A (zh)
CN (1) CN113872999A (zh)
WO (1) WO2022001203A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105740048A (zh) * 2016-01-26 2016-07-06 华为技术有限公司 一种镜像管理方法、装置及系统
CN106506587A (zh) * 2016-09-23 2017-03-15 中国人民解放军国防科学技术大学 一种基于分布式存储的Docker镜像下载方法
CN106776149A (zh) * 2017-01-04 2017-05-31 郑州云海信息技术有限公司 本地容器镜像上传至镜像仓库的方法及系统
CN107566195A (zh) * 2017-10-23 2018-01-09 中国联合网络通信集团有限公司 镜像仓库处理方法及系统
CN108322496A (zh) * 2017-01-17 2018-07-24 北京京东尚科信息技术有限公司 镜像文件分发方法及系统、计算机可读存储介质、电子设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11288377B1 (en) * 2019-10-03 2022-03-29 Pavel Izhutov Virtual machine-based trusted execution environment
US11093221B1 (en) * 2020-02-14 2021-08-17 Red Hat, Inc. Automatic containerization of operating system distributions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105740048A (zh) * 2016-01-26 2016-07-06 华为技术有限公司 一种镜像管理方法、装置及系统
CN106506587A (zh) * 2016-09-23 2017-03-15 中国人民解放军国防科学技术大学 一种基于分布式存储的Docker镜像下载方法
CN106776149A (zh) * 2017-01-04 2017-05-31 郑州云海信息技术有限公司 本地容器镜像上传至镜像仓库的方法及系统
CN108322496A (zh) * 2017-01-17 2018-07-24 北京京东尚科信息技术有限公司 镜像文件分发方法及系统、计算机可读存储介质、电子设备
CN107566195A (zh) * 2017-10-23 2018-01-09 中国联合网络通信集团有限公司 镜像仓库处理方法及系统

Also Published As

Publication number Publication date
JP2023532138A (ja) 2023-07-26
CN113872999A (zh) 2021-12-31
US20230269295A1 (en) 2023-08-24
EP4174645A1 (en) 2023-05-03

Similar Documents

Publication Publication Date Title
US11561956B2 (en) Key pattern management in multi-tenancy database systems
CN109947773B (zh) 在多租户数据库系统中部署对键模式的改变
CN106506587B (zh) 一种基于分布式存储的Docker镜像下载方法
US11157517B2 (en) Versioned hierarchical data structures in a distributed data store
US11741046B2 (en) Method and apparatus for creating system disk snapshot of virtual machine
US10831720B2 (en) Cloud storage distributed file system
US10817498B2 (en) Distributed transactions in cloud storage with hierarchical namespace
US9779153B2 (en) Data transfer between storage systems using data fingerprints
EP3477500A1 (en) Deploying changes in a multi-tenancy database system
US10922303B1 (en) Early detection of corrupt data partition exports
US20140358859A1 (en) File sharing system and file sharing method
WO2019231689A1 (en) Multi-protocol cloud storage for big data and analytics
CN106789249B (zh) 热更新方法、客户端及服务器
US11403269B2 (en) Versioning validation for data transfer between heterogeneous data stores
CN111258976A (zh) 分布式锁实现方法、系统、设备及存储介质
US10620871B1 (en) Storage scheme for a distributed storage system
US20200153889A1 (en) Method for uploading and downloading file, and server for executing the same
US9588884B2 (en) Systems and methods for in-place reorganization of device storage
WO2022001203A1 (zh) 镜像分发方法、电子设备及存储介质
US11010408B2 (en) Hydration of a hierarchy of dehydrated files
WO2022194021A1 (zh) 并发控制方法、网卡、计算机设备、存储介质
US20220067065A1 (en) Providing instant and distributed access to a source blob via copy-on-read blobs and link blobs
CN110019057B (zh) 请求处理方法及装置
US20130297867A1 (en) Iterative disk upload based on differencing disk format
US11379147B2 (en) Method, device, and computer program product for managing storage system

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2022581580

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021833429

Country of ref document: EP

Effective date: 20230130