Container mirror image uploading and downloading system and method based on object storage and medium

Abstract

The invention relates to the technical field of Kubernetes container cloud platforms, in particular to a container mirror image uploading and downloading system and method based on object storage and a medium. In the system, a front-end page controller and a rear-end controller are arranged, and after receiving a mirror image uploading request or a mirror image downloading request submitted by a user, the front-end page controller sends the mirror image uploading request or the mirror image downloading request to the rear-end controller. The back-end controller obtains an upload link or a download link from the object storage system and sends the upload link or the download link to the front-end page controller, the front-end page controller uploads or downloads based on the upload link or the download link, the system simplifies Docker bottom layer operation, a user can log in a Harbor and operate a container mirror image without perception, and the user experience is improved. Container service uploading and downloading processes are simplified, and common users can operate conveniently. And meanwhile, the object storage system is adopted for mirror image storage, so that the uploading and downloading speed and efficiency are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of Kubernetes container cloud platform, and in particular to a container image upload and download system, method and medium based on object storage. Background Art

[0002] With the development of Kubernetes technology, many enterprises' services are gradually transforming in the direction of service containerization to achieve the purpose of enterprise service cloud migration. At the same time, enterprise service cloud migration can help enterprises save resources and costs, and facilitate users to deploy and monitor services. Among them, the basis of enterprise service cloud migration is to build service images. Enterprise service cloud migration can deploy Kubernetes clusters based on mainstream frameworks such as Kubernetes, Docker, Harbor and other components to achieve service containerization. When building images, users can build images of different sizes based on different system architectures and through Docker build commands. After cloud migration, when deploying new services or services need to be updated and upgraded, users push container images to Harbor in advance. Users need to log in to the service cluster node in advance, then connect to the Harbor service, and push the new version of the service image to Harbor. When the service image needs to be saved and downloaded locally, users also need to log in to the cluster node and operate the Harbor image. The above series of operations have the following problems for ordinary users or test development, front-end development and other personnel:

[0003] 1. Users may not have the authority to operate cluster nodes;

[0004] 2. Operators need to have certain basic knowledge and abilities, which increases the cost of learning;

[0005] 3. Logging in to the cluster node to operate increases the risk of misoperation. Summary of the invention

[0006] In view of this, the present invention provides a container image upload and download system, method and medium based on object storage to solve one of the problems existing in the prior art.

[0007] In a first aspect, the present invention provides a container image upload and download system based on object storage, the system comprising: a front-end page controller and a back-end controller; the front-end page controller is used to receive a user's image upload request and / or image download request and send it to the back-end controller; the back-end controller is used to apply for an upload link and / or a download link from the object storage system based on the image upload request and / or the image download request and send it to the front-end page controller; the front-end page controller is used to upload the image to be uploaded to the object storage system and / or download the image file from the object storage system based on the upload link and / or the download link.

[0008] In the present invention, by setting a front-end page controller and a back-end controller, the front-end page controller sends the image upload request or image download request submitted by the user to the back-end controller after receiving it. The back-end controller obtains the upload link or download link from the object storage system and sends it to the front-end page controller. The front-end page controller uploads or downloads based on the upload link or download link. Therefore, when the user uses the system to upload and download images, he only needs to operate on the page without performing operations such as the Docker command line. That is, the system simplifies the underlying Docker operation, enables users to log in to Harbor and operate container images without perception, simplifies the process of uploading and downloading container services, and facilitates ordinary users to operate. At the same time, the object storage system is used for image storage, which improves the speed and efficiency of uploading and downloading; and when uploading and downloading, the front-end page controller directly uploads and downloads from the object storage system to reduce the pressure on the back end.

[0009] In an optional embodiment, the back-end controller is also used to verify user permissions based on user information in the image upload request and / or image download request; when the verification passes, the upload link and / or download link is applied to the object storage system based on the image upload request and / or image download request and sent to the front-end page controller.

[0010] In the present invention, the security of image uploading and downloading is improved by verifying the user authority based on the user information.

[0011] In an optional implementation, the front-end page controller is further used to obtain the identification of each image piece and send it to the back-end controller; the back-end controller is further used to determine whether the object storage system contains the corresponding image piece based on the identification of each image piece; when the object storage system does not contain the corresponding image piece and the user authority check is passed, apply to the object storage system for the upload link of the corresponding image piece, and send the upload link to the front-end page controller.

[0012] In the present invention, by fragmenting the image, the stability of subsequent image upload can be improved. At the same time, by judging whether the image has been uploaded by the image identifier, repeated uploading is avoided.

[0013] In an optional embodiment, the back-end controller is also used to monitor the upload status of each image slice; when the image slice in the image to be uploaded is uploaded successfully, a merge notification is sent to the object storage system; when the upload of any image slice is interrupted, the interrupted image slice is recorded and sent to the front-end page controller, and the front-end page controller is also used to resume the upload based on the interrupted image slice.

[0014] In the present invention, when uploading image fragments, by recording the interrupted image fragments when the upload is interrupted, it is not necessary to restart the upload, but to re-upload from the last failed fragment, thereby improving the speed and efficiency of large image upload and realizing the breakpoint resumption function.

[0015] In an optional implementation, the backend controller is also used to determine whether the object storage system includes the image file to be downloaded based on the image download request; when the object storage system does not include the image file to be downloaded, pull the image file to be downloaded from the image repository to the object storage system.

[0016] In an optional implementation, the front-end page controller is further configured to concurrently upload the image fragments to the object storage system based on the upload link.

[0017] In the present invention, by uploading the image fragments concurrently, the uploading efficiency is improved and time is saved.

[0018] In an optional implementation, the backend controller is also used to push the image to be uploaded uploaded by the user to the image warehouse.

[0019] In the present invention, the image is pushed to the image warehouse to facilitate the long-term storage of the image.

[0020] In a second aspect, the present invention provides a container image upload and download method based on object storage, which is applied to the container image upload and download system based on object storage as described in the first aspect of the present invention and any one of the first aspects, and the method includes: receiving a user's image upload request and / or image download request; applying for an upload link and / or a download link from the object storage system based on the image upload request and / or the image download request; uploading the image to be uploaded to the object storage system and / or downloading the image file from the object storage system based on the upload link and / or the download link.

[0021] In the present invention, the method is adopted to upload and download images, and the functions of automatic uploading and downloading are realized; it is convenient for non-professionals to upload and download images, avoids users from learning related knowledge, saves time costs, shields the information of the underlying nodes, improves security, and reduces the risk of misoperation.

[0022] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the object storage-based container image upload and download method of the second aspect by executing the computer instructions.

[0023] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the object storage-based container image upload and download method of the second aspect.

[0024] In a fifth aspect, the present invention provides a computer program product, including computer instructions, which are used to enable a computer to execute the container image uploading and downloading method of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0026] Figure 1 is a structural block diagram of a container image upload and download system based on object storage according to an embodiment of the present invention;

[0027] Figure 2 is a structural block diagram of another container image upload and download system based on object storage according to an embodiment of the present invention;

[0028] Figure 3 It is a flowchart of a method for uploading and downloading container images based on object storage according to an embodiment of the present invention;

[0029] Figure 4 It is a flow chart of uploading an image according to a method for uploading and downloading a container image based on object storage according to an embodiment of the present invention;

[0030] Figure 5 It is a flow chart of downloading an image according to a method for uploading and downloading a container image based on object storage according to an embodiment of the present invention;

[0031] Figure 6It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0032] As described in the background technology, in order for the container service to pull the corresponding image and run normally, before deploying the service, you need to log in to the specified Harbor service through the Docker login command, and push the built image to Harbor through the Docker push command; when the user needs to download the container image to the local, the user needs to log in to the host and use the Dockersave command to download the required image file. The current method of pushing and downloading images requires users to have certain basic skills, log in to the host where Harbor is located, and users need to be familiar with Linux systems and Docker command line operations. For ordinary users, the process of uploading and downloading container images is relatively complicated and not suitable for novice operations.

[0033] In view of this, the present invention implements Kubernetes container image upload and download through page operations, isolates the underlying Docker operations, enables users to log in to Harbor and operate container images without perception, simplifies the process of uploading and downloading container services, and facilitates operations for ordinary users.

[0034] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0035] In this embodiment, a container image upload and download system based on object storage is provided. Figure 1 As shown, the system includes: a front-end page controller and a back-end controller; the front-end page controller is used to receive the user's image upload request and / or image download request and send it to the back-end controller; the back-end controller is used to apply for an upload link and / or a download link from the object storage system based on the image upload request and / or the image download request and send it to the front-end page controller; the front-end page controller is used to upload the image to be uploaded to the object storage system and / or download the image file from the object storage system based on the upload link and / or the download link.

[0036] Specifically, the front-end page controller includes a front-end interface that directly interacts with the user, and the user can log in through the front-end interface. At the same time, the front-end interface also includes an upload button and a download button that are displayed after the user logs in. When the user clicks the upload button, the image upload request can be submitted to the front-end page controller, and when the user clicks the download button, the image download request can be submitted to the front-end page controller. After receiving the image upload request or the image download request, the front-end page controller sends it to the back-end controller. The back-end controller applies for an upload link or a download link from the object storage system, and sends the upload link or the download link to the front-end page controller. The front-end page controller uploads the image uploaded by the user to the object storage system based on the upload link, or the front-end page controller downloads the image from the object storage system to the local based on the download link.

[0037] The object storage system is a high-performance, distributed object storage system. The object storage system provides distributed and shared storage functions, has good scalability and reliability. Specifically, the object storage system supports high-concurrency read and write operations, and can provide stable high throughput in a multi-node cluster. In this embodiment, the object storage system is used to temporarily store image files, that is, the image files uploaded by the front-end page controller can be temporarily stored in the object storage system, and can be saved to the image warehouse later.

[0038] The object storage-based container image upload and download system provided in this embodiment is configured with a front-end page controller and a back-end controller. After receiving the image upload request or image download request submitted by the user, the front-end page controller sends it to the back-end controller. The back-end controller obtains the upload link or download link from the object storage system and sends it to the front-end page controller. The front-end page controller uploads or downloads based on the upload link or download link. Therefore, when the user uses the system to upload and download images, he only needs to operate on the page without the need to perform operations such as the Docker command line. That is, the system simplifies the underlying Docker operation, enables users to log in to Harbor and operate container images without perception, simplifies the process of uploading and downloading container services, and facilitates operations for ordinary users. At the same time, the object storage system is used for image storage, which improves the speed and efficiency of uploading and downloading; and when uploading and downloading, the front-end page controller directly uploads and downloads from the object storage system to reduce the pressure on the back end.

[0039] In an optional embodiment, the back-end controller is also used to verify user permissions based on user information in the image upload request and / or image download request; when the verification passes, the upload link and / or download link is applied to the object storage system based on the image upload request and / or image download request and sent to the front-end page controller.

[0040] Specifically, when the back-end controller receives an image upload request or an image download request, it also performs a permission check operation on the user according to the user information attached in the request, that is, verifies whether the user is allowed to perform the upload and download functions of the relevant image. Among them, when performing permission verification, the user's permissions can be queried according to the user identity in the user information, and then matched with the image upload request or image download request sent by the user, so as to determine whether the corresponding image file can be uploaded or downloaded. If the match is unsuccessful, the content such as no permission request can be returned on the front-end interface; if the match is successful, the requested upload link or download link can be returned to the front-end page controller, and the front end can upload or download.

[0041] In an optional implementation, the front-end page controller is further used to send the image slices to be uploaded in the image upload request and obtain the identification of each image slice to the back-end controller; the back-end controller is further used to determine whether the object storage system contains the corresponding image slice based on the identification of each image slice; when the object storage system does not contain the corresponding image slice and the user authority check is passed, apply to the object storage system for the upload link of the corresponding image slice, and send the upload link to the front-end page controller. The front-end page controller is also used to upload the image slices to the object storage system concurrently based on the upload link.

[0042] Specifically, the image file to be uploaded is usually a large data file, so the image to be uploaded can be uploaded in pieces. Therefore, after receiving the image to be uploaded, the front-end page controller first processes it in pieces, and calculates the MD5 value of each image piece as the identifier of the image piece through the MD5 algorithm (Message-Digest Algorithm, information digest algorithm) to verify it. At the same time, the front-end page controller sends the MD5 identifier to the back-end controller, and the back-end controller interacts with the object storage system based on the identifier to determine whether the object storage system has a corresponding image piece. When the corresponding image piece already exists, the front-end page controller can be informed, and the subsequent front-end page controller can no longer upload the corresponding image piece. When the corresponding image piece does not exist, and the user authority verification is passed, the back-end controller applies to the object storage system for the upload link of the image piece that does not exist, and sends the applied upload link to the front-end page controller. After the front-end page controller receives the upload link of the image piece, it uploads the corresponding image piece to the object storage system concurrently.

[0043] In an optional implementation, the backend controller is also used to monitor the upload status of each image slice; when the image slice in the image to be uploaded is successfully uploaded, a merge notification is sent to the object storage system; when the upload of any image slice is interrupted, the interrupted image slice is recorded and sent to the frontend page controller, and the frontend page controller is also used to resume the upload according to the interrupted image slice. The backend controller is also used to push the image to be uploaded uploaded by the user to the image warehouse.

[0044] Specifically, during the process of uploading image shards to the object storage system by the front-end page controller, the back-end controller can interact with the object storage system. When the back-end controller determines that all image shards have been uploaded, it notifies the object storage system to merge the image shards. When merging, the object storage system can merge all image shards of the image to be uploaded into a complete image file based on the identifiers of all image shards sent by the back-end controller. At the same time, the image file generated by the merger of the object storage system can also be pushed to the image warehouse by the back-end controller to achieve long-term storage. Among them, the image warehouse can use Harbor, which is an open source enterprise-level container image warehouse that can realize the storage, distribution and management of container images, and is suitable for large-scale cluster deployment to provide container image warehouse services. In this embodiment, Harbor is used as the image warehouse to facilitate Kubernetes deployment and upgrade programs.

[0045] In addition, if the front-end page controller is disconnected or the upload operation is interrupted during the process of uploading image fragments, the back-end controller can inform the front-end page controller of the number of fragments that have been uploaded, and the front-end page controller can re-upload from the last failed allocation, thereby realizing the breakpoint resume function.

[0046] In an optional implementation, the back-end controller is further used to determine whether the object storage system includes the image file to be downloaded based on the image download request; when the object storage system does not include the image file to be downloaded, the image file to be downloaded is pulled from the image warehouse to the object storage system. Specifically, when the back-end controller receives the image download request sent by the front-end page controller, it applies to the object storage system for a download link. If the object storage system does not have the corresponding image, the back-end controller pulls the image from the image warehouse Harbor and pushes it to the object storage system, so as to download the image from the object storage system.

[0047] Therefore, based on the above content, it can be seen that the front-end page controller and back-end controller in the system can respectively implement the following functions:

[0048] The front-end page controller implements the logic of concurrent transmission of fragments, breakpoint resumption, and image download, including the following:

[0049] 1. After the user uploads the image, the front end is responsible for generating the MD5 identifier for each piece of the image file, and then concurrently transmits the large image file in pieces. After successfully uploading it to the object storage system, it initiates a request to notify the back-end controller, which records the upload status of each piece.

[0050] 2. Before uploading the image, request the backend upload status, and the backend will inform the frontend of the number of pieces currently uploaded. If the network is disconnected or the upload operation is interrupted in the middle, the user does not have to start the upload again, but re-upload from the last failed segment. It also supports concurrent uploading of multiple segments, which improves the speed and efficiency of uploading large images and realizes the breakpoint resuming function.

[0051] The backend controller completes the push and pull of Harbor images and applies for object storage system upload and download links, including the following:

[0052] 1. Interact with the front-end, and the back-end controller performs permission verification to verify whether the image repository allows the current user to upload; and judge whether the image fragment is uploaded repeatedly based on the file MD5 value, inform the front-end of the current image upload status, and record the upload status of the image fragment.

[0053] 2. Interact with the object storage system. When the back-end controller determines that all shards have been uploaded, it notifies the object storage system to merge the image shards. When the front-end requests to upload or download an image, it requests the object storage system to upload and download links. When requesting a download link, if the object storage system has the image file, it directly obtains the link. If there is no image file, it will be pushed from the Harbor image.

[0054] 3. Interact with Harbor. When uploading, the backend controller pushes the image uploaded by the user to Harbor; when downloading, the backend controller pulls the image in Harbor and pushes it to the object storage system.

[0055] As a specific application example of the embodiment of the present invention, Figure 2 As shown, the object storage-based container image upload and download system can work according to the following process:

[0056] The front-end page design is mainly divided into two parts: image fragment upload and image download. When the user uploads on the page, the front-end page controller will fragment the service image and pass the MD5 of each fragment to the back-end controller. The back-end controller determines whether the image fragment has been uploaded. Then the back-end controller applies to the object storage system for each uploaded link to be assigned to the front-end page controller. The front-end page controller uploads the image to the object storage system and notifies the back-end controller of the successful upload. When the user downloads, the front-end page controller will get the download link applied by the back-end controller; the back-end controller is mainly divided into two parts: applying for upload and download links and service image push and pull operations. When the back-end controller receives an upload and download request, it will apply to the object storage system for a link request, and perform user verification and merge file logic processing. When downloading, if there is no image file in the object storage system, the image will be pulled from Harbor and pushed to the object storage system. If the image already exists in the object storage system, it will be downloaded directly from the object storage system. There is no need to pull it from Harbor, which also avoids secondary uploads and speeds up upload and download speeds; the object storage system is mainly responsible for temporarily storing image files, and the front-end directly uploading and downloading from the object storage system can reduce the pressure on the back-end.

[0057] The container image upload and download system based on object storage provided by this embodiment realizes the function of automatic upload and download; it is convenient for non-professionals to upload and download images, avoids users from learning relevant knowledge, saves time costs, shields the information of the underlying nodes, improves security, and reduces the risk of misoperation. It has the characteristics of fragment transmission, breakpoint retransmission, and concurrent transmission of image fragments, which improves the efficiency of uploading and downloading and saves time; based on the design of this embodiment, the upload and download operations are simple and convenient.

[0058] The object storage-based container image upload and download system provided in this embodiment is suitable for the image upload and download functions of private clouds, which facilitates non-professionals to upload and download images, avoids users from learning related knowledge, saves time costs, shields the information of underlying nodes, improves security, reduces the risk of misoperation, and thus facilitates program service deployment and upgrades.

[0059] According to an embodiment of the present invention, an embodiment of a method for uploading and downloading container images based on object storage is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0060] In this embodiment, a container image upload and download method based on object storage is provided, which is applied to the above-mentioned container image upload and download system based on object storage. Figure 3is a flow chart of a method for uploading and downloading container images based on object storage according to an embodiment of the present invention. Figure 3 As shown, the process includes the following steps:

[0061] Step S101, receiving a user's image upload request and / or image download request. Specifically, the corresponding request may be received by a front-end page controller in the system.

[0062] Step S102, based on the image upload request and / or image download request, apply for an upload link and / or a download link from the object storage system. Specifically, after receiving the image upload request or the image download request, the front-end page controller sends it to the back-end controller, and the back-end controller applies for an upload link or a download link from the object storage system and sends it to the front-end page controller.

[0063] Step S103, uploading the image to be uploaded to the object storage system and / or downloading the image file from the object storage system based on the upload link and / or the download link. Specifically, after the front-end page controller receives the upload link or the download link, it can upload the image to the object storage system or download the image from the object storage system based on the link.

[0064] The further functional description of each of the above steps is the same as that of the above corresponding embodiments and will not be repeated here.

[0065] In an optional embodiment, if Figure 4 As shown in the figure, when the container image upload and download method based on object storage is used to upload the image, it can be implemented according to the following process:

[0066] The user sends an image upload request to the front-end page controller. After receiving the image upload request, the front-end page controller sends it to the back-end controller. The back-end controller performs a user permission check operation (i.e., performs authentication) to verify whether the current user is allowed to upload. At the same time, the front-end page controller segments the uploaded image, and passes the MD5 of each segment to the back-end controller. After the back-end controller passes the authentication and receives the MD5, it determines whether the MD5 corresponding image exists in the object storage system (i.e., whether the corresponding image segment has been uploaded). If it exists, the upload of the corresponding image segment is terminated. If it does not exist, the back-end controller applies for an upload link from the object storage system and returns the upload link to the front-end page controller. The front-end page controller uploads the image segments to the object storage system concurrently based on the upload link of each segment. When the upload is completed, the back-end controller notifies the object storage system to merge the image segments, and then the image file can be uploaded to Harbor for long-term storage.

[0067] In an optional embodiment, if Figure 5As shown in the figure, when the container image upload and download method based on object storage is used to download the image, it can be implemented according to the following process:

[0068] The user sends an image download request to the front-end page controller. After receiving the image download request, the front-end page controller sends it to the back-end controller. The back-end controller performs a user permission check (i.e., authentication) to verify whether the image is allowed to be uploaded by the current user. After the authentication is passed, the back-end controller determines whether the object storage system contains the image required in the image download request. If not, the back-end controller pulls the image from Harbor and pushes it to the object storage system, and applies for a download link from the object storage system; if it is included, the back-end controller can directly apply for a download link from the object storage system. The back-end controller returns the requested download link to the front-end page controller, and the front-end page controller downloads the image from the object storage system based on the download link.

[0069] The embodiment of the present invention also provides a computer device having the above Figure 1 The container image upload and download system based on object storage is shown.

[0070] See also Figure 6 , Figure 6 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 6 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 6 A processor 10 is taken as an example.

[0071] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0072] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0073] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the use of a computer device based on the presentation of a small program landing page, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0074] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0075] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0076] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0077] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0078] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A container image upload and download system based on object storage, characterized in that: The system comprises: a front-end page controller and a back-end controller; The front-end page controller is used to receive the user's image upload request and / or image download request and send it to the back-end controller; The back-end controller is used to apply for an upload link and / or a download link from the object storage system based on an image upload request and / or an image download request and send the request to the front-end page controller; The front-end page controller is used to upload the image to be uploaded to the object storage system and / or download the image file from the object storage system based on the upload link and / or the download link.

2. The system according to claim 1, characterized in that: The back-end controller is also used to verify user permissions based on user information in the image upload request and / or image download request; when the verification passes, it applies to the object storage system for an upload link and / or a download link based on the image upload request and / or image download request and sends it to the front-end page controller.

3. The system according to claim 2, characterized in that: The front-end page controller is also used to send the image fragments to be uploaded in the image upload request and the identification of each image fragment to the back-end controller; the back-end controller is also used to determine whether the object storage system contains the corresponding image fragment based on the identification of each image fragment; when the object storage system does not contain the corresponding image fragment and the user authority check is passed, apply for the upload link of the corresponding image fragment from the object storage system, and send the upload link to the front-end page controller.

4. The system according to claim 3, characterized in that: The back-end controller is also used to monitor the upload status of each image slice; when the image slice in the image to be uploaded is uploaded successfully, a merge notification is sent to the object storage system; when the upload of any image slice is interrupted, the interrupted image slice is recorded and sent to the front-end page controller, and the front-end page controller is also used to resume the upload based on the interrupted image slice.

5. The system according to claim 1, characterized in that: The backend controller is also used to determine whether the object storage system includes the image file to be downloaded based on the image download request; when the object storage system does not include the image file to be downloaded, pull the image file to be downloaded from the image warehouse to the object storage system.

6. The system according to claim 1, characterized in that: The front-end page controller is also used to concurrently upload the image fragments to the object storage system based on the upload link.

7. The system according to claim 1, characterized in that: The backend controller is also used to push the image to be uploaded uploaded by the user to the image warehouse.

8. A container image upload and download method based on object storage, characterized in that: The method applied to the container image upload and download system based on object storage according to any one of claims 1 to 7 comprises: Receive a user's image upload request and / or image download request; Applying for an upload link and / or a download link from the object storage system based on an image upload request and / or an image download request; The image to be uploaded is uploaded to the object storage system and / or the image file is downloaded from the object storage system based on the upload link and / or the download link.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the object storage-based container image uploading and downloading method according to claim 8 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the object storage-based container image uploading and downloading method according to claim 8.

Images