CN115826995B - Distributed mirror image construction system - Google Patents
Distributed mirror image construction system Download PDFInfo
- Publication number
- CN115826995B CN115826995B CN202211344605.3A CN202211344605A CN115826995B CN 115826995 B CN115826995 B CN 115826995B CN 202211344605 A CN202211344605 A CN 202211344605A CN 115826995 B CN115826995 B CN 115826995B
- Authority
- CN
- China
- Prior art keywords
- target
- architecture
- data processing
- hardware
- file
- 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.)
- Active
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Stored Programmes (AREA)
Abstract
The application relates to a distributed mirror image construction system, which belongs to the technical field of information, and comprises a data processing module, an agent node module, a supporting environment warehouse and a basic mirror image warehouse; the data processing module is respectively connected with the agent node module, the supporting environment warehouse and the basic mirror image warehouse, and the agent node module, the supporting environment warehouse and the basic mirror image warehouse are mutually connected in parallel; the agent node module comprises a plurality of agent nodes, and the agent nodes store a target hardware architecture and a target software architecture; the support environment warehouse stores target hardware files and target software files; and a built model is stored in the basic mirror image warehouse. The method and the device have the effect of improving the operation efficiency of the embedded system.
Description
Technical Field
The present application relates to the field of information technologies, and in particular, to a distributed mirror image construction system.
Background
In a computer network environment, application software is placed in a standardized container to run by introducing container technology in a host, so that the application software can be flexibly deployed on any running environment running with the container, and the requirements of cross-platform multiplexing and portability are met.
However, with the development of the embedded system, the number of embedded hardware platforms and software systems is greatly increased, and the difference of software running in the embedded system is large, and the capability of running the software is different, so that it is difficult to meet various deployment requirements of the embedded system through the existing container in the host, resulting in a reduction in the running efficiency of the embedded system.
Disclosure of Invention
The application provides a distributed mirror image construction system, which has the characteristic of improving the operation efficiency of an embedded system.
The distributed mirror image construction system is realized by the following technical scheme:
a distributed mirror image construction system comprises a data processing module, an agent node module, a supporting environment warehouse and a basic mirror image warehouse;
the data processing module is respectively connected with the agent node module, the supporting environment warehouse and the basic mirror image warehouse, and the agent node module, the supporting environment warehouse and the basic mirror image warehouse are mutually connected in parallel;
the agent node module comprises a plurality of agent nodes, and the agent nodes store a target hardware architecture and a target software architecture;
the support environment warehouse stores target hardware files and target software files;
and a built model is stored in the basic mirror image warehouse.
By adopting the technical scheme, the data processing module is arranged on the connecting center of the agent node module, the supporting environment warehouse and the basic mirror image warehouse, and each connected module is mobilized through the data processing module, so that different mirror images are built for the embedded system, various deployment requirements of the embedded system are met, and the running efficiency of the embedded system is improved.
The present application may be further configured in a preferred example to: the data processing module is configured to:
acquiring a request construction instruction, wherein the request construction instruction comprises an initial hardware architecture, an initial software architecture and task information to be executed;
invoking a target hardware architecture corresponding to the initial hardware architecture and a target software architecture corresponding to the initial software architecture in the proxy node module;
and calling a target hardware file corresponding to the initial hardware architecture and a target software file corresponding to the initial software architecture in the support environment warehouse.
By adopting the technical scheme, the data processing module is used as a dispatching center, and required data can be fetched from different modules according to the request construction instruction, so that technical support is provided for meeting various deployment requirements of the embedded system.
The present application may be further configured in a preferred example to: the data processing module is further configured to:
and obtaining a target mirror image according to the target hardware architecture, the target software architecture, the target hardware file, the target software file, the task information to be executed and the construction model.
By adopting the technical scheme, after the data processing module 1 generates the target image, the target image is returned to the remote container manager, and the backup target image is also generated and stored in the basic image warehouse. The advantage of placing the process of generating the target image in the data processing module is that: when the data processing module 1 receives the request construction instruction with the same content, the target image can be directly fetched from the base image warehouse, so that the operation amount of the distributed image construction system is reduced.
The present application may be further configured in a preferred example to: the proxy node module (2) is configured to:
receiving target hardware architecture, target software architecture, target hardware file, target software file and task information to be executed, which are sent by the data processing module (1);
obtaining a target mirror image according to the target hardware architecture, the target software architecture, the target hardware file, the target software file, task information to be executed and a construction model;
and returning the target mirror image to the data processing module (1).
By adopting the technical scheme, the method has the advantages that the process of generating the target image is placed in the proxy node: after the proxy node module outputs the target image, the data generated in the process of generating the target image is automatically cleared, so that the excessive intermediate data is prevented from occupying the running space of the data processing module.
The present application may be further configured in a preferred example to: the base image repository (4) is configured to:
receiving target hardware architecture, target software architecture, target hardware file, target software file and task information to be executed, which are sent by the data processing module (1);
obtaining a target mirror image according to the target hardware architecture, the target software architecture, the target hardware file, the target software file, task information to be executed and a construction model;
and returning the target mirror image to the data processing module (1).
By adopting the technical scheme, the process of generating the target image is placed in the basic image warehouse, and the advantages are that: the generated target image is automatically stored by the base image warehouse, so that the situation that excessive intermediate data occupy the running space of the data processing module is avoided, and the next call of the data processing module can be facilitated.
The present application may be further configured in a preferred example to: the data processing module is also connected with a user terminal and a remote container manager;
the user terminal and/or the remote container manager are/is configured to send the request construction instruction;
the remote container manager is also configured to receive the target image.
By adopting the technical scheme, the data processing module receives the request construction instruction sent by the user terminal and/or the remote container manager, so that the application can support standardized mirror image construction, namely the complex mirror image construction requirement of the remote container manager, and can also support the mirror image construction requirement of user terminal customization, thereby improving the practicability of the application.
The present application may be further configured in a preferred example to: the data processing module is further configured to: the system is used for receiving a request construction instruction input by any one of a text, a table or a voice.
By adopting the technical scheme, the application supports various modes for inputting the request construction instruction, thereby improving the practicability of the application.
The present application may be further configured in a preferred example to: the proxy node module is configured to: the hardware architecture and the software architecture disclosed in the network are collected through port scanning and web crawler technology.
By adopting the technical scheme, the hardware architecture and the software architecture are collected in two ways, so that the collected hardware architecture and software architecture resources are enriched.
The present application may be further configured in a preferred example to: after the agent node module gathers the hardware architecture and the software architecture, the agent node module further includes:
obtaining n multiplied by m groups of architecture combinations according to n hardware architectures, m software architectures and a preset dividing rule;
storing the n×m groups of architecture combinations into n×m groups of proxy nodes;
and n and m are positive integers more than 1.
By adopting the technical scheme, the n multiplied by m group architecture combinations are correspondingly stored in the n multiplied by m group proxy nodes, so that the data processing module can conveniently correspondingly call the required target hardware architecture and the target software architecture, and the call efficiency of the data processing module is improved. Meanwhile, the data processing module only calls the target hardware architecture and the target software architecture in one proxy node, so that the stability of the proxy node module is ensured.
The present application may be further configured in a preferred example to: the system also comprises a safety monitoring module, wherein the safety monitoring module is connected with the data processing module.
By adopting the technical scheme, the safety monitoring module is connected with the data processing module and is used for monitoring the operation process of the data processing module, thereby effectively monitoring illegal operation.
In summary, the present application includes at least one of the following beneficial technical effects:
1. the data processing module is arranged on the connecting centers of the agent node module, the supporting environment warehouse and the basic mirror image warehouse, and the data processing module is used for constructing various connected modules according to the request construction instruction so as to achieve the purpose of constructing different mirror images for the embedded system;
2. the data processing module receives a request construction instruction sent by the user terminal and/or the remote container manager, so that the application can support standardized image construction, namely complex image construction requirements of the remote container manager, and can also support user terminal customized image construction requirements, and the practicability of the application is improved.
Drawings
Fig. 1 is a diagram of a distributed mirror construction system according to an embodiment of the present application.
FIG. 2 is a flowchart of a method applied to a data processing module in an embodiment of the present application.
Fig. 3 is a flowchart of a method applied to a proxy node module in an embodiment of the present application.
Fig. 4 is a flowchart of a method applied to a base mirror warehouse in an embodiment of the present application.
Reference numerals illustrate: 1. a data processing module; 2. a proxy node module; 3. supporting an environmental warehouse; 4. a base mirror warehouse; 5. a safety monitoring module; 6. a user terminal; 7. a remote container manager.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
In addition, the term "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone.
Example 1:
the application provides a distributed mirror image construction system, which is arranged at a cloud end. Referring to fig. 1, the distributed mirror construction system includes a data processing module 1, a proxy node module 2, a supporting environment warehouse 3, a base mirror warehouse 4, and a security monitoring module 5. The data processing module 1 is a connection center, and is respectively in bidirectional communication with the agent node module 2, the supporting environment warehouse 3, the basic mirror image warehouse 4 and the safety monitoring module 5.
The data processing module 1 is also connected to a user terminal 6 and a remote container manager 7. The user terminal 6 is used for inputting a user-defined mirror image request construction instruction, and the user terminal 6 is electronic equipment such as a mobile phone, a tablet, a computer and the like. The remote container manager 7 is connected with an embedded system, the embedded system comprises a plurality of hardware platforms and software systems, and the container manager sends a mirror image request construction instruction to the data processing module 1 according to the mirror image construction requirement of the embedded system. That is, the present application supports customized image construction and standardized image construction.
In addition, the data processing module 1 also supports request construction instructions input in various modes such as characters, tables, voices and the like, so that the practicability of the application is improved.
Specifically, the present application supports customized image construction and standardized image construction including the following:
(1) The proxy node module 2 is established.
The disclosed hardware architecture and software architecture are collected from the network through port scanning, web crawlers and other technologies, and the hardware architecture and the software architecture can be supplemented in a manual entry mode. After abundant hardware architecture and software architecture resources are obtained, a hardware architecture and a software architecture are combined into a group of architecture combinations through preset division rules, and the group of architecture combinations are put into a proxy node, and the proxy node only stores the group of architecture combinations. For example, the hardware architecture has x86, ARM, RISC-V, C-SKY and MIPS, and the software architecture has liteOS, hopenOS, linux, and 15 groups of architecture combinations are obtained, respectively: [ x86, liteOS ], [ x86, hopenOS ], [ x86, linux ], [ ARM, liteOS ], [ ARM, hopenOS ], [ ARM, linux ], [ RISC-V, liteOS ], [ RISC-V, hopenOS ], [ RISC-V, linux ], [ C-SKY, liteOS ], [ C-SKY, hopenOS ], [ C-SKY, linux ], [ MIPS, liteOS ], [ MIPS, hopenOS ], [ MIPS, linux ].
Therefore, when there are N groups of hardware architecture and software architecture, N groups of proxy nodes are correspondingly generated, and the N groups of proxy nodes are mutually combined in parallel to form the proxy node module 2. The above N is an arbitrary positive integer of 1 or more.
In addition, in order to facilitate distinguishing between the hardware architecture before and after the proxy node is placed, the hardware architecture after the proxy node is placed is named as a target hardware architecture, and the software architecture after the proxy node is placed is named as a target software architecture.
(2) A supporting environment warehouse 3 is established.
Similar to the agent node module 2, the supporting environment warehouse 3 is also built to collect the disclosed hardware files and software files from the network through the techniques of port scanning, web crawlers and the like, and the hardware files and the software files can be supplemented through a manual entry mode. In the present embodiment, a hardware file refers to the smallest file system required under a hardware architecture, and a software file refers to the smallest file system required under a software architecture. For example, when the hardware architecture is X86, the hardware file may be a register, a processor, a clock, or an operating system or a device driver that collectively performs a task under the X86 hardware architecture.
After obtaining the hardware file and the software file, the hardware file and the software file are stored in the supporting environment warehouse 3 in a unified way. In the present embodiment, in order to facilitate distinguishing between the hardware files stored to the supporting environment repository 3 and the software files, the hardware files stored to the supporting environment repository 3 are named as target hardware files, and the software files stored to the supporting environment repository 3 are named as target software files.
In one possible implementation, the target hardware file and the target software file in the supporting environment repository 3 are stored separately; in another possible implementation, the target hardware file and the target software file that can collectively perform a task are stored in a tree structure, thereby facilitating subsequent management and invocation.
(3) A base image repository 4 is built.
The base image warehouse 4 stores a build model for combining the target hardware architecture, the target software architecture, the target hardware file and the target software file. The process of building the model to build the mirror image is as follows: firstly, extracting a target hardware architecture, and matching corresponding target hardware files according to the target hardware architecture to obtain a target hardware system; then, extracting a target software architecture, and matching corresponding target software files according to the target software architecture to obtain a target software system; and finally, combining the target hardware system and the target software system to form a target mirror image. After the build model is generated, the build model is stored in the base image repository 4.
In order to save the time for generating the target image, the process of generating the target hardware system and the process of generating the target software system can be synchronously performed, but in order to reduce the probability of confusion of the built target image, the starting time of generating the target hardware system cannot be later than the starting time of generating the target software system.
(4) A security monitoring module 5 is built.
The safety monitoring module 5 monitors the operation of the data processing module 1. The safety monitoring module 5 comprises a first monitoring sub-module, a second monitoring sub-module and a third monitoring sub-module. The first monitoring sub-module, the second monitoring sub-module and the third monitoring sub-module are all connected with the data processing module 1. The first monitoring sub-module is configured to monitor accuracy and authenticity of a request construction instruction received by the data processing module 1, for example, when the data processing module 1 receives the request construction instruction sent by the user terminal 6 and the remote container manager 7, the first monitoring sub-module returns identity authentication information to the corresponding user terminal 6 and remote container manager 7, and then receives identity authentication information fed back by the user terminal 6 and the remote container manager 7, and only when the identity authentication passes, the data processing platform starts to construct a mirror image; otherwise, when the identity verification fails, the first monitoring sub-module shields the request construction instruction, so that the safety of the mirror image construction system in the cloud is ensured. The second monitoring sub-module is used for recording the calling behavior of the data processing module 1, so as to effectively monitor illegal operation. The third monitoring sub-module is used for monitoring the generated target image, and when the target image needs to be kept secret, the target image is converted into ciphertext by adopting an encryption algorithm and then is output, so that the purpose that the target image is not stolen and read by illegal persons is achieved.
After the agent node module 2, the supporting environment warehouse 3, the basic mirror image warehouse 4 and the safety monitoring module 5 are sequentially built, the data processing module 1 is arranged on the connecting center of the agent node module 2, the supporting environment warehouse 3, the basic mirror image warehouse 4 and the safety monitoring module 5, the data processing module 1 is in bidirectional communication with the agent node module 2, the supporting environment warehouse 3, the basic mirror image warehouse 4 and the safety monitoring module 5, and the safety monitoring module 5 monitors the process of building the mirror image in real time.
After the agent node module 2, the supporting environment warehouse 3, the basic mirror image warehouse 4 and the safety monitoring module 5 are built, the end of the early preparation work of the mirror image construction is described, the built agent node module 2, the supporting environment warehouse 3, the basic mirror image warehouse 4 and the safety monitoring module 5 are stored in the cloud, and the mirror image construction system in the cloud can support the mirror image construction requirements of one or more embedded systems.
In this embodiment, since the data processing module 1 is disposed on the connection center of the agent node module 2, the supporting environment warehouse 3, the base mirror warehouse 4, and the security monitoring module 5, each connected module is mobilized by the data processing module 1 to implement the mirror construction requirement for supporting one or more embedded systems.
Referring to fig. 2, the data processing module 1 is configured to:
step S11: and acquiring a request construction instruction.
The request construction instruction is a control command transmitted to the data processing module 1 by the user terminal 6 and/or the remote container manager 7 as needed, and includes an initial hardware architecture, an initial software architecture, and task information to be executed. The initial hardware architecture refers to the hardware architecture required by the user terminal 6 and the remote container manager 7, and is named here to distinguish from the target hardware architecture stored in the proxy node module 2, and the initial software architecture is also named to distinguish from the target software architecture stored in the proxy node module 2. The task information to be executed refers to the function realized by the cooperation of the hardware architecture and the software architecture after the user terminal 6 and the remote container manager 7 call up the required hardware architecture and the software architecture, and can also be considered that the task information to be executed can assist the data processing module 1 to call up the target hardware file and the target software file later, and even be used as a standard for combining the target hardware architecture, the target software architecture, the target hardware file and the target software file.
When the data processing module 1 acquires the request construction instruction, the initial hardware architecture and the initial software architecture are extracted first, and the next step is entered after the extraction is completed.
Step S12: the target hardware architecture corresponding to the initial hardware architecture and the target software architecture corresponding to the initial software architecture are invoked.
After the data processing module 1 extracts the initial hardware architecture, one or more proxy nodes are determined according to the corresponding relation between the initial hardware architecture and the target hardware architecture, and then the final proxy nodes are further positioned according to the corresponding relation between the initial software architecture and the target software architecture, and the target hardware architecture and the target software architecture in the final proxy nodes are called. For example, there are proxy nodes: [ x86, liteOS ], [ x86, hopenOS ], [ x86, linux ], [ ARM, liteOS ], [ ARM, hopenOS ], [ ARM, linux ], [ RISC-V, liteOS ], [ RISC-V, hopenOS ], if the initial hardware architecture is x86, the proxy node is first located: [ x86, liteOS ], [ x86, hopenOS ], [ x86, linux ], if the initial software architecture is Linux, the final proxy node is [ x86, linux ].
It should be noted that, the above process of invoking the target hardware architecture and the target software architecture is merely exemplary, for example, one or more proxy nodes may be determined according to the corresponding relationship between the initial software architecture and the target software architecture, and then the final proxy node may be obtained according to the corresponding relationship between the initial hardware architecture and the target hardware architecture.
Step S13: the target hardware file corresponding to the initial hardware architecture and the target software file corresponding to the initial software architecture are invoked.
In this embodiment, after the data processing module 1 retrieves the target hardware architecture and the target software architecture, the corresponding target hardware file is retrieved from the supporting environment warehouse 3 according to the initial hardware architecture in the request construction instruction, and the corresponding target software file is retrieved from the supporting environment warehouse 3 according to the initial software architecture in the request construction instruction. In the present embodiment, the order in which the target hardware file and the target software file are called is not limited.
In other embodiments, the data processing module 1 may also call the corresponding target hardware file from the supporting environment warehouse 3 according to the target hardware architecture and the task information to be executed, and call the corresponding target software file from the supporting environment warehouse 3 according to the target software architecture and the task information to be executed.
Step S14: and retrieving the construction model, and obtaining a target mirror image according to the construction model, the target hardware architecture, the target software architecture, the target hardware file, the target software file and the task information to be executed.
After the data processing module 1 obtains the target hardware architecture, the target software architecture, the target hardware file and the target software file, the model is called from the base mirror image warehouse 4. And then inputting the target hardware architecture, the target software architecture, the target hardware file and the target software file into a building model, and combining the target hardware architecture, the target software architecture, the target hardware file and the target software file according to the task information to be executed and the building principle by the building model to obtain a target mirror image.
The construction principle of the construction model is already described when the base mirror warehouse 4 is constructed, so that the description thereof will not be repeated here.
After the data processing module 1 generates the target image, the security monitoring module 5 detects the target image, and then the data processing module 1 returns the target image which passes the security detection to the remote container manager 7, and the backup target image is also generated and stored in the base image warehouse 4. The advantage of placing the process of generating the target image in the data processing module 1 is that: when the data processing module 1 receives the request construction instruction with the same content, the target image can be directly fetched from the base image warehouse 4, so that the operation amount of the distributed image construction system is reduced.
The implementation principle of the distributed mirror image construction system in embodiment 1 of the present application is as follows: the data processing module 1 serves as a dispatching center, when receiving a request construction instruction, the corresponding target hardware architecture and target software architecture are called from the proxy node module 2, target hardware files are called in the supporting environment warehouse 3 according to the target hardware architecture, target software files are called in the supporting environment warehouse 3 according to the target software architecture, and a construction model is called from the basic mirror image warehouse 4. And finally, inputting the target hardware architecture, the target software architecture, the target hardware file and the target software file into a building model, and outputting a target mirror image by the building model. It can be seen that, in embodiment 1, the data processing module 1 invokes each module according to the request building instruction, so as to support customized image building and standardized image building, i.e. the distributed image building system can be suitable for use in complex image building requirements.
Example 2:
referring to fig. 3, the proxy node module 2 is configured to:
step S21: receiving target hardware architecture, target software architecture, target hardware file, target software file and task information to be executed, which are sent by the data processing module 1;
step S22: receiving a built model sent by the data processing module 1;
step S23: obtaining a target mirror image according to a target hardware architecture, a target software architecture, a target hardware file, a target software file, task information to be executed and a construction model;
step S24: the target image is returned to the data processing module 1.
The above steps S21 to S24 can be briefly described as: the data processing module 1 sends the invoked target hardware architecture, target software architecture, target hardware file, target software file and build model to the proxy node module 2, and inputs the task information to be executed extracted from the request building instruction into the proxy node module 2, and the task information is executed by the proxy node module 2: inputting the target hardware architecture, the target software architecture, the target hardware file and the target software file into a building model, and combining the target hardware architecture, the target software architecture, the target hardware file and the target software file according to the task information to be executed and the building principle by the building model to obtain a target mirror image.
In embodiment 2, the advantage of placing the process of generating the target image in the proxy node module 2 is that: after the proxy node module 2 outputs the target image, data generated in the process of generating the target image is automatically cleared, so that excessive intermediate data is prevented from occupying the running space of the data processing module 1.
Example 3:
referring to fig. 4, the base image repository 4 is configured to:
step S31: receiving target hardware architecture, target software architecture, target hardware file, target software file and task information to be executed, which are sent by the data processing module 1;
step S32: obtaining a target mirror image according to the construction model, the target hardware architecture, the target software architecture, the target hardware file, the target software file and the task information to be executed;
step S33: the target image is returned to the data processing module 1.
The process of steps S31 to S33 can be briefly described as follows: firstly, after acquiring a target hardware architecture, a target software architecture, a target hardware file, a target software file and task information to be executed, which are sent by a data processing module 1, a base image warehouse 4 inputs the target hardware architecture, the target software architecture, the target hardware file and the target software file into a building model, the building model combines the target hardware architecture, the target software architecture, the target hardware file and the target software file according to the task information to be executed and a built-in building principle to obtain a target image, and finally outputs the target image.
In embodiment 3, the advantage of placing the process of generating the target image in the base image repository 4 is that: the generated target image is automatically saved by the base image warehouse 4, so that not only is the excessive intermediate data prevented from occupying the running space of the data processing module 1, but also the next call of the data processing module 1 can be facilitated.
The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this application is not limited to the specific combinations of features described above, but it is intended to cover other embodiments in which any combination of features described above or equivalents thereof is possible without departing from the spirit of the disclosure. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.
Claims (6)
1. The utility model provides a distributed mirror image construction system, sets up at the high in the clouds, its characterized in that: the system comprises a data processing module (1), an agent node module (2), a supporting environment warehouse (3) and a basic mirror image warehouse (4);
the data processing module (1) is respectively connected with the agent node module (2), the supporting environment warehouse (3) and the basic mirror image warehouse (4), and the agent node module (2), the supporting environment warehouse (3) and the basic mirror image warehouse (4) are mutually connected in parallel;
the agent node module (2) comprises a plurality of agent nodes, and the agent nodes store a target hardware architecture and a target software architecture;
the supporting environment warehouse (3) stores target hardware files and target software files;
a built model is stored in the basic mirror image warehouse (4);
the data processing module (1) is configured to:
acquiring a request construction instruction, wherein the request construction instruction comprises an initial hardware architecture, an initial software architecture and task information to be executed;
a target hardware architecture corresponding to the initial hardware architecture and a target software architecture corresponding to the initial software architecture are called in the proxy node module (2);
a target hardware file corresponding to an initial hardware architecture and a target software file corresponding to an initial software architecture are called in the supporting environment warehouse (3);
obtaining a target mirror image according to the target hardware architecture, the target software architecture, the target hardware file, the target software file, task information to be executed and a construction model; or (b)
The proxy node module (2) is configured to:
receiving target hardware architecture, target software architecture, target hardware file, target software file and task information to be executed, which are sent by the data processing module (1);
obtaining a target mirror image according to the target hardware architecture, the target software architecture, the target hardware file, the target software file, task information to be executed and a construction model;
returning the target mirror image to the data processing module (1); or alternatively
The base image repository (4) is configured to:
receiving target hardware architecture, target software architecture, target hardware file, target software file and task information to be executed, which are sent by the data processing module (1);
obtaining a target mirror image according to the target hardware architecture, the target software architecture, the target hardware file, the target software file, task information to be executed and a construction model;
and returning the target mirror image to the data processing module (1).
2. The distributed mirror build system of claim 1, wherein: the data processing module (1) is also connected with a user terminal (6) and a remote container manager (7);
-said user terminal (6) and/or said remote container manager (7) being adapted to send said request construction instruction;
the remote container manager (7) is further configured to receive the target image.
3. The distributed mirror build system of claim 1, wherein: the data processing module (1) is further configured to: the system is used for receiving a request construction instruction input by any one of a text, a table or a voice.
4. The distributed mirror build system of claim 1, wherein: the proxy node module (2) is further configured to: the hardware architecture and the software architecture disclosed in the network are collected through port scanning and web crawler technology.
5. The distributed mirror build system of claim 4, wherein: after the agent node module (2) gathers the hardware architecture and the software architecture, the agent node module further comprises:
obtaining n multiplied by m groups of architecture combinations according to n hardware architectures, m software architectures and a preset dividing rule;
storing the n×m groups of architecture combinations into n×m groups of proxy nodes;
and n and m are positive integers more than 1.
6. The distributed mirror build system of claim 1, wherein: the system further comprises a safety monitoring module (5), wherein the safety monitoring module (5) is connected with the data processing module (1).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211344605.3A CN115826995B (en) | 2022-10-31 | 2022-10-31 | Distributed mirror image construction system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211344605.3A CN115826995B (en) | 2022-10-31 | 2022-10-31 | Distributed mirror image construction system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115826995A CN115826995A (en) | 2023-03-21 |
| CN115826995B true CN115826995B (en) | 2023-07-14 |
Family
ID=85525879
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211344605.3A Active CN115826995B (en) | 2022-10-31 | 2022-10-31 | Distributed mirror image construction system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115826995B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110413294A (en) * | 2019-08-06 | 2019-11-05 | 中国工商银行股份有限公司 | Service delivery system, method, apparatus and equipment |
| WO2020135492A1 (en) * | 2018-12-26 | 2020-07-02 | 中兴通讯股份有限公司 | Software hierarchical management system |
| CN112231052A (en) * | 2020-09-29 | 2021-01-15 | 中山大学 | High-performance distributed container mirror image distribution system and method |
| CN113886016A (en) * | 2021-09-30 | 2022-01-04 | 联想(北京)有限公司 | Method and device for generating mirror image file |
| CN114416296A (en) * | 2022-01-11 | 2022-04-29 | 浪潮云信息技术股份公司 | Starting speed-up method and system for large-scale cluster container with hybrid CPU framework |
| CN114490037A (en) * | 2021-12-28 | 2022-05-13 | 深圳云天励飞技术股份有限公司 | Mirror image deployment method and device, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268312B (en) * | 2021-05-14 | 2022-08-02 | 济南浪潮数据技术有限公司 | Application migration method and system |
-
2022
- 2022-10-31 CN CN202211344605.3A patent/CN115826995B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020135492A1 (en) * | 2018-12-26 | 2020-07-02 | 中兴通讯股份有限公司 | Software hierarchical management system |
| CN110413294A (en) * | 2019-08-06 | 2019-11-05 | 中国工商银行股份有限公司 | Service delivery system, method, apparatus and equipment |
| CN112231052A (en) * | 2020-09-29 | 2021-01-15 | 中山大学 | High-performance distributed container mirror image distribution system and method |
| CN113886016A (en) * | 2021-09-30 | 2022-01-04 | 联想(北京)有限公司 | Method and device for generating mirror image file |
| CN114490037A (en) * | 2021-12-28 | 2022-05-13 | 深圳云天励飞技术股份有限公司 | Mirror image deployment method and device, electronic equipment and storage medium |
| CN114416296A (en) * | 2022-01-11 | 2022-04-29 | 浪潮云信息技术股份公司 | Starting speed-up method and system for large-scale cluster container with hybrid CPU framework |
Non-Patent Citations (1)
| Title |
|---|
| Docker技术在乘客信息系统部署中的应用;田源;李樊;汪晓臣;赵伟慧;黄志威;;铁路计算机应用(第05期);第75-78页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115826995A (en) | 2023-03-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7099442B2 (en) | Telephony and voice interface for voice server system management | |
| CN109660377B (en) | Unified configuration management method, service server and operation maintenance management platform | |
| CN112235400B (en) | Communication method, communication system, communication device, server, and storage medium | |
| CN103731479B (en) | One kind connects method and system of dealing with emergencies and dangerous situations | |
| CN101848374A (en) | Wireless video monitoring system and wireless video monitoring method thereof | |
| CN113467972B (en) | Communication interface construction method and device, computer equipment and storage medium | |
| CN113821363B (en) | Inter-process communication method and system | |
| CN110958206A (en) | Data security method for mobile equipment application based on virtualization | |
| CN114416877A (en) | Data processing method, device and equipment and readable storage medium | |
| CN113722754A (en) | Generation method and device of privacy executable file and server | |
| CN115826995B (en) | Distributed mirror image construction system | |
| CN114285659A (en) | Reverse proxy method, device, equipment and storage medium | |
| CN116974948B (en) | Service system testing method, system, equipment and medium | |
| CN111488286B (en) | Method and device for independently developing Android modules | |
| CN113132678A (en) | Data transmission method and device, electronic equipment and storage medium | |
| CN115438323A (en) | Enterprise application system integration device and method based on micro-service | |
| CN114675876B (en) | Service processing method and device, electronic equipment and storage medium | |
| CN110958267B (en) | Method and system for monitoring threat behaviors in virtual network | |
| CN106228667A (en) | Hardware number calling system for state and place tax combined office | |
| CN113724711A (en) | Method, device, system, medium and equipment for realizing voice recognition service | |
| CN114268653B (en) | Equipment calling method, device, equipment, medium and product | |
| CN112037796B (en) | Data processing method, device, equipment and medium | |
| CN112560089B (en) | Sensitive information early warning device and method for interface service | |
| CN117591589A (en) | Smart city system, method, apparatus and storage medium | |
| CN113918242A (en) | Application programming interface calling method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |