[go: up one dir, main page]

WO2019127971A1 - Procédé de synchronisation d'images pour registre d'images, système, dispositif et support d'informations - Google Patents

Procédé de synchronisation d'images pour registre d'images, système, dispositif et support d'informations Download PDF

Info

Publication number
WO2019127971A1
WO2019127971A1 PCT/CN2018/082251 CN2018082251W WO2019127971A1 WO 2019127971 A1 WO2019127971 A1 WO 2019127971A1 CN 2018082251 W CN2018082251 W CN 2018082251W WO 2019127971 A1 WO2019127971 A1 WO 2019127971A1
Authority
WO
WIPO (PCT)
Prior art keywords
mirror
warehouse
data access
access request
proxy server
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.)
Ceased
Application number
PCT/CN2018/082251
Other languages
English (en)
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.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen 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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2019127971A1 publication Critical patent/WO2019127971A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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
    • 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/50—Network services
    • H04L67/55—Push-based network services
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present application relates to the field of Docker technology, and in particular, to a mirror synchronization method, system, device and storage medium of a mirror warehouse.
  • Docker (Docker Is an open source application container engine that allows developers to package their applications and dependencies into a portable container and then publish them to any popular Linux On the machine, virtualization can also be implemented.
  • the container technology provided allows several containers to be run on the same host or virtual machine, each container being a separate virtual environment or application.
  • Container from Docker Image which can be generated by the user or submitted by the running container. After the image is generated, it can be pushed to the image repository for saving, or pulled from the mirror repository. Go to the local to run the container.
  • Docker provides an official image repository (Docker hub), while allowing users to build their own private image repository (private Registry). For most organizations and organizations, it is necessary to use a private image repository to protect the mirrored content and use of the repository.
  • Mirrors are stored in the file system as tiered storage. Different images may share some layers to save storage space. For warehouse construction involving multi-regional user access, mirror synchronization is a must-have when unified management of the image is required to ensure that the scope of the image used by the user is not limited to a certain area.
  • Mirror synchronization can be implemented by multiple schemes, one of which is shared storage, that is, a registry of multiple areas mounts a shared network storage disk, so that each time a mirror is pushed to a certain area of the registry. All the warehouses are immediately synchronized. However, sometimes the multi-region registry cannot share storage, and the networks between the regions cannot access each other, that is, the regions are isolated.
  • the present application provides a mirror synchronization method, system, device and storage medium for a mirror warehouse, which mainly solves the problem that the existing Docker images cannot be synchronized in real time.
  • a mirror synchronization method for a mirror warehouse comprising the following steps:
  • the host client in the available area initiates a data access request to the cloud management area warehouse through the proxy server of the available area;
  • the cloud management area warehouse parses the data access request, and when determining that the data access request is a mirror push request, notifying the host client of the available area to push the image to the cloud management area warehouse through the proxy server; determining that the data access request is a mirror pull request When you pull the required image from the cloud management area warehouse to the available area.
  • the method before the step of the host client in the available area to initiate a data access request to the cloud management area warehouse by using the proxy server of the available area, the method further includes:
  • the step of the host client in the available area initiating a data access request to the cloud management area warehouse by using the proxy server of the available area includes:
  • the host client in the available zone accesses the proxy server of the available zone through the domain name;
  • the proxy server performs secure transport layer protocol authentication according to the domain name, and sends the data access request of the host client to the cloud management area warehouse after the verification is passed.
  • the cloud management area warehouse parses the data access request, and when determining that the data access request is a mirror push request, notifying the host client of the available area to push the image to the cloud management area warehouse through the proxy server, and determining data access
  • the steps of pulling the required image from the cloud management area repository to the available area include:
  • the cloud management area warehouse receives a data access request sent by the proxy server and parses the data access request;
  • the host client of the available area is notified to push the image to the cloud management area warehouse through the proxy server; if the data access request is a mirror pull request, the image required by the request is searched, and the request is sent.
  • the proxy server pulls the image into the host client of the Availability Zone where the proxy server is located.
  • the mirror synchronization method of the mirror warehouse further includes:
  • the proxy server When the proxy server pushes the image to the cloud management area warehouse or the cloud management area warehouse to pull the image to the proxy server, the proxy server analyzes the size of the mirrored data, and prompts the mirror transmission failure when the mirrored data is larger than the upper limit of the data size preset by the proxy server. .
  • the number of the available areas is at least one, and each of the available areas is deployed with a set of proxy servers.
  • the domain name, certificate, and key of the proxy server for each Availability Zone are the same.
  • a mirror synchronization system of a mirror warehouse includes:
  • a host client and a proxy server, the host client being configured to initiate a data access request to the cloud management area repository through the proxy server of the available area;
  • the cloud management area warehouse is configured to parse the data access request, and when determining that the data access request is a mirror push request, notify the host client of the available area to push the image to the cloud management area warehouse through the proxy server; and determine that the data access request is When the image pull request is requested, the required image is pulled from the cloud management area repository to the available area for sending the request.
  • the host client is further configured to receive a mirroring event initiated by a user terminal of an available area where the host client is located, and generate a data access request according to the mirroring time, where the mirroring event includes Mirror push events and image pull events.
  • the proxy server is specifically configured to perform a secure transport layer protocol authentication according to the domain name when the host client accesses the proxy server of the available area through the domain name, and the host client is verified after the verification is passed.
  • the data access request of the end is sent to the cloud management area warehouse.
  • a mirror synchronization device of a mirrored warehouse comprising a processor, a memory, and a mirror synchronization program stored on the memory and executable by the processor, the image synchronization program being When executed, implement the following steps:
  • the host client in the available area initiates a data access request to the cloud management area warehouse through the proxy server of the available area;
  • the cloud management area warehouse parses the data access request, and when determining that the data access request is a mirror push request, notifying the host client of the available area to push the image to the cloud management area warehouse through the proxy server; determining that the data access request is a mirror pull request When you pull the required image from the cloud management area warehouse to the available area.
  • a storage medium storing a mirror synchronization program, the mirror synchronization program being executed by a processor, implementing the following steps:
  • the host client in the available area initiates a data access request to the cloud management area warehouse through the proxy server of the available area;
  • the cloud management area warehouse parses the data access request, and when determining that the data access request is a mirror push request, notifying the host client of the available area to push the image to the cloud management area warehouse through the proxy server; determining that the data access request is a mirror pull request When you pull the required image from the cloud management area warehouse to the available area.
  • the present application discloses a mirror synchronization method, system, device and storage medium of a mirror warehouse, and a host client of an available area initiates a data access request to a cloud management area warehouse through a proxy server of the available area; and then, the cloud management area warehouse parses the data. Accessing the request, and when determining that the data access request is a mirror push request, notifying the host client of the available area to push the image to the cloud management area warehouse through the proxy server; when determining that the data access request is a mirror pull request, the cloud management area warehouse Pull the desired image into the Availability Zone.
  • the present invention uniformly manages the mirroring of the available area by setting a centralized mirror warehouse in the cloud management area, so that no cross-area mirror synchronization is required, and various problems caused by other methods for synchronous mirroring are avoided. It does not cause the problem that the mirrored by the available area mirror library is not sent out, and only a mirrored warehouse is deployed in the cloud management area. Only one proxy server needs to be deployed in each available area, which saves deployment costs.
  • FIG. 1 is a flowchart of a preferred embodiment of a mirror synchronization method of a mirrored warehouse provided by the present application
  • step S100 is a flowchart of a preferred embodiment of step S100 in the mirror synchronization method of the mirrored warehouse provided by the present application;
  • step S200 is a flowchart of a preferred embodiment of step S200 in the mirror synchronization method of the mirrored warehouse provided by the present application;
  • FIG. 4 is a functional block diagram of a mirror synchronization system of a mirror warehouse provided by the present application.
  • the present application provides a mirror image synchronization method and system for a mirrored warehouse.
  • the objects, technical solutions, and advantages of the present application will be more clearly and clarified, and the present application will be further described in detail below with reference to the accompanying drawings. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.
  • FIG. 1 is a flowchart of a preferred embodiment of a mirror synchronization method of a mirrored warehouse provided by the present application.
  • the mirror synchronization method of the mirror warehouse according to the preferred embodiment of the present application has the following steps:
  • the host client in the available area initiates a data access request to the cloud management area warehouse through the proxy server of the available area.
  • a cloud management area and a plurality of available areas are set in the system, and the cloud management area is a centralized management area, and a cloud management area warehouse is deployed in the cloud management area, and is configured to manage all the mirrors, and each available area passes the proxy.
  • the server accesses the cloud management area warehouse, wherein each of the available areas is deployed with a set of proxy servers, and the host client of an available area can only access the cloud management area warehouse through the proxy server of the available area, wherein the proxy server is an Nginx proxy server.
  • Each available area can be set in different locations, such as Beijing, Shanghai, and Shenzhen.
  • Each available area can communicate with the cloud management area, but each available area is isolated from each other. This application does not have a mirror in each available area.
  • the proxy server is set in each available area, and the host clients of each available area access the cloud management area warehouse through the proxy server, thereby realizing the unified management of the mirror, so no cross-region mirror synchronization is required, and the deployment is saved. Cost, and does not result in mirroring due to the original Availability Zone Image Repository Issue caused the problem can not be synchronized.
  • the method further includes: receiving, by the host client in the available area, a mirroring event initiated by the user terminal of the available area, and generating a data access request according to the mirroring time, wherein the mirroring event includes a mirroring push event and Mirror pull event.
  • the user terminal initiates a mirroring event to the host client in the available area, specifically, pushing the image to the host user of the available area or initiating the image pull request, and the host client in the available area receives the image event and determines
  • the mirroring event is a mirroring event or a mirroring event, and generates a data access request. If it is a mirroring push event, the image is pushed to the cloud management area warehouse through the proxy server. If the image is pulled, the image is accessed through the proxy server. Warehouse, pull the required image from the cloud management warehouse.
  • Step S101 The host client in the available area accesses the proxy server of the available area by using a domain name
  • Step S102 The proxy server performs secure transport layer protocol authentication according to the domain name, and sends the data access request of the host client to the cloud management area warehouse after the verification is passed.
  • the host client in the available zone accesses the proxy server of the available zone through the domain name, and the DNS server resolves the domain name to the proxy server, and then the proxy server performs secure transport layer protocol verification (TLS authentication), and after the verification is passed,
  • TLS authentication secure transport layer protocol verification
  • the data access request is forwarded by the proxy server to the cloud management area warehouse, wherein the domain name, the certificate, and the key used by the proxy server of each available area are the same, and the certificate and the key pair are generated according to the domain name and the like, and when performing TLS verification, That is, if the verification certificate and the key pair are correct, and the verification is successful, the cloud management area warehouse can be accessed through the proxy server.
  • This application sets the domain name, certificate, and key of the proxy server of each available area to be consistent, thereby making each available area
  • the domain name accessed by the host client is the same, and there is only one TLS certificate key pair.
  • the actual mirror storage is only one, so the consistency of the system is guaranteed.
  • Step S200 The cloud management area warehouse parses the data access request, and when determining that the data access request is a mirror push request, notifying the host client of the available area to push the image to the cloud management area warehouse through the proxy server; determining that the data access request is a mirror When pulling the request, pull the required image from the cloud management area repository to the available area.
  • the mirrored warehouse of the cloud management area parses the data access request when receiving the data access request of the proxy server, performs corresponding operations according to the request type, and notifies the available area when the access request is a mirror push request.
  • the host client pushes the image to the cloud management area warehouse through the proxy server.
  • the other available areas can directly invoke the pushed image from the cloud management area.
  • the cloud management area warehouse stores the image.
  • the host in the Beijing area can initiate a mirror pull request to the cloud management area warehouse through the proxy server in the area, so that the host client in the Beijing area can directly pull the image pushed by the Shenzhen area from the cloud management area warehouse.
  • the data access request includes at least a specific number of the available area and a type of the access, and the type of the access includes a mirror push and a mirror pull.
  • each available area is preset with a number. For example, the Shenzhen area is set to 001, the Guangzhou area is set to 002, and so on, and the number of each of the available areas is inconsistent, so that the cloud management area warehouse cannot determine which available area to send the data access request.
  • the cloud management area warehouse needs to initiate The host client is authenticated.
  • the data access request further carries a user name and a password, and the user terminal accesses the host client of the available area by using the login user name and password, and the host client uses the user.
  • the name and password are placed in the data access request, packaged and sent to the proxy server, and then further sent to the cloud management area warehouse through the proxy server.
  • the cloud management area warehouse After the host client sends the data access request to the cloud management area warehouse through the proxy server, the cloud management area warehouse first decodes the data access request, verifies the user name and password in the data access request, and reads the data after the verification is passed. Accessing the available area number in the request, and then determining the type of the data access, and analyzing whether the data access request is reasonable.
  • the cloud management area warehouse is provided with a control unit, and the cloud management area warehouse is controlled by the control unit.
  • the data access request decodes and verifies the username and password and determines the type of the data access request.
  • the cloud management warehouse When determining the mirror push request, the cloud management warehouse sends a data push notification to the host client of the corresponding numbered Availability Zone, the host client is After receiving the data push notification sent by the cloud management area warehouse, the image can be pushed to the cloud management area warehouse through the proxy server.
  • the data access request further needs to carry the type and name of the image to be pulled
  • the cloud management area warehouse is further Split into multiple mirrored storage units that store different types of mirrors.
  • the control unit of the cloud management area warehouse parses the type and name of the image to be pulled, first finds the image storage unit that stores the image of the type, and then traverses the image storage unit, if the name of the image to be pulled is found.
  • the image is pulled to the host client of the available area for sending the request, and is delivered by the host client to the user terminal; if the name of the image to be pulled is not found, the prompt message is sent to the host client through the proxy server. Prompt the host client to have no such mirror and verify that the name of the mirror is correct.
  • the application authenticates the host client, ensures data security of the cloud management area warehouse, avoids malicious access of the cloud management area warehouse, and avoids the cloud management area by processing each available area number.
  • the name of the Availability Zone for sending data access requests cannot be known, ensuring normal mirror synchronization.
  • the present invention does not need to have a mirrored warehouse in the available area and the cloud management area.
  • the mirror synchronization consumes less time, and does not need to pass user push, notification, and cloud management area components.
  • Call Docker API pull image, cloud management area component calls Docker The API pushes the image to the various Availability Zones, and since there is no need to push the image to the cloud zone in an available zone and then push the image to each Availability Zone, there is no probability of failure due to the native notification mechanism of the cloud zone warehouse. After the push mirror is sent, the notification is not sent, causing the problem that synchronization cannot be started.
  • there is only one centralized mirror library there is no problem of mirror synchronization loopback.
  • FIG. 3 is a flowchart of a preferred embodiment of step S200 in the image synchronization method of the mirror warehouse provided by the present application.
  • the step S200 includes:
  • Step S201 The cloud management area warehouse receives a data access request sent by the proxy server and parses the data access request;
  • Step S202 determining whether the data access request is a mirror push request or a mirror pull request
  • Step S203 If the data access request is a mirror push request, notify the host client of the available area to push the image to the cloud management area warehouse through the proxy server; if the data access request is a mirror pull request, find the image required by the request, and pass the The proxy server that sent the request pulls the image into the host client of the Availability Zone where the proxy server is located.
  • the data access request is sent to the mirrored warehouse through the proxy server, and the cloud management area warehouse pulls the stored image to the available area.
  • the mirror is sent to the host client of the available area through the proxy server, and then the host client feeds back to the user terminal, and the mirror of all the available areas is uniformly managed by adopting a mirror library, so that the warehouse push is not caused by the available area.
  • the image is not sent out and the problem cannot be synchronized. You do not need to push the image to the cloud zone warehouse in an available area, and then synchronize the image to all available areas. You only need to store the image. When the zone needs to be called synchronously, it only needs to access the cloud management zone to obtain the image.
  • the synchronization method is simple and the system consistency is ensured.
  • the mirror synchronization method of the mirror warehouse further includes:
  • the proxy server When the proxy server pushes the image to the cloud management area warehouse or the cloud management area warehouse to pull the image to the proxy server, the proxy server analyzes the size of the mirrored data, and prompts the mirror transmission failure when the mirrored data is larger than the upper limit of the data size preset by the proxy server. .
  • the default size of the request data is small (1M) after using the Nginx proxy server, and some mirror layers are larger (about 100+M) when the image is pushed, the pushed image passes through the proxy server.
  • the size of the mirrored data needs to be analyzed.
  • the mirrored data is larger than the upper limit of the data size preset by the proxy server, the image transmission fails.
  • the user can modify the configuration of the Nginx proxy server to set the size of the preset request data.
  • the upper limit is set to infinity to continue the transfer.
  • the number of available zones is at least one, and each of the available zones is deployed with a set of proxy servers, and the host clients of each available zone access the cloud zone warehouse through the proxy servers of the available zones.
  • the domain name, the certificate, and the key of the proxy servers in the respective Availability Zones are the same, so that the domain names accessed by the host clients of the available zones are the same, and only one copy of the TLS certificate key pair is used. There is only one mirror storage, so the consistency of the system is guaranteed.
  • This application provides a unified management method for mirroring.
  • There is only one centralized mirror library which has the following advantages: because there is only one mirror library, there is no need to perform any cross-region mirror synchronization, avoiding the synchronization of mirroring by other methods.
  • Various problems The domain name of the mirror library accessed by all hosts in all areas is the same.
  • There is only one TLS certificate key pair and there is only one actual mirror storage, which maintains the consistency of the system.
  • Only the centralized management area needs to deploy a Registry (mirror repository) to store the image. In other areas, only one proxy server needs to be deployed, which saves deployment costs.
  • Registry mirror repository
  • the application also provides a mirror synchronization system of a mirror warehouse. As shown in FIG. 4, the device includes:
  • the cloud management area warehouse 2 is configured to parse the data access request, and when determining that the data access request is a mirror push request, notify the host client 11 of the available area to push the image to the cloud management area warehouse 2 through the proxy server 12, When the data access request is a mirror pull request, the required image is pulled from the cloud management area repository 2 to the available area for sending the request.
  • the data access request is a mirror pull request
  • the required image is pulled from the cloud management area repository 2 to the available area for sending the request.
  • the host client 11 is further configured to receive a mirroring event initiated by a user terminal of an available area where the host client 11 is located, and generate a data access request according to the mirroring time, where the mirroring Events include mirror push events and mirror pull events.
  • the mirroring Events include mirror push events and mirror pull events.
  • the proxy server is specifically configured to perform a secure transport layer protocol authentication according to the domain name when the host client accesses the proxy server of the available zone through the domain name, and the host client is verified after the verification is passed.
  • the data access request of the end is sent to the cloud management area warehouse.
  • the present application uniformly manages the mirroring of the available area by setting a centralized mirror warehouse in the cloud management area, so that no cross-area mirror synchronization is required, and the synchronization is achieved by other methods.
  • the various problems will not cause the problem that the mirrors pushed by the available area mirror library are not sent out, and only a mirrored warehouse is deployed in the cloud management area. Only one proxy server needs to be deployed in each free area, saving Deployment costs.
  • the private image inside the tenant can also be synchronized to each available area in time, so that in any available area, the user has no indiscriminate access to the public image and the user under the tenant for the private image inside the tenant.
  • the present application also provides a mirror synchronization device of a mirrored warehouse, the rights authentication device including a processor, a memory, and a mirror synchronization program stored on the memory and executable by the processor, the image synchronization program When executed by the processor, the steps of the image synchronization method as described above are implemented.
  • the present application also provides a storage medium storing a mirror synchronization program that, when executed by a processor, implements the steps of the image synchronization method as described above.
  • a computer program to instruct related hardware (such as a processor, a controller, etc.), and the program can be stored in one.
  • the program when executed, may include the processes of the various method embodiments as described above.
  • the storage medium described therein may be a memory, a magnetic disk, an optical disk, or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un procédé de synchronisation d'images pour un registre d'images, un système, un dispositif et un support d'informations. Le procédé de synchronisation d'images comprend : premièrement, le lancement par un client hôte dans une zone disponible, au moyen d'un serveur mandataire dans la zone disponible, d'une demande d'accès à des données vers un registre de zone de gestion de nuage ; et ensuite, l'analyse, par le registre de zone de gestion de nuage, de la demande d'accès à des données, la notification, lorsqu'il est déterminé que la demande d'accès à des données est une demande de poussée d'image, au client hôte de la zone disponible de pousser l'image au moyen du serveur mandataire, et la poussée, lorsqu'il est déterminé que la demande d'accès à des données est une demande de poussée d'image, de l'image demandée du registre de zone de gestion de nuage vers la zone disponible.
PCT/CN2018/082251 2017-12-29 2018-04-09 Procédé de synchronisation d'images pour registre d'images, système, dispositif et support d'informations Ceased WO2019127971A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711476883.3 2017-12-29
CN201711476883.3A CN108200155A (zh) 2017-12-29 2017-12-29 Docker镜像仓库的镜像同步方法和镜像同步系统

Publications (1)

Publication Number Publication Date
WO2019127971A1 true WO2019127971A1 (fr) 2019-07-04

Family

ID=62586248

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082251 Ceased WO2019127971A1 (fr) 2017-12-29 2018-04-09 Procédé de synchronisation d'images pour registre d'images, système, dispositif et support d'informations

Country Status (2)

Country Link
CN (1) CN108200155A (fr)
WO (1) WO2019127971A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111190547A (zh) * 2019-12-30 2020-05-22 中国电子科技集团公司信息科学研究院 一种分布式容器镜像存储与分发系统与方法
CN112000740A (zh) * 2020-08-24 2020-11-27 浪潮云信息技术股份公司 一种基于脚本的Git与Harbor数据同步方法及系统
CN113110917A (zh) * 2021-04-28 2021-07-13 北京链道科技有限公司 基于Kubernetes的数据发现和安全访问方法
CN113596162A (zh) * 2021-07-30 2021-11-02 北京快乐茄信息技术有限公司 镜像文件处理方法及装置、网络设备和存储介质

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109062663B (zh) * 2018-07-19 2020-07-17 北京百度网讯科技有限公司 镜像分发方法、装置及存储介质
CN109688232B (zh) * 2019-01-28 2021-09-21 杭州涂鸦信息技术有限公司 一种镜像回溯方法、镜像回溯系统及代理服务器
CN110187954B (zh) * 2019-04-23 2023-08-18 平安科技（深圳）有限公司 应用镜像推送方法、装置、计算机设备及存储介质
CN111291017B (zh) * 2020-03-03 2024-04-05 中国工商银行股份有限公司 镜像仓库的镜像存储、提取方法及装置
CN111294410B (zh) * 2020-05-11 2020-08-14 杭州朗澈科技有限公司 一种本地镜像文件上传多地域私有镜像仓库的方法
CN111917856A (zh) * 2020-07-27 2020-11-10 平安证券股份有限公司 镜像文件的交付方法及相关设备
CN112231052B (zh) * 2020-09-29 2024-06-18 中山大学 一种高性能分布式容器镜像分发系统及方法
CN112800070A (zh) * 2020-12-28 2021-05-14 杭州涂鸦信息技术有限公司 一种镜像仓库系统
CN113572619B (zh) * 2021-09-22 2021-12-07 银河麒麟软件(长沙)有限公司 一种基于notary的容器云镜像可信实现方法及系统
CN115941704A (zh) * 2022-12-07 2023-04-07 山石网科通信技术股份有限公司 镜像同步方法及装置、电子设备、存储介质
CN116339910B (zh) * 2023-02-16 2025-05-16 西安雷风电子科技有限公司 一种基于共享存储的集群镜像同步改进方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9569180B1 (en) * 2015-10-29 2017-02-14 International Business Machines Corporation Application development in cloud based environment
CN106469083A (zh) * 2015-08-19 2017-03-01 三星Sds株式会社 容器镜像安全检查方法及其装置
WO2017067016A1 (fr) * 2015-10-23 2017-04-27 Huawei Technologies Co., Ltd. Extension de contraintes de ressources pour conteneurs définis pour le service
CN106933635A (zh) * 2017-03-15 2017-07-07 北京搜狐新媒体信息技术有限公司 Docker镜像生成方法及Docker容器
CN107105054A (zh) * 2017-05-17 2017-08-29 郑州云海信息技术有限公司 一种面向docker镜像仓库的镜像垃圾清理系统及方法
CN107247793A (zh) * 2017-06-21 2017-10-13 平安科技（深圳）有限公司 Docker镜像仓库的镜像同步方法和镜像同步系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106331045B (zh) * 2015-07-02 2019-12-31 北京京东尚科信息技术有限公司 实现Docker镜像服务的方法和系统
CN106790663A (zh) * 2017-01-22 2017-05-31 济南浪潮高新科技投资发展有限公司 基于Docker的网络存储系统的实现方法
CN107105033B (zh) * 2017-04-21 2020-08-18 北京奇安信科技有限公司 云应用访问方法、云代理服务器及云应用访问系统
CN107239688B (zh) * 2017-06-30 2019-07-23 平安科技（深圳）有限公司 Docker镜像仓库的权限认证方法和系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106469083A (zh) * 2015-08-19 2017-03-01 三星Sds株式会社 容器镜像安全检查方法及其装置
WO2017067016A1 (fr) * 2015-10-23 2017-04-27 Huawei Technologies Co., Ltd. Extension de contraintes de ressources pour conteneurs définis pour le service
US9569180B1 (en) * 2015-10-29 2017-02-14 International Business Machines Corporation Application development in cloud based environment
CN106933635A (zh) * 2017-03-15 2017-07-07 北京搜狐新媒体信息技术有限公司 Docker镜像生成方法及Docker容器
CN107105054A (zh) * 2017-05-17 2017-08-29 郑州云海信息技术有限公司 一种面向docker镜像仓库的镜像垃圾清理系统及方法
CN107247793A (zh) * 2017-06-21 2017-10-13 平安科技（深圳）有限公司 Docker镜像仓库的镜像同步方法和镜像同步系统

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111190547A (zh) * 2019-12-30 2020-05-22 中国电子科技集团公司信息科学研究院 一种分布式容器镜像存储与分发系统与方法
CN111190547B (zh) * 2019-12-30 2023-02-24 中国电子科技集团公司信息科学研究院 一种分布式容器镜像存储与分发系统与方法
CN112000740A (zh) * 2020-08-24 2020-11-27 浪潮云信息技术股份公司 一种基于脚本的Git与Harbor数据同步方法及系统
CN113110917A (zh) * 2021-04-28 2021-07-13 北京链道科技有限公司 基于Kubernetes的数据发现和安全访问方法
CN113110917B (zh) * 2021-04-28 2024-03-15 北京链道科技有限公司 基于Kubernetes的数据发现和安全访问方法
CN113596162A (zh) * 2021-07-30 2021-11-02 北京快乐茄信息技术有限公司 镜像文件处理方法及装置、网络设备和存储介质

Also Published As

Publication number Publication date
CN108200155A (zh) 2018-06-22

Similar Documents

Publication Publication Date Title
WO2019127971A1 (fr) Procédé de synchronisation d'images pour registre d'images, système, dispositif et support d'informations
WO2019128007A1 (fr) Procédé de connexion à un conteneur, serveur d'application, système et support de stockage
US11522701B2 (en) Generating and managing a composite identity token for multi-service use
WO2019127973A1 (fr) Procédé, système et dispositif d'authentification d'autorité pour référentiel de miroirs et support de stockage
WO2020189926A1 (fr) Procédé et serveur permettant de gérer une identité d'utilisateur en utilisant un réseau à chaîne de blocs, et procédé et terminal d'authentification d'utilisateur utilisant l'identité d'utilisateur basée sur un réseau à chaîne de blocs
US20200329121A1 (en) Remote provisioning and enrollment of enterprise devices with on-premises domain controllers
WO2022050652A1 (fr) Procédé, appareil et support d'enregistrement lisible par ordinateur pour la commande d'un compte
WO2014007516A1 (fr) Système de service à certificat unique et son procédé de fonctionnement
KR20160129852A (ko) 장치 간 신뢰 애플리케이션을 위한 보안 하드웨어
WO2018076841A1 (fr) Procédé de partage de données, appareil, support de stockage, et serveur
WO2016169410A1 (fr) Procédé et dispositif d'ouverture de session, serveur et système d'ouverture de session
WO2015018243A1 (fr) Procédé et dispositif de blocage de page internet basés sur un dispositif ios
WO2013065915A1 (fr) Procédé d'interfonctionnement de confiance entre une région de confiance et une région non de confiance, procédé, serveur et terminal pour commander le téléchargement d'applications de confiance, et système de commande les appliquant
WO2017088664A1 (fr) Procédé et appareil de traitement de données destinés à un système de fichiers en grappes
WO2020189927A1 (fr) Procédé et serveur de gestion de l'identité d'un utilisateur à l'aide d'un réseau de chaîne de blocs, et procédé et terminal d'authentification d'utilisateur à l'aide d'une identité d'utilisateur sur la base d'un réseau de chaîne de blocs
WO2018076844A1 (fr) Procédé et dispositif de copie de sauvegarde de données, support de stockage et appareil électronique
WO2017054443A1 (fr) Procédé de commande à distance, serveur et stockage rattaché à un réseau
WO2018233352A1 (fr) Procédé de transmission de données, dispositif, terminal, et support de stockage lisible par ordinateur
WO2018120680A1 (fr) Système de sauvegarde de disque virtuel, procédé, appareil, hôte de service et support d'enregistrement
WO2018098881A1 (fr) Procédé et dispositif de traitement d'accès pour application
US20210099297A1 (en) Secure reusable access tokens
WO2020017767A1 (fr) Procédé et dispositif de commande d'accès d'application
WO2018076863A1 (fr) Procédé de stockage de données, appareil, support de stockage, serveur et système
WO2023090755A1 (fr) Système de contrôle d'accès au réseau d'instance de virtualisation, et procédé associé
WO2018076881A1 (fr) Procédé et dispositif de synchronisation de données, support de stockage et serveur

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 07/10/2020)

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18897855

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 18897855

Country of ref document: EP

Kind code of ref document: A1