CN114157658A - Mirror image warehouse deployment method and device, electronic equipment and computer readable medium - Google Patents
Mirror image warehouse deployment method and device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN114157658A CN114157658A CN202111479396.9A CN202111479396A CN114157658A CN 114157658 A CN114157658 A CN 114157658A CN 202111479396 A CN202111479396 A CN 202111479396A CN 114157658 A CN114157658 A CN 114157658A
- Authority
- CN
- China
- Prior art keywords
- target
- mirror image
- instance
- mirror
- image warehouse
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000004590 computer program Methods 0.000 claims description 9
- 238000012423 maintenance Methods 0.000 claims description 7
- 238000004458 analytical method Methods 0.000 claims description 6
- 238000013507 mapping Methods 0.000 claims description 5
- 230000004931 aggregating effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 13
- 239000003795 chemical substances by application Substances 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 238000004891 communication Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the disclosure discloses a mirror image warehouse deployment method, a mirror image warehouse deployment device, an electronic device and a computer readable medium. One embodiment of the method comprises: starting a mirror image warehouse instance in a first target server corresponding to the first target server information as a target mirror image warehouse instance; deploying an application publishing terminal, and uploading a target file sent by the application publishing terminal to a target mirror image warehouse instance as a mirror image; deploying at least one middleware; writing middleware information of each middleware in the at least one middleware into each mirror image warehouse instance configuration corresponding to the at least one second target server, and starting each mirror image warehouse instance in the at least one second target server according to each mirror image warehouse instance configuration written with the middleware information; deployment of the mirror repository instance cluster is performed. The method and the system can quickly and efficiently deploy the stable, high-availability and product-level mirror image warehouse.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computers, in particular to a mirror image warehouse deployment method, a mirror image warehouse deployment device, an electronic device and a computer readable medium.
Background
For deploying a mirror repository that can use various highly available versions of middleware services, the following methods are generally adopted: before creating a paas Platform (Platform-as-a-Service), a simple, non-highly available version of the mirror warehouse building Service (docker registry Service) is used. Then, the paas platform is started according to the built service, so that a high-availability product-level mirror warehouse is further deployed. Wherein, the mirror repository deployed according to the paas platform can use middleware services of various high-availability versions.
However, when the above-mentioned method is adopted to deploy a high-available product-level mirror warehouse, the following technical problems often exist:
when the simple mirror image warehouse of the non-high available version goes down, the paas platform is affected and cannot provide paas service, so that the mirror image warehouse deployed according to the paas platform cannot use the middleware service of each high available version.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Some embodiments of the present disclosure propose mirror repository deployment methods, apparatuses, electronic devices and computer readable media to address one or more of the technical problems mentioned in the background section above.
In a first aspect, some embodiments of the present disclosure provide a mirror repository deployment method, including:
starting a mirror image warehouse instance in a first target server corresponding to the first target server information as a target mirror image warehouse instance; deploying an application publishing terminal by using the target mirror image warehouse example, and uploading a target file sent by the application publishing terminal as a mirror image to the target mirror image warehouse example; deploying at least one middleware by utilizing the deployed application publishing terminal; writing middleware information of each middleware in the at least one middleware into each mirror image warehouse instance configuration corresponding to at least one second target server, so as to start each mirror image warehouse instance in the at least one second target server according to each mirror image warehouse instance configuration written with the middleware information, wherein each second target server in the at least one second target server has corresponding second target server information; and executing the deployment of the mirror image warehouse instance cluster according to the mirror image warehouse instances and the target mirror image warehouse instance comprising the mirror image.
Optionally, the starting the mirror warehouse instance in the first target server corresponding to the first target server information includes: starting a target file storage system in the first target server; configuring a configuration file aiming at the mirror image maintenance system in the target file storage system; and starting a mirror image warehouse instance in the first target server according to the configuration file.
Optionally, after the mirror repository instance is started in the first target server corresponding to the first target server information, the method further includes: determining target domain name resolution information, wherein the target domain name resolution information represents a mapping relation between a domain name corresponding to the target mirror image warehouse instance and an internet protocol address corresponding to the target mirror image warehouse instance; and sending the target domain name resolution information to a target domain name resolution server to register the domain name resolution information.
Optionally, the starting the mirror warehouse instance in the first target server corresponding to the first target server information includes: starting a target file storage system in the first target server; configuring a configuration file aiming at the mirror image maintenance system in the target file storage system; and starting a mirror image warehouse instance in the first target server according to the configuration file.
Optionally, the deploying the application distributor by using the target mirror repository instance includes: initializing a container arranging end by utilizing the first target server; and deploying the application issuing end by utilizing the initialized container arranging end and the target mirror image warehouse example.
Optionally, the executing the deployment of the mirror repository instance cluster according to the mirror repository instances and the target mirror repository instance including the mirror includes: setting state information of the target mirror image warehouse example and restarting the target mirror image warehouse example after the state information is set; migrating the mirror image in the target mirror image warehouse example after the first restart to each mirror image warehouse example; updating the mirror image warehouse instance configuration corresponding to the target mirror image warehouse instance, and restarting the target mirror image warehouse instance after updating the mirror image warehouse instance configuration; and migrating each mirrored warehouse instance after mirroring according to the mirrored warehouse instance after the second restart, and executing the deployment of the mirrored warehouse instance cluster.
Optionally, after the performing the deployment of the mirror repository instance cluster according to the mirror repository instances and the target mirror repository instance including the mirror, the method further includes: determining the internet protocol address of the first target server and the internet protocol address of at least one second target server; aggregating the internet protocol address of the first target server and the internet protocol address of the at least one second target server to generate a target internet protocol address; and updating the domain name resolution information in the target domain name resolution server according to the target Internet protocol address.
Optionally, the method further includes: and analyzing the updated domain name analysis information to obtain the cluster information of the mirror image warehouse instance cluster.
In a second aspect, some embodiments of the present disclosure provide an image repository deployment apparatus, comprising: the starting unit is configured to start the mirror image warehouse instance in a first target server corresponding to the first target server information to serve as a target mirror image warehouse instance; the deployment uploading unit is configured to deploy an application publishing terminal by using the target mirror image warehouse instance, and upload a target file sent by the application publishing terminal to the target mirror image warehouse instance as a mirror image; the deployment unit is configured to deploy at least one middleware by utilizing the deployed application publishing terminal; a writing unit, configured to write middleware information of each middleware in the at least one middleware into each mirror image repository instance configuration corresponding to at least one second target server, so as to start each mirror image repository instance in the at least one second target server according to each mirror image repository instance configuration after the middleware information is written, where each second target server in the at least one second target server has corresponding second target server information; and the execution unit is configured to execute the deployment of the mirror image warehouse instance cluster according to the mirror image warehouse instances and the target mirror image warehouse instance comprising the mirror image.
Optionally, the starting unit is further configured to: starting a target file storage system in the first target server; configuring a configuration file aiming at the mirror image maintenance system in the target file storage system; and starting a mirror image warehouse instance in the first target server according to the configuration file.
Optionally, the apparatus further comprises: determining target domain name resolution information, wherein the target domain name resolution information represents a mapping relation between a domain name corresponding to the target mirror image warehouse instance and an internet protocol address corresponding to the target mirror image warehouse instance; and sending the target domain name resolution information to a target domain name resolution server to register the domain name resolution information.
Optionally, the deployment upload unit is further configured to: initializing a container arranging end by utilizing the first target server; and deploying the application issuing end by utilizing the initialized container arranging end and the target mirror image warehouse example.
Optionally, the execution unit is further configured to: setting state information of the target mirror image warehouse example and restarting the target mirror image warehouse example after the state information is set; migrating the mirror image in the target mirror image warehouse example after the first restart to each mirror image warehouse example; updating the mirror image warehouse instance configuration corresponding to the target mirror image warehouse instance, and restarting the target mirror image warehouse instance after updating the mirror image warehouse instance configuration; and migrating each mirrored warehouse instance after mirroring according to the mirrored warehouse instance after the second restart, and executing the deployment of the mirrored warehouse instance cluster.
Optionally, the apparatus further comprises: determining the internet protocol address of the first target server and the internet protocol address of at least one second target server; aggregating the internet protocol address of the first target server and the internet protocol address of the at least one second target server to generate a target internet protocol address; and updating the domain name resolution information in the target domain name resolution server according to the target Internet protocol address.
Optionally, the apparatus further comprises: and analyzing the updated domain name analysis information to obtain the cluster information of the mirror image warehouse instance cluster.
In a third aspect, some embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors, cause the one or more processors to implement the method as described in any of the implementations of the first aspect.
In a fourth aspect, some embodiments of the disclosure provide a computer readable medium having a computer program stored thereon, where the program when executed by a processor implements a method as described in any of the implementations of the first aspect.
The above embodiments of the present disclosure have the following beneficial effects: the mirror image warehouse deployment method of some embodiments of the present disclosure can quickly and efficiently deploy mirror image warehouses that can use middleware services of various highly available versions. In particular, the reason why it is not efficient to deploy a mirror repository that can use various highly available versions of middleware services is that: when the simple mirror image warehouse of the non-high available version goes down, the paas platform is affected and cannot provide paas service, so that the mirror image warehouse deployed according to the paas platform cannot use the middleware service of each high available version. Based on this, the mirror image warehouse deployment method according to some embodiments of the present disclosure may first start the mirror image warehouse instance in the first target server corresponding to the first target server information, and use the mirror image warehouse instance as the target mirror image warehouse instance for subsequently deploying the application distributor. Here, the deployment of the application publisher depends on the deployed mirror repository instance. And then, deploying the application issuing end by utilizing the target mirror image warehouse example. And uploading the target file sent by the application publishing terminal as an image to the target image warehouse instance. The subsequent deployment of at least one middleware can be realized only by deploying the application publishing terminal. In addition, the target file sent by the application publishing terminal is used as an image and uploaded to the image warehouse instance for deployment of a subsequent image warehouse instance cluster. And then, by utilizing the deployed application publishing terminal, at least one highly available middleware can be efficiently and quickly deployed. And further writing the middleware information of each middleware in the at least one middleware into each mirror image warehouse instance configuration corresponding to the at least one second target server, so as to start each mirror image warehouse instance in the at least one second target server according to each mirror image warehouse instance configuration written with the middleware information. And each second target server in the at least one second target server has corresponding second target server information. Here, by writing the middleware information of each middleware into the mirror repository instance configuration in the at least one second target server, there is each highly available middleware in the subsequent at least one second target server that can be relied upon. And finally, according to the mirror image warehouse instances and the target mirror image warehouse instance comprising the mirror image, the deployment of the mirror image warehouse instance cluster is efficiently executed. Thus, a stable, highly available mirror repository instance cluster is generated.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
FIG. 1 is a schematic diagram of one application scenario of a mirror warehouse deployment method, in accordance with some embodiments of the present disclosure;
FIG. 2 is a flow diagram of some embodiments of a mirror warehouse deployment method according to the present disclosure;
FIG. 3 is a schematic diagram of obtaining first target server information and at least one second target server information in some embodiments of a mirror warehouse deployment method in accordance with the present disclosure;
FIG. 4 is a flow diagram of further embodiments of a mirror warehouse deployment method according to the present disclosure;
FIG. 5 is a schematic block diagram of some embodiments of mirrored warehouse deployment devices, according to the present disclosure;
FIG. 6 is a schematic structural diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings. The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 is a schematic diagram of one application scenario of a mirror warehouse deployment method according to some embodiments of the present disclosure.
In the application scenario of fig. 1, the electronic device 101 may first start a mirror repository instance in the first target server 103 corresponding to the first target server information 102 as a target mirror repository instance 104. The electronic device 101 can then deploy the application distributor 105 using the target mirror repository instance 104 described above. And the electronic device 101 may upload the target file sent by the application distributor 105 to the target mirror repository instance 104 as an image. Next, the electronic device 101 may deploy at least one middleware 106 by using the deployed application publishing terminal 105. Furthermore, the electronic device 101 may write the middleware information 107 of each middleware in the at least one middleware 106 into a mirror repository instance configuration corresponding to at least one second target server, so as to start each mirror repository instance in the at least one second target server according to each mirror repository instance configuration after the middleware information is written. And each second target server in the at least one second target server has corresponding second target server information. In this application scenario, the at least one second target server information corresponding to the at least one second target server includes: second target server information 108 and second target server information 109. The electronic device 101 may write the middleware information 107 of each middleware into the mirror repository instance configuration 112 corresponding to the mirror repository instance 111 in the second target server 110 corresponding to the second target server information 108. Similarly, the electronic device 101 may write the middleware information 107 of each middleware into the mirror repository instance configuration 115 corresponding to the mirror repository instance 114 in the second target server 113 corresponding to the second target server information 109. Finally, deployment of the mirror repository instance cluster 116 is performed based on the various mirror repository instances and the target mirror repository instance 104 that includes the mirror.
The electronic device 101 may be hardware or software. When the electronic device is hardware, the electronic device may be implemented as a distributed cluster formed by a plurality of servers or terminal devices, or may be implemented as a single server or a single terminal device. When the electronic device is embodied as software, it may be installed in the above-listed hardware devices. It may be implemented, for example, as multiple software or software modules to provide distributed services, or as a single software or software module. And is not particularly limited herein.
It should be understood that the number of electronic devices in fig. 1 is merely illustrative. There may be any number of electronic devices, as desired for implementation.
With continued reference to fig. 2, a flow 200 of some embodiments of a mirror warehouse deployment method in accordance with the present disclosure is shown. The mirror image warehouse deployment method comprises the following steps:
In some embodiments, an executing entity (e.g., the electronic device shown in fig. 1) of the image repository deployment method may start an image repository instance in a first target server corresponding to the first target server information, as a target image repository instance. The first target server information may be server information of the first target server. For example, identification information of the first target server, location information of the first target server. The first target server information may be selected from a pre-constructed server information list. The mirror repository is a repository that centrally stores mirrors. The mirror (Image) may be a mirror Image involved in container technology. The mirror repository instance may be an instance of a mirror repository built in the first target server.
As an example, the execution principal may start the mirror repository instance in the first target server via "docker run-d < docker registry mirror >" in the docker command. Where docker registry is an open source product of the mirror warehouse, product v2 may be used, and the name distribution is given in github.
In some optional implementation manners of some embodiments, the starting the mirror repository instance in the first target server corresponding to the first target server information may include the following steps:
in a first step, the executing agent may start a target file storage system in the first target server. The target file storage system may be a system capable of providing the S3 service.
In a second step, the executing agent may configure a configuration file for the image maintenance system in the target file storage system. The image maintenance system can be a system capable of providing image warehouse building service.
Third, the execution agent may start an image repository instance in the target server according to the configuration file.
As an example, the execution agent may start a mirror warehouse instance in the first target server according to the configuration file by using a relevant docker command.
In some optional implementations of some embodiments, after step 201, the above step further includes:
first, the execution subject may determine target domain name resolution information. The target Domain name resolution information represents a mapping relationship between a Domain name (Domain name) corresponding to the target mirror image warehouse instance and an Internet Protocol address (IP, Internet Protocol) corresponding to the target mirror image warehouse instance.
In a second step, the execution subject may send the target domain name resolution information to a target domain name resolution server (DNS server) to register domain name resolution information.
In some embodiments, the execution agent may deploy an application distributor using the target image repository instance, and upload a target file sent by the application distributor as an image to the target image repository instance. The application publishing terminal may be a paas platform. The paas platform may be a publishing platform of an application marketplace. For example, the paas platform provides applications for mysql relational database management systems, postgresql, redis, and the like. Correspondingly, the user selects the application of mysql in the application market of the paas platform, and then a high-availability mysql cluster is created by selecting the cluster creation. The target file is a file generated at the deployment application issuing end and used for initializing the deployment application issuing end.
In some optional implementation manners of some embodiments, the deploying the application distributor by using the target mirror repository instance may include the following steps:
in a first step, the execution agent may initialize a container arrangement end by using the first target server. Wherein, the container arranging end is used for managing and controlling the container. E.g., a K8s cluster.
And secondly, the execution main body can deploy the application publishing end by utilizing the initialized container arranging end and the target mirror image warehouse instance.
By way of example, the execution subject may utilize the initialized container orchestration end to arrange tasks for deploying the application publisher according to the target mirror repository instance, and the deployment of the application publisher is completed.
And 203, deploying at least one middleware by utilizing the deployed application publishing terminal.
In some embodiments, the execution agent may deploy at least one middleware using the deployed application publishing terminal. The middleware can be a kind of software between the application system and the system software, and it uses the basic service (function) provided by the system software to connect each part of the application system or different applications on the network, so as to achieve the purpose of resource sharing and function sharing. For example, the at least one middleware may include, but is not limited to, at least one of: s3 Service (Simple Storage Service), postgresql-relational database management system, Remote Dictionary Service (Redis).
As an example, the execution body may call a target interface of the deployed application publishing terminal to deploy at least one middleware.
In some embodiments, the execution subject may write middleware information of each middleware in the at least one middleware into each mirror repository instance configuration corresponding to the at least one second target server, so as to start each mirror repository instance in the at least one second target server according to each mirror repository instance configuration after the middleware information is written. And each second target server in the at least one second target server has corresponding second target server information. The middleware information may be configuration information of the middleware. For example, version information of the middleware, link information of the middleware. The second target server information may be server information of the second target server. For example, identification information of the second target server, location information of the second target server. The at least one second target server information may be selected from a pre-constructed server information list. The number of the at least one second target server may be preset. For example 3.
As an example, as shown in fig. 3, the first target server information and the at least one second target server information may be selected from the same table shown in fig. 3. The number of the first target server information may be 1. The number of the at least one second target server information is 3.
In some embodiments, the execution agent may perform deployment of a mirror repository instance cluster according to the respective mirror repository instances and a target mirror repository instance comprising the mirror. Wherein the mirror warehouse instance cluster is a mirror warehouse cluster of a high available product level.
As an example, the execution agent may first migrate the image in the target image repository instance to the respective image repository instance. The mirror repository instance configuration of the target mirror repository instance is then updated. And finally, determining the target mirror image warehouse after the updating and each mirror image warehouse after the mirror image migration as a cluster node in the mirror image warehouse instance cluster so as to obtain the deployed mirror image warehouse instance cluster.
The above embodiments of the present disclosure have the following beneficial effects: the mirror image warehouse deployment method of some embodiments of the present disclosure can quickly and efficiently deploy mirror image warehouses that can use middleware services of various highly available versions. In particular, the reason why it is not efficient to deploy a mirror repository that can use various highly available versions of middleware services is that: when the simple mirror image warehouse of the non-high available version goes down, the paas platform is affected and cannot provide paas service, so that the mirror image warehouse deployed according to the paas platform cannot use the middleware service of each high available version. Based on this, the mirror image warehouse deployment method according to some embodiments of the present disclosure may first start the mirror image warehouse instance in the first target server corresponding to the first target server information, and use the mirror image warehouse instance as the target mirror image warehouse instance for subsequently deploying the application distributor. Here, the deployment of the application publisher depends on the deployed mirror repository instance. And then, deploying the application issuing end by utilizing the target mirror image warehouse example. And uploading the target file sent by the application publishing terminal as an image to the target image warehouse instance. The subsequent deployment of at least one middleware can be realized only by deploying the application publishing terminal. In addition, the target file sent by the application publishing terminal is used as an image and uploaded to the image warehouse instance for deployment of a subsequent image warehouse instance cluster. And then, by utilizing the deployed application publishing terminal, at least one highly available middleware can be efficiently and quickly deployed. And further writing the middleware information of each middleware in the at least one middleware into each mirror image warehouse instance configuration corresponding to the at least one second target server, so as to start each mirror image warehouse instance in the at least one second target server according to each mirror image warehouse instance configuration written with the middleware information. And each second target server in the at least one second target server has corresponding second target server information. Here, by writing the middleware information of each middleware into the mirror repository instance configuration in the at least one second target server, there is each highly available middleware in the subsequent at least one second target server that can be relied upon. And finally, according to the mirror image warehouse instances and the target mirror image warehouse instance comprising the mirror image, the deployment of the mirror image warehouse instance cluster is efficiently executed. Thus, a stable, highly available mirror repository instance cluster is generated.
With further reference to fig. 4, a flow 400 of further embodiments of a mirror warehouse deployment method according to the present disclosure is shown. The mirror image warehouse deployment method comprises the following steps:
And 403, deploying at least one middleware by using the deployed application publishing terminal.
In some embodiments, the specific implementation of steps 401 and 404 and the technical effect thereof can refer to steps 201 and 204 in the embodiment corresponding to fig. 2, and are not described herein again.
In some embodiments, an executing agent (e.g., the electronic device shown in fig. 1) may set the state information of the target mirror repository instance and restart the target mirror repository instance after the state information is set.
As an example, the executing entity may set the state information of the target mirror repository instance as: the "read-only state".
As yet another example, the execution principal may set state information of the mirror warehouse instance in the first target server through an associated interface.
And step 406, migrating the mirror image in the target mirror image warehouse instance after the first restart to each mirror image warehouse instance.
In some embodiments, the execution subject may migrate the image in the target image repository instance after the first reboot into each of the image repository instances.
As an example, the execution subject may migrate the mirror in the target mirror warehouse instance after the first reboot into each mirror warehouse instance through a related docker (container) command.
In some embodiments, the execution subject may update the mirror repository instance configuration corresponding to the target mirror repository instance, and restart the target mirror repository instance after updating the mirror repository instance configuration.
As an example, the execution subject updates the mirror repository instance configuration corresponding to the target mirror repository instance through the related command and the mirror repository instance configuration of each mirror repository instance after the mirror is migrated.
As another example, the mirror repository instance configuration corresponding to the target mirror repository instance is updated to serve as a node of the subsequent mirror repository instance cluster.
And step 408, migrating each mirrored warehouse instance after mirroring according to the mirrored warehouse instance after the second restart, and executing the deployment of the mirrored warehouse instance cluster.
In some embodiments, the execution subject may migrate each mirrored warehouse instance after mirroring according to the mirrored warehouse instance after the second reboot, and execute the deployment of the mirrored warehouse instance cluster.
As an example, the execution subject may use the mirror repository instance after the second reboot and the mirror repository instance in the at least one second target server after the mirror is migrated as child nodes of the cluster, so as to generate the mirror repository instance cluster.
As can be seen from fig. 4, compared with the description of some embodiments corresponding to fig. 2, the flow 400 of the mirror repository deployment method in some embodiments corresponding to fig. 4 highlights how to perform the specific steps of deploying the mirror repository instance cluster according to the mirror repository instance started in the at least one second target server and the mirror repository instance started in the first target server and including the mirror. Therefore, the solutions described in the embodiments can efficiently and quickly implement the high-availability product-level mirror warehouse embodiment cluster in a self-starting manner.
With further reference to fig. 5, as an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a mirror warehouse deployment apparatus, which correspond to those of the method embodiments shown in fig. 2, and which may be applied in various electronic devices.
As shown in fig. 5, a mirror warehouse deployment apparatus 500 includes: the system comprises a starting unit 501, a deployment uploading unit 502, a deployment unit 503, a writing unit 504 and an execution unit 505. The starting unit 501 is configured to start a mirror warehouse instance in a first target server corresponding to the first target server information as a target mirror warehouse instance; a deployment uploading unit 502 configured to deploy an application distributor using the target mirror image warehouse instance, and upload a target file sent by the application distributor as a mirror image to the target mirror image warehouse instance; a deployment unit 503 configured to deploy at least one middleware by using the deployed application publishing terminal; a writing unit 504, configured to write middleware information of each middleware in the at least one middleware into each mirror repository instance configuration corresponding to at least one second target server, so as to start each mirror repository instance in the at least one second target server according to each mirror repository instance configuration after the middleware information is written, where each second target server in the at least one second target server has corresponding second target server information; and an execution unit 505 configured to execute the deployment of the mirror repository instance cluster according to the mirror repository instances and the target mirror repository instance including the mirror.
In some optional implementations of some embodiments, the starting unit 501 in the mirror warehouse deployment apparatus 500 may be further configured to: starting a target file storage system in the first target server; configuring a configuration file aiming at the mirror image maintenance system in the target file storage system; and starting a mirror image warehouse instance in the first target server according to the configuration file.
In some optional implementations of some embodiments, the apparatus 500 further includes: a determination unit and an analysis unit (not shown in the figure). Wherein the determining unit may be configured to: and determining target domain name resolution information, wherein the target domain name resolution information represents a mapping relation between a domain name corresponding to the target mirror image warehouse instance and an internet protocol address corresponding to the target mirror image warehouse instance. The parsing unit may be configured to: and sending the target domain name resolution information to a target domain name resolution server to register the domain name resolution information.
In some optional implementations of some embodiments, the deployment upload unit 502 in the mirror warehouse deployment apparatus 500 may be further configured to: initializing a container arranging end by utilizing the first target server; and deploying the application issuing end by utilizing the initialized container arranging end and the target mirror image warehouse example.
In some optional implementations of some embodiments, the execution unit 505 in the mirror warehouse deployment apparatus 500 may be further configured to: setting state information of the target mirror image warehouse example and restarting the target mirror image warehouse example after the state information is set; migrating the mirror image in the target mirror image warehouse example after the first restart to each mirror image warehouse example; updating the mirror image warehouse instance configuration corresponding to the target mirror image warehouse instance, and restarting the target mirror image warehouse instance after updating the mirror image warehouse instance configuration; and migrating each mirrored warehouse instance after mirroring according to the mirrored warehouse instance after the second restart, and executing the deployment of the mirrored warehouse instance cluster.
In some optional implementations of some embodiments, the apparatus 500 further includes: a determining unit, a generating unit and an updating unit (not shown in the figure). Wherein the determining unit may be configured to: the internet protocol address of the first target server and the internet protocol address of at least one second target server are determined. The generation unit may be configured to: and converging the internet protocol address of the first target server and the internet protocol address of the at least one second target server to generate a target internet protocol address. The update unit may be configured to: and updating the domain name resolution information in the target domain name resolution server according to the target Internet protocol address.
In some optional implementations of some embodiments, the apparatus 500 further includes: an analysis unit (not shown). Wherein the parsing unit may be configured to: and analyzing the updated domain name analysis information to obtain the cluster information of the mirror image warehouse instance cluster.
It will be understood that the elements described in the apparatus 500 correspond to various steps in the method described with reference to fig. 2. Thus, the operations, features and resulting advantages described above with respect to the method are also applicable to the apparatus 500 and the units included therein, and are not described herein again.
Referring now to FIG. 6, a block diagram of an electronic device (e.g., the electronic device of FIG. 1) 600 suitable for use in implementing some embodiments of the present disclosure is shown. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 6, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 6 may represent one device or may represent multiple devices as desired.
In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In some such embodiments, the computer program may be downloaded and installed from a network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of some embodiments of the present disclosure.
It should be noted that the computer readable medium described above in some embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In some embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: starting a mirror image warehouse instance in a first target server corresponding to the first target server information as a target mirror image warehouse instance; deploying an application publishing terminal by using the target mirror image warehouse example, and uploading a target file sent by the application publishing terminal as a mirror image to the target mirror image warehouse example; deploying at least one middleware by utilizing the deployed application publishing terminal; writing middleware information of each middleware in the at least one middleware into each mirror image warehouse instance configuration corresponding to at least one second target server, so as to start each mirror image warehouse instance in the at least one second target server according to each mirror image warehouse instance configuration written with the middleware information, wherein each second target server in the at least one second target server has corresponding second target server information; and executing the deployment of the mirror image warehouse instance cluster according to the mirror image warehouse instances and the target mirror image warehouse instance comprising the mirror image.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in some embodiments of the present disclosure may be implemented by software, and may also be implemented by hardware. The described units may also be provided in a processor, and may be described as: a processor comprising: the device comprises a starting unit, a deployment uploading unit, a deployment unit, a writing unit and an execution unit. The names of these units do not form a limitation on the units themselves in some cases, for example, the execution unit may also be described as "a unit that starts the mirror repository instance in the first target server corresponding to the first target server information as the target mirror repository instance".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept as defined above. For example, the above features and (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.
Claims (10)
1. A mirror image warehouse deployment method comprises the following steps:
starting a mirror image warehouse instance in a first target server corresponding to the first target server information as a target mirror image warehouse instance;
deploying an application publishing terminal by using the target mirror image warehouse instance, and uploading a target file sent by the application publishing terminal to the target mirror image warehouse instance as a mirror image;
deploying at least one middleware by utilizing the deployed application publishing terminal;
writing middleware information of each middleware in the at least one middleware into each mirror image warehouse instance configuration corresponding to at least one second target server, so as to start each mirror image warehouse instance in the at least one second target server according to each mirror image warehouse instance configuration after the middleware information is written, wherein each second target server in the at least one second target server has corresponding second target server information;
and executing the deployment of the mirror image warehouse instance cluster according to the mirror image warehouse instances and the target mirror image warehouse instance comprising the mirror image.
2. The method of claim 1, wherein the starting the mirror repository instance in the first target server corresponding to the first target server information comprises:
starting a target file storage system in the first target server;
configuring a configuration file for a mirror image maintenance system in the target file storage system;
and starting a mirror image warehouse instance in the first target server according to the configuration file.
3. The method of claim 1, wherein after the launching of the mirror repository instance in the first target server to which the first target server information corresponds, the method further comprises:
determining target domain name resolution information, wherein the target domain name resolution information represents a mapping relation between a domain name corresponding to the target mirror image warehouse instance and an internet protocol address corresponding to the target mirror image warehouse instance;
and sending the target domain name resolution information to a target domain name resolution server so as to register the domain name resolution information.
4. The method of claim 1, wherein said deploying an application publisher with the target mirror repository instance comprises:
initializing a container arranging end by utilizing the first target server;
and deploying the application issuing end by utilizing the initialized container arranging end and the target mirror image warehouse instance.
5. The method of claim 1, wherein said performing deployment of a mirror repository instance cluster from the respective mirror repository instance and a target mirror repository instance comprising the mirror comprises:
setting state information of the target mirror image warehouse example and restarting the target mirror image warehouse example after the state information is set;
migrating the mirror image in the target mirror image warehouse example after the first restart to each mirror image warehouse example;
updating the mirror image warehouse instance configuration corresponding to the target mirror image warehouse instance, and restarting the target mirror image warehouse instance after updating the mirror image warehouse instance configuration;
and migrating each mirrored warehouse instance after mirroring according to the mirrored warehouse instance after the second restart, and executing the deployment of the mirrored warehouse instance cluster.
6. The method of claim 3, wherein after the performing deployment of a mirror repository instance cluster from the respective mirror repository instance and a target mirror repository instance comprising the mirror, the method further comprises:
determining an internet protocol address of the first target server and an internet protocol address of at least one second target server;
aggregating the internet protocol address of the first target server and the internet protocol address of the at least one second target server to generate a target internet protocol address;
and updating the domain name resolution information in the target domain name resolution server according to the target Internet protocol address.
7. The method of claim 6, wherein the method further comprises:
and analyzing the updated domain name analysis information to obtain the cluster information of the mirror image warehouse instance cluster.
8. A mirror warehouse deployment apparatus, comprising:
the starting unit is configured to start the mirror image warehouse instance in a first target server corresponding to the first target server information to serve as a target mirror image warehouse instance;
the deployment uploading unit is configured to deploy an application publishing terminal by using the target mirror image warehouse instance, and upload a target file sent by the application publishing terminal to the target mirror image warehouse instance as a mirror image;
a deployment unit configured to deploy at least one middleware using the deployed application publishing terminal;
a writing unit, configured to write middleware information of each middleware in the at least one middleware into each mirror repository instance configuration corresponding to at least one second target server, so as to start each mirror repository instance in the at least one second target server according to each mirror repository instance configuration after the middleware information is written, where each second target server in the at least one second target server has corresponding second target server information;
an execution unit configured to execute deployment of a mirror repository instance cluster according to the respective mirror repository instance and a target mirror repository instance comprising the mirror.
9. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111479396.9A CN114157658B (en) | 2021-12-06 | 2021-12-06 | Mirror warehouse deployment method, apparatus, electronic device and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111479396.9A CN114157658B (en) | 2021-12-06 | 2021-12-06 | Mirror warehouse deployment method, apparatus, electronic device and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114157658A true CN114157658A (en) | 2022-03-08 |
| CN114157658B CN114157658B (en) | 2024-03-01 |
Family
ID=80452891
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111479396.9A Active CN114157658B (en) | 2021-12-06 | 2021-12-06 | Mirror warehouse deployment method, apparatus, electronic device and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114157658B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117519912A (en) * | 2024-01-04 | 2024-02-06 | 之江实验室 | Mirror image warehouse deployment method, device, storage medium and equipment |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120066394A1 (en) * | 2010-09-15 | 2012-03-15 | Oracle International Corporation | System and method for supporting lazy deserialization of session information in a server cluster |
| CN106406933A (en) * | 2016-08-30 | 2017-02-15 | 广西电网有限责任公司 | One-key automatic deployment method for Tomcat cluster |
| CN109271198A (en) * | 2018-08-16 | 2019-01-25 | 中国平安人寿保险股份有限公司 | Mirror image packaging method, device and electronic equipment based on Docker container |
| CN109981351A (en) * | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| US20200073649A1 (en) * | 2018-08-30 | 2020-03-05 | International Business Machines Corporation | Generating target configuration containers providing computer environments based on a configuration container |
| CN111142879A (en) * | 2019-12-05 | 2020-05-12 | 深圳融卡智能科技有限公司 | Software integration release method and automatic operation and maintenance platform |
| CN112995267A (en) * | 2019-12-16 | 2021-06-18 | 中科星图股份有限公司 | Data subscription service method and equipment based on Kubernetes cluster |
| CN113238763A (en) * | 2021-05-17 | 2021-08-10 | 京东数字科技控股股份有限公司 | Application deployment method, device, storage medium and program product |
| CN113434254A (en) * | 2021-06-30 | 2021-09-24 | 深圳平安智汇企业信息管理有限公司 | Client deployment method, client deployment apparatus, computer device, and storage medium |
| WO2021217871A1 (en) * | 2020-04-28 | 2021-11-04 | 平安科技（深圳）有限公司 | Method and apparatus for deploying micro service cluster, computer device and storage medium |
| CN113656147A (en) * | 2021-08-20 | 2021-11-16 | 北京百度网讯科技有限公司 | Cluster deployment method, device, equipment and storage medium |
-
2021
- 2021-12-06 CN CN202111479396.9A patent/CN114157658B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120066394A1 (en) * | 2010-09-15 | 2012-03-15 | Oracle International Corporation | System and method for supporting lazy deserialization of session information in a server cluster |
| US20120066400A1 (en) * | 2010-09-15 | 2012-03-15 | Oracle International Corporation | System and method for parallel muxing between servers in a cluster |
| CN106406933A (en) * | 2016-08-30 | 2017-02-15 | 广西电网有限责任公司 | One-key automatic deployment method for Tomcat cluster |
| CN109271198A (en) * | 2018-08-16 | 2019-01-25 | 中国平安人寿保险股份有限公司 | Mirror image packaging method, device and electronic equipment based on Docker container |
| US20200073649A1 (en) * | 2018-08-30 | 2020-03-05 | International Business Machines Corporation | Generating target configuration containers providing computer environments based on a configuration container |
| CN109981351A (en) * | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| CN111142879A (en) * | 2019-12-05 | 2020-05-12 | 深圳融卡智能科技有限公司 | Software integration release method and automatic operation and maintenance platform |
| CN112995267A (en) * | 2019-12-16 | 2021-06-18 | 中科星图股份有限公司 | Data subscription service method and equipment based on Kubernetes cluster |
| WO2021217871A1 (en) * | 2020-04-28 | 2021-11-04 | 平安科技（深圳）有限公司 | Method and apparatus for deploying micro service cluster, computer device and storage medium |
| CN113238763A (en) * | 2021-05-17 | 2021-08-10 | 京东数字科技控股股份有限公司 | Application deployment method, device, storage medium and program product |
| CN113434254A (en) * | 2021-06-30 | 2021-09-24 | 深圳平安智汇企业信息管理有限公司 | Client deployment method, client deployment apparatus, computer device, and storage medium |
| CN113656147A (en) * | 2021-08-20 | 2021-11-16 | 北京百度网讯科技有限公司 | Cluster deployment method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 王晶;施亮;: "基于开源平台的网络镜像部署方案", 微型电脑应用, no. 04 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117519912A (en) * | 2024-01-04 | 2024-02-06 | 之江实验室 | Mirror image warehouse deployment method, device, storage medium and equipment |
| CN117519912B (en) * | 2024-01-04 | 2024-04-05 | 之江实验室 | Mirror image warehouse deployment method, device, storage medium and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114157658B (en) | 2024-03-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11170065B2 (en) | Technology agnostic UI microservices | |
| US10341181B2 (en) | Method and apparatus to allow dynamic changes of a replica network configuration in distributed systems | |
| CN111885114B (en) | Method, device and storage medium for upgrading application program interface module in gateway | |
| US12026494B2 (en) | Dynamic automation of prerequisite component deployment in disconnected environments | |
| CN113821352A (en) | Remote service calling method and device | |
| CN113900721A (en) | Operating system starting method and device and electronic equipment | |
| CN114035879A (en) | Page theme color changing method and device, electronic equipment and computer readable medium | |
| CN112748962A (en) | Application loading method and device, electronic equipment and computer readable medium | |
| CN114911518A (en) | Cloud function application release management method, system, equipment and storage medium | |
| CN114157658B (en) | Mirror warehouse deployment method, apparatus, electronic device and computer readable medium | |
| CN115167874B (en) | Automatic driving software mirror image deployment method and device, electronic equipment and readable medium | |
| CN108804442B (en) | Serial number generation method and device | |
| CN114398035A (en) | Method, apparatus, device and computer readable medium for providing service using component | |
| CN111414200B (en) | Method, apparatus, electronic device and computer readable medium for installing operating system | |
| CN112328184A (en) | Cluster capacity expansion method, device, equipment and storage medium | |
| CN112099841A (en) | Method and system for generating configuration file | |
| US12032991B2 (en) | Continuous liveness and integrity of applications during migration | |
| WO2023279869A1 (en) | Continuous liveness and integrity of applications during migration | |
| CN112883697B (en) | Workflow form generation method, device, electronic equipment and computer readable medium | |
| US11323512B2 (en) | Peer to peer infrastructure management architecture | |
| CN117112500B (en) | Resource management method, device, equipment and storage medium | |
| CN118043778A (en) | Resource reuse for pipeline workload | |
| CN113805858A (en) | Method and device for continuously deploying software developed by scripting language | |
| CN114697206A (en) | Internet of things node management method, device, equipment and computer readable medium | |
| CN113760351A (en) | Project uploading method and device, electronic equipment and computer readable 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 |