Product delivery methods and devices
By storing the target image file to a mobile hard disk and mounting it directly into the mirror warehouse system, the problem of long-term image file transfer in cloud native privatized delivery is solved, and a more efficient delivery process is achieved.
Patent Information
- Application Number
- CN202311203987.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-18
- Publication Date
- 2025-04-01
- Estimated Expiration
- 2043-09-18
AI Technical Summary
In cloud native privatization delivery, when the image files are too large or too many, the transmission takes a long time, resulting in an extended delivery cycle and affecting efficiency.
By storing the target image file to the mobile hard disk and mounting it directly into the mirror warehouse system, a large number of I/O operations during the upload process are avoided and downloaded and installed directly from the hard disk.
It significantly reduces the transfer time of target image files, shortens the delivery cycle, improves delivery efficiency, and reduces dependence on network bandwidth and disk read and write performance in customer privatized environments.
Smart Images

Figure CN117234539B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of cloud services, specifically to technical fields such as private cloud and cloud native. Background Art
[0002] When service providers deliver products to customers, they need to deploy the products in the customer's private environment for data privacy and network security considerations. This delivery process is called private delivery. The rapid development of cloud native technology has provided a lot of convenience for private delivery. At present, private delivery based on cloud native technology has become the main delivery method.
[0003] In cloud-native private delivery, the service provider first transfers the product to the customer's private environment in the form of an image file, and then runs the product in the customer's private environment in the form of a container application. When there are too many or too large image files of the product, the transmission process will be very time-consuming due to the network bandwidth and disk read and write performance of the customer's private environment, which will extend the entire delivery cycle and ultimately affect delivery efficiency. Summary of the invention
[0004] The embodiments of the present disclosure provide a product delivery method, apparatus, device, storage medium, and program product.
[0005] In a first aspect, an embodiment of the present disclosure proposes a product delivery method, including: building a target image file based on the product, and storing the target image file in a mobile hard disk; deploying a cloud native base, and installing an image warehouse system in the cloud native base; mounting the mobile hard disk to the image warehouse system; downloading the target image file from the image warehouse system, and installing the product on the cloud native base based on the target image file.
[0006] In the second aspect, an embodiment of the present disclosure proposes a product delivery device, including: a build and storage module, configured to build a target image file based on the product and store the target image file in a mobile hard disk; a deployment and installation module, configured to deploy a cloud native base and install an image warehouse system in the cloud native base; a mounting module, configured to mount the mobile hard disk into the image warehouse system; a download and installation module, configured to download the target image file from the image warehouse system, and install the product on the cloud native base based on the target image file.
[0007] In a third aspect, an embodiment of the present disclosure proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to 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 so that the at least one processor can execute the method described in the first aspect.
[0008] In a fourth aspect, an embodiment of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to cause a computer to execute the method described in the first aspect.
[0009] In a fifth aspect, an embodiment of the present disclosure proposes a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor.
[0010] The product delivery method provided by the embodiment of the present disclosure directly mounts the mobile hard disk to the image warehouse system, thereby eliminating the process of uploading the target image file to the image warehouse system, avoiding the time consumption caused by a large number of I / O operations, and reducing the transmission time of the target image file of the product to nearly 0. The overall time consumption of the delivery cycle is greatly reduced, while reducing the dependence on the network bandwidth and disk read and write performance of the customer's private environment, and ultimately improving the delivery efficiency.
[0011] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Other features, purposes and advantages of the present disclosure will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings. The drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure. Among them:
[0013] Figure 1 is a flow chart of one embodiment of a product delivery method according to the present disclosure;
[0014] Figure 2 is a flow chart of yet another embodiment of a product delivery method according to the present disclosure;
[0015] Figure 3 is a flow chart of another embodiment of a product delivery method according to the present disclosure;
[0016] Figure 4 is a schematic structural diagram of an embodiment of a product delivery device according to the present disclosure;
[0017] Figure 5 The present invention is a block diagram of an electronic device used to implement the product delivery method of the embodiment of the present disclosure. DETAILED DESCRIPTION
[0018] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.
[0019] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0020] Figure 1 A process 100 of an embodiment of a product delivery method according to the present disclosure is shown. The product delivery method comprises the following steps:
[0021] Step 101, construct a target image file based on the product, and store the target image file in a mobile hard disk.
[0022] In this embodiment, the service provider develops products according to customer needs, builds a target image file based on the product, and stores the target image file in a mobile hard disk.
[0023] Here, the product is the product that the service provider needs to deliver to the customer, usually a software installation package. A series of product files are made into a single target image file according to the file system format of the customer's image warehouse system to facilitate customer download and use.
[0024] Among them, the target image file can be a software installer based on k8s cloud native, which can only be installed in the k8s cloud native environment. k8s stands for kubernetes, which is an open source platform for automatic deployment, expansion and management of containers applied to clusters, providing a container-centric infrastructure. Cloud native is a method of building and running applications, a set of technical systems and methodologies. Cloud Native is a combination of Cloud + Native. Cloud means that the application is located in the cloud, not a traditional data center; Native means that the application is designed with the cloud environment in mind from the beginning, is natively designed for the cloud, runs in the cloud in the best posture, and fully utilizes and gives play to the elasticity and distributed advantages of the cloud platform.
[0025] Step 102: deploy a cloud native base and install an image repository system in the cloud native base.
[0026] In this embodiment, the service provider deploys a cloud-native base in the customer's privatized environment and installs an image repository system in the cloud-native base.
[0027] Usually, the products developed by service providers can only run based on cloud native forms, so it is necessary to deploy a cloud native base as the underlying operating environment. Installing an image warehouse system in the cloud native base can be used to store the target image files of the product.
[0028] Step 103, mount the mobile hard disk into the image warehouse system.
[0029] In this embodiment, the service provider can directly mount the mobile hard disk to the image warehouse system. In this way, there is no need to upload the target image file in the mobile hard disk to the image warehouse system, and the target image file can be directly obtained from the mobile hard disk mounted by the image warehouse system.
[0030] Due to factors such as network bandwidth and disk read / write performance in the customer's private environment, uploading the target image file to the image warehouse system usually takes a long time. The implementation process is as follows:
[0031] First, the upload tool reads the target image file from the mobile hard disk into the memory.
[0032] Afterwards, the upload tool uploads the target image file in the memory to the image warehouse system through HTTP (Hypertext Transfer Protocol).
[0033] Then, the image repository system writes the received target image file to the disk and returns a success status code.
[0034] Finally, after receiving the success status code, the upload tool clears the target image file in the memory and ends the upload.
[0035] From the above process, we can see that it has gone through several stages, including reading hard disk -> writing to memory -> HTTP protocol transmission -> writing to disk -> clearing memory. Each stage is an I / O (Input / Output) operation. When the target image files of the product are too many or too large, it will be very time-consuming.
[0036] The product delivery method provided in this application eliminates the process of uploading the target image file to the image warehouse system by directly mounting the mobile hard disk to the image warehouse system, avoids the time-consuming process caused by a large number of I / O operations, and reduces the transmission time of the product's target image file to near zero.
[0037] Step 104: Download the target image file from the image repository system, and install the product on the cloud native base based on the target image file.
[0038] In this embodiment, the cloud native base in the customer's private environment can download the target image file from the image warehouse system, and install the product on the cloud native base based on the target image file. Specifically, the target image file can be run in the form of a container application in the customer's private environment.
[0039] The product delivery method provided by the embodiment of the present disclosure directly mounts the mobile hard disk to the image warehouse system, thereby eliminating the process of uploading the target image file to the image warehouse system, avoiding the time consumption caused by a large number of I / O operations, and reducing the transmission time of the target image file of the product to nearly 0. The overall time consumption of the delivery cycle is greatly reduced, while reducing the dependence on the network bandwidth and disk read and write performance of the customer's private environment, and ultimately improving the delivery efficiency.
[0040] Continue to refer Figure 2 , which shows a process 200 of another embodiment of a product delivery method according to the present disclosure. The product delivery method includes the following steps:
[0041] Step 201, packaging the product into an original image file.
[0042] In this embodiment, the service provider can package the product into an original image file.
[0043] Here, the product is the product that the service provider needs to deliver to the customer, usually a software installation package. A series of product files are made into a single original image file in a certain format to facilitate customer download and use.
[0044] Step 202: The original image file is broken up and reorganized according to the file system of the image repository system to obtain a target image file.
[0045] In this embodiment, the original image file is broken up and reorganized according to the file system of the image warehouse system to obtain the target image file.
[0046] Among them, the target image file can be a software installer based on k8s cloud native, which can only be installed in the k8s cloud native environment. k8s stands for kubernetes, which is an open source platform for automatic deployment, expansion and management of containers applied to clusters, providing a container-centric infrastructure. Cloud native is a method of building and running applications, a set of technical systems and methodologies. Cloud Native is a combination of Cloud + Native. Cloud means that the application is located in the cloud, not a traditional data center; Native means that the application is designed with the cloud environment in mind from the beginning, is natively designed for the cloud, runs in the cloud in the best posture, and fully utilizes and gives play to the elasticity and distributed advantages of the cloud platform.
[0047] Here, we study the file system of the image warehouse system, and can directly format the original image file according to the format specified by the file system. The formatting is completed by the service provider on site, and the customer does not need to download and then format it.
[0048] Commonly used image warehouse systems include: harbor and registry. When formatting, the two have different ways of breaking up, and there are detailed differences in layering, storage, and arrangement. Among them, the registry breaks up the original image files by layer. When a product usually contains multiple image files, there will be duplicate layers. The registry will merge the duplicate layers to save the space actually occupied by the image warehouse system. Harbor breaks up the original image files by layer. For an original image file, the multi-architecture and multi-platform files will be stored together.
[0049] Step 203, storing the target image file in a mobile hard disk.
[0050] In this embodiment, the target image file is stored in a mobile hard disk.
[0051] Step 204: deploy a cloud native base and install an image repository system in the cloud native base.
[0052] In this embodiment, the service provider deploys a cloud-native base in the customer's privatized environment and installs an image repository system in the cloud-native base.
[0053] Usually, the products developed by service providers can only run based on cloud native forms, so it is necessary to deploy a cloud native base as the underlying operating environment. Installing an image warehouse system in the cloud native base can be used to store the target image files of the product.
[0054] Step 205, partition the mobile hard disk.
[0055] In this embodiment, the mobile hard disk is partitioned.
[0056] Step 206, set the mount point, and mount the partition to the file directory of the image repository system.
[0057] In this embodiment, a mount point is set to mount the partition into a file directory of the image repository system.
[0058] The mount point is a directory in the image repository system's file system (usually a new directory is created using the mkdir command before mounting). Usually, after mounting successfully, accessing the mount point is accessing the partition mounted by the image repository system.
[0059] Step 207: Download the target image file from the image repository system, and install the product on the cloud native base based on the target image file.
[0060] In this embodiment, the cloud native base in the customer's private environment can download the target image file from the image warehouse system, and install the product on the cloud native base based on the target image file. Specifically, the target image file can be run in the form of a container application in the customer's private environment.
[0061] from Figure 2 It can be seen that Figure 1 Compared with the corresponding embodiment, the product delivery method in this embodiment highlights the formatting step and the mounting step. Therefore, the solution described in this embodiment studies the file system of the image warehouse system and can directly format the original image file according to the format specified by the file system. The formatting is completed on site by the service provider, and the customer does not need to download and then format it, which saves the customer time to install the product. Through partition mounting, direct access to the mobile hard disk mounted by the image warehouse system is achieved.
[0062] Further references Figure 3 , which shows a process 300 of another embodiment of a product delivery method according to the present disclosure. The product delivery method comprises the following steps:
[0063] Step 301, packaging the product into an original image file.
[0064] In this embodiment, the service provider can package the product into an original image file.
[0065] Here, the product is the product that the service provider needs to deliver to the customer, usually a software installation package. A series of product files are made into a single original image file in a certain format to facilitate customer download and use.
[0066] Step 302: The original image file is broken up and reorganized according to the file system of the image repository system to obtain a target image file.
[0067] In this embodiment, the original image file is broken up and reorganized according to the file system of the image warehouse system to obtain the target image file.
[0068] Among them, the target image file can be a software installer based on k8s cloud native, which can only be installed in the k8s cloud native environment. k8s stands for kubernetes, which is an open source platform for automatic deployment, expansion and management of containers applied to clusters, providing a container-centric infrastructure. Cloud native is a method of building and running applications, a set of technical systems and methodologies. Cloud Native is a combination of Cloud + Native. Cloud means that the application is located in the cloud, not a traditional data center; Native means that the application is designed with the cloud environment in mind from the beginning, is natively designed for the cloud, runs in the cloud in the best posture, and fully utilizes and gives play to the elasticity and distributed advantages of the cloud platform.
[0069] Here, we study the file system of the image warehouse system, and can directly format the original image file according to the format specified by the file system. The formatting is completed by the service provider on site, and the customer does not need to download and then format it.
[0070] Commonly used image warehouse systems include: harbor and registry. When formatting, the two have different ways of breaking up, and there are detailed differences in layering, storage, and arrangement. Among them, the registry breaks up the original image files by layer. When a product usually contains multiple image files, there will be duplicate layers. The registry will merge the duplicate layers to save the space actually occupied by the image warehouse system. Harbor breaks up the original image files by layer. For an original image file, the multi-architecture and multi-platform files will be stored together.
[0071] Step 303, storing the target image file in a mobile hard disk.
[0072] In this embodiment, the target image file is stored in a mobile hard disk.
[0073] Step 304: deploy a cloud native base and install an image repository system in the cloud native base.
[0074] In this embodiment, the service provider deploys a cloud-native base in the customer's privatized environment and installs an image repository system in the cloud-native base.
[0075] Usually, the products developed by service providers can only run based on cloud native forms, so it is necessary to deploy a cloud native base as the underlying operating environment. Installing an image warehouse system in the cloud native base can be used to store the target image files of the product.
[0076] Step 305: mount the mobile hard disk as a distributed node into the image warehouse system.
[0077] In this embodiment, the mobile hard disk is mounted as a distributed node in the image warehouse system.
[0078] Step 306: synchronize the target image file in the mobile hard disk to other distributed nodes of the image warehouse system through a synchronization tool.
[0079] In this embodiment, the target image file in the mobile hard disk is synchronized to other distributed nodes of the image warehouse system through a synchronization tool.
[0080] Distributed file system mounting has high availability. The mobile hard disk is used as a distributed node of the image warehouse system and mounted in the image warehouse system. The target image file in the distributed node is synchronized between each distributed node through the synchronization tool to ensure data consistency.
[0081] Step 307: Download the target image file from the image repository system, and install the product on the cloud native base based on the target image file.
[0082] In this embodiment, the cloud native base in the customer's private environment can download the target image file from the image warehouse system, and install the product on the cloud native base based on the target image file. Specifically, the target image file can be run in the form of a container application in the customer's private environment.
[0083] from Figure 3 It can be seen that Figure 1 Compared with the corresponding embodiment, the product delivery method in this embodiment highlights the formatting step and the mounting step. Therefore, the solution described in this embodiment studies the file system of the image warehouse system, and can directly format the original image file according to the format specified by the file system. The formatting is completed by the service provider on site, and the customer does not need to download and then format it, which saves the customer time to install the product. Through the distributed file system mounting, the synchronization of the target image file between the various distributed nodes of the image warehouse system is achieved.
[0084] Further references Figure 4 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a product delivery device, which is similar to Figure 1 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.
[0085] like Figure 4As shown, the product delivery device 400 of this embodiment may include: a construction and storage module 401, a deployment and installation module 402, a mounting module 403, and a download and installation module 404. Among them, the construction and storage module 401 is configured to build a target image file based on the product and store the target image file in a mobile hard disk; the deployment and installation module 402 is configured to deploy a cloud native base and install an image warehouse system in the cloud native base; the mounting module 403 is configured to mount the mobile hard disk into the image warehouse system; the download and installation module 404 is configured to download the target image file from the image warehouse system and install the product on the cloud native base based on the target image file.
[0086] In this embodiment, in the product delivery device 400, the specific processing of the construction and storage module 401, the deployment and installation module 402, the mounting module 403 and the download and installation module 404 and the technical effects thereof can be referred to respectively. Figure 1 The relevant descriptions of steps 101 - 104 in the corresponding embodiment are not repeated here.
[0087] In some optional implementations of this embodiment, the construction and storage module 401 is further configured to: package the product into an original image file; and break up and reorganize the original image file according to the file system of the image warehouse system to obtain a target image file.
[0088] In some optional implementations of this embodiment, the image repository is a registry, and the registry breaks up the original image files according to layers and merges duplicate layers.
[0089] In some optional implementations of this embodiment, the image repository is harbor, which breaks up the original image files by layer and stores files of multiple architectures and platforms belonging to the same image file together.
[0090] In some optional implementations of this embodiment, the mounting module 403 is further configured to: partition the mobile hard disk; set a mount point, and mount the partition to a file directory of the image warehouse system.
[0091] In some optional implementations of this embodiment, the mounting module 403 is further configured to: mount the mobile hard disk as a distributed node in the image warehouse system; and synchronize the target image file in the mobile hard disk to other distributed nodes of the image warehouse system through a synchronization tool.
[0092] In the technical solution disclosed herein, the acquisition, storage and application of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0093] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
[0094] Figure 5 A schematic block diagram of an example electronic device 500 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.
[0095] like Figure 5 As shown, the device 500 includes a computing unit 501, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 502 or a computer program loaded from a storage unit 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the device 500 can also be stored. The computing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.
[0096] A number of components in the device 500 are connected to the I / O interface 505, including: an input unit 506, such as a keyboard, a mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a disk, an optical disk, etc.; and a communication unit 509, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 509 allows the device 500 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0097] The computing unit 501 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 501 performs the various methods and processes described above, such as the product delivery method. For example, in some embodiments, the product delivery method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 500 via the ROM 502 and / or the communication unit 509. When the computer program is loaded into the RAM 503 and executed by the computing unit 501, one or more steps of the product delivery method described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to execute the product delivery method in any other appropriate manner (e.g., by means of firmware).
[0098] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0099] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0100] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0101] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0102] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.
[0103] A computer system may include a client and a server. The client and the server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises through computer programs running on respective computers and having a client-server relationship to each other. The server may be a cloud server, a server in a distributed system, or a server combined with a blockchain.
[0104] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions provided by this disclosure can be achieved, and this document does not limit this.
[0105] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.
Claims
1. A product delivery method comprising: The product is packaged into an original image file, the original image file is scattered and reorganized according to the file system of the image warehouse system to obtain a target image file, and the target image file is stored in a mobile hard disk, wherein the image warehouse is a registry, the registry scatters the original image file according to layers, and merges duplicate layers; the image warehouse is a harbor, the harbor scatters the original image file according to layers, and stores files of multiple architectures and platforms belonging to the same image file together; Deploy a cloud-native base and install an image repository system in the cloud-native base; Mounting the mobile hard disk to the image warehouse system, wherein the mobile hard disk is partitioned, a mount point is set, and the partition is mounted to the file directory of the image warehouse system; or mounting the mobile hard disk as a distributed node to the image warehouse system, and synchronizing the target image file in the mobile hard disk to other distributed nodes of the image warehouse system through a synchronization tool; The target image file is downloaded from the image repository system, and the product is installed on the cloud native base based on the target image file.
2. A product delivery device comprising: The building and storage module is configured to package the product into an original image file, break up and reorganize the original image file according to the file system of the image warehouse system to obtain a target image file, and store the target image file in a mobile hard disk, wherein the image warehouse is a registry, the registry breaks up the original image file according to layers, and merges duplicate layers; the image warehouse is a harbor, the harbor breaks up the original image file according to layers, and stores files of multiple architectures and platforms belonging to the same image file together; A deployment and installation module, configured to deploy a cloud native base and install an image repository system in the cloud native base; A mounting module is configured to mount the mobile hard disk into the image warehouse system, wherein the mobile hard disk is partitioned, a mount point is set, and the partition is mounted into a file directory of the image warehouse system; or the mobile hard disk is mounted into the image warehouse system as a distributed node, and the target image file in the mobile hard disk is synchronized to other distributed nodes of the image warehouse system through a synchronization tool; The download and installation module is configured to download the target image file from the image repository system and install the product on the cloud native base based on the target image file.
3. An electronic device, comprising: at least one processor; as well as a memory communicatively connected to 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 to enable the at least one processor to perform the method of claim 1.
4. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to execute the method of claim 1.
5. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to claim 1.
Citation Information
Patent Citations
Optimized deployment resource and software delivery platform in cloud computing environment
CN110764786A
Mirror image file delivery method and related equipment
CN111917856A