CN111782242A - Client dynamic release method and device in cloud environment - Google Patents
Client dynamic release method and device in cloud environment Download PDFInfo
- Publication number
- CN111782242A CN111782242A CN202010602752.0A CN202010602752A CN111782242A CN 111782242 A CN111782242 A CN 111782242A CN 202010602752 A CN202010602752 A CN 202010602752A CN 111782242 A CN111782242 A CN 111782242A
- Authority
- CN
- China
- Prior art keywords
- client
- latest
- updating
- dynamic
- host
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
The invention provides a method and a device for dynamically releasing a client under a cloud environment, wherein the method for dynamically releasing the client under the cloud environment comprises the following steps: sending the latest client to each host machine; sending a client updating instruction to each host machine; and updating the client of each host machine according to the client updating instruction. The client dynamic release method and device under the cloud environment can uniformly manage the client version through the management node and the client warehouse, and can be dynamically released to the host machine under the cloud environment according to the requirement, so that a user can be helped to reduce version operation caused by updating the client version.
Description
Technical Field
The invention relates to the technical field of computer data processing, in particular to the technical field of distributed monitoring and containers, and specifically relates to a client dynamic publishing method and device in a cloud environment.
Background
With the popularization of the internet and the rapid increase of internet users, the traditional single application system cannot meet the requirements of increasing user pressure on system capacity and high availability. By modifying the application of the single body into a distributed service mode, the continuously increased system pressure can be effectively solved, which is verified in the commodity promotion of a plurality of internet companies. In the field of distributed technology, in the application starting process, the key link of RPC or HTTP service is embedded, and in the calling process, the embedded point tracking and monitoring are a general implementation scheme in the field of distributed monitoring.
In the prior art, a distributed monitoring client is generally actively introduced by using an application, a special starting configuration is added to the monitoring client in a project, and the link point burying operation can be completed in the starting process after the configuration is completed. With the increasingly widespread use of the monitoring client and the continuous iterative upgrade of the client, the following three problems occur, namely that when the version of the client is upgraded, the version which is required to be displayed and is introduced is replaced and packaged and deployed again, and with the increasingly widespread use, the version upgrade is difficult to implement and the cost is very high. Secondly, because the monitoring client side calls the link through the whole distributed system, along with the version upgrading of the monitoring client side, the compatibility difficulty between the monitoring client sides of different versions is multiplied, and the management capability of good versions is lacked; and thirdly, part of application services run stably, and the version of the monitoring client is not dynamically upgraded, so that the latest monitoring capability cannot fall to the ground and cannot play a role.
Disclosure of Invention
Aiming at the problems in the prior art, the client dynamic release method and the client dynamic release device under the cloud environment can uniformly manage the client version by the management node and the client warehouse, and can be dynamically released to the host machine under the cloud environment according to the requirement, so that a user is helped to reduce the version operation caused by updating the client version.
In order to solve the technical problems, the invention provides the following technical scheme:
in a first aspect, the present invention provides a method for dynamically publishing a client in a cloud environment, including:
sending the latest client to each host machine;
sending a client updating instruction to each host machine;
and updating the client of each host machine according to the client updating instruction.
In an embodiment, the method for dynamically publishing the client in the cloud environment further includes:
and responding to the client updating instruction, and each host machine checks the latest client and sets a label for the latest client.
In an embodiment, the updating the client of each host according to the client update instruction includes:
and when the container of each host machine is started, acquiring the latest client according to the label so as to finish client updating.
In an embodiment, the sending the latest clients to the hosts includes:
and sending the latest client to a data warehouse, and uniformly sending the latest client to each host machine through the data warehouse.
In one embodiment, the check is an md5 check.
In a second aspect, the present invention provides a dynamic client publishing device in a cloud environment, including:
the client sending unit is used for sending the latest client to each host;
the updating instruction sending unit is used for sending a client updating instruction to each host machine;
and the client updating unit is used for updating the clients of the host machines according to the client updating instruction.
In an embodiment, the dynamic client publishing device in the cloud environment further includes:
and the label setting unit is used for responding to the client updating instruction, and each host machine checks the latest client and sets a label for the latest client.
In an embodiment, the client updating unit is specifically configured to, when the container of each host is started, obtain the latest client according to the tag, so as to complete client updating;
the client sending unit is specifically configured to send the latest client to a data warehouse, and send the latest client to each host in a unified manner through the data warehouse;
the check is an md5 check.
In a third aspect, the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the client dynamic publishing method in a cloud environment when executing the program.
In a fourth aspect, the present invention provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a client dynamic publishing method in a cloud environment.
As can be seen from the above description, according to the method and the device for dynamically publishing the client in the cloud environment provided by the embodiment of the present invention, the latest client is sent to each host; then, sending a client updating instruction to each host machine; and finally, updating the client of each host according to the client updating instruction. The invention solves the problems of difficulty and compatibility in upgrading the distributed monitoring client side component. The invention supports the decoupling between the upgrading of the monitoring client and the application upgrading, and the client management system can dynamically release the latest client, automatically select the upgrading strategy of the client and manage the version of the client. Specifically, the invention has the following beneficial effects:
1. the release process of the public client version is completely transparent to the application, and the application does not need to manually change the client version for upgrading.
2. And monitoring the running condition of the client version in the production environment in real time, and performing dynamic gray scale upgrading.
3. The number of running versions in production is reduced, the over-old versions are discarded in time, and the difficulty of compatibility of different versions is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a first schematic flow chart of a client dynamic publishing method in a cloud environment according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a client dynamic publishing method in a cloud environment according to an embodiment of the present invention;
FIG. 3 is a flow chart illustrating step 300 according to an embodiment of the present invention;
FIG. 4 is a flow chart illustrating step 100 according to an embodiment of the present invention;
fig. 5 is a schematic flow chart of a client dynamic publishing method in a cloud environment in a specific application example of the present invention;
fig. 6 is an architecture diagram of a dynamic publishing system of a monitoring client in a cloud environment in an embodiment of the present invention;
FIG. 7 is a diagram illustrating an architecture of a client management device in an embodiment of the present invention;
FIG. 8 is a diagram of a dynamic publishing device architecture in an embodiment of the present invention;
FIG. 9 is a diagram of an architecture of a dynamic loading device in an embodiment of the present invention;
fig. 10 is a first block diagram illustrating a configuration of a dynamic client publishing device in a cloud environment according to an embodiment of the present invention;
fig. 11 is a structural block diagram of a client dynamic publishing device in a cloud environment in an embodiment of the present invention;
fig. 12 is a schematic structural diagram of an electronic device in an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
It should be noted that the terms "comprises" and "comprising," and any variations thereof, in the description and claims of this application and the above-described drawings, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
The embodiment of the invention provides a specific implementation manner of a client dynamic publishing method in a cloud environment, and referring to fig. 1, the method specifically includes the following steps:
step 100: and sending the latest client to each host machine.
It is understood that the host in step 100 refers to a host system with two network adapters, and the routing function in the host system is disabled, while the service and access to the external network are provided by the proxy server on the gateway. The firewall system is a firewall system with a very simple structure and high safety, and is an improvement on a dual-host firewall. The structure is constructed around a dual-homed host having at least two network interfaces. The network inside and outside the double-host computer can communicate with the double-host computer, but the internal and external networks can not communicate directly, and the IP data flow between the internal and external networks is completely cut off by the double-host computer. The dual-homed host may provide a high degree of network control by proxy or having users directly registered to it.
Structurally, the host is used to replace router to execute safety control function, so it is similar to packet filtering firewall. A dual-host, i.e. a host with multiple network interfaces, can be used to route between an internal network and an external network. If the routing function is disabled in a dual-homed host, the host can isolate the communication between its connected internal and external networks, and both the internal and external networks connected to it can execute the network applications provided by it, if allowed, they can share data. Therefore, the information can be transmitted between some nodes of the internal network and the external network through the shared data on the double hosts, but the information cannot be transmitted between the internal network and the external network, and the effect of protecting the internal network is achieved. The method is the only channel for the external network user to enter the internal network, so that the safety of the dual-host is very important, and the user password control safety of the dual-host is a key.
Step 200: and sending a client updating instruction to each host machine.
Specifically, a client update instruction is searched to each host machine according to the distributed monitoring and issuing method of each host machine.
Step 300: and updating the client of each host machine according to the client updating instruction.
When the step 300 is implemented, the method specifically comprises the following steps: and when the container in a single host machine is started, acquiring the latest version client from the host machine according to the client label, and completing the loading operation of the latest client.
As can be seen from the above description, in the dynamic client publishing method in the cloud environment provided by the embodiment of the present invention, the latest client is first sent to each host; then, sending a client updating instruction to each host machine; and finally, updating the client of each host according to the client updating instruction. The invention solves the problems of difficulty and compatibility in upgrading the distributed monitoring client side component. The invention supports the decoupling between the upgrading of the monitoring client and the application upgrading, and the client management system can dynamically release the latest client, automatically select the upgrading strategy of the client and manage the version of the client. Specifically, the invention has the following beneficial effects:
1. the release process of the public client version is completely transparent to the application, and the application does not need to manually change the client version for upgrading.
2. And monitoring the running condition of the client version in the production environment in real time, and performing dynamic gray scale upgrading.
3. The number of running versions in production is reduced, the over-old versions are discarded in time, and the difficulty of compatibility of different versions is reduced.
In an embodiment, referring to fig. 2, the client dynamic publishing method in the cloud environment further includes:
step 400: and responding to the client updating instruction, and each host machine checks the latest client and sets a label for the latest client.
It is understood that step 400 is implemented at the host side.
In one embodiment, referring to fig. 3, step 300 further comprises:
step 301: and when the container of each host machine is started, acquiring the latest client according to the label so as to finish client updating.
It will be appreciated that the container in step 301 is an operating system virtualization technique for packaging applications and their dependencies and running them in an isolated environment. In a different type of infrastructure, the container provides a way to lightweight package and deploy applications in a standard manner. The container can run consistently on any host that supports the container, so developers can directly test the same software locally, and can easily deploy it later into a complete production environment. Meanwhile, the Container Format can ensure that the dependent items of the application program are put into the mirror image, and the manual operation part and the release flow are simplified. Because the host and platform running the container are common, the infrastructure for managing the container-based system can be standardized. In addition, the container is created from a container image, which contains the system, application, and container environment. As with creating a particular container template, the same image may be used to generate any number of running containers. This works similarly to classes and instances in object-oriented programming: a single class may be used to create any number of instances and a single container mirror may be used to create any number of containers. This type of metaphor is also applicable to the inheritance aspect, as the container image can serve as a parent to other custom container images. The user can download the pre-constructed container from the external resource, and can also construct the self-defined mirror image according to the requirement.
In one embodiment, referring to fig. 4, step 100 further comprises:
step 101: and sending the latest client to a data warehouse, and uniformly sending the latest client to each host machine through the data warehouse.
Specifically, the distributed monitoring and issuing party issues the latest client version to the client management unified warehouse through the client management device, and then the warehouse sends the latest client to each host.
In one embodiment, the check is an md5 check.
Essentially, the md5 check is a one-way operation that translates a data string of arbitrary length into a short fixed-length value. Any two strings should not have the same hash value (i.e., there is a "high probability" that it is not the same, and it should be difficult to artificially create a string where two hash values are the same).
MD5 checks the correctness of data by performing a hash operation on the received transmission data. The calculated hash value is compared with the hash value transmitted with the data. If the two values are the same, it indicates that the transmitted data is intact and has not been tampered (provided that the hash value has not been tampered), and thus can be used with confidence.
According to the client dynamic release method in the cloud environment provided by the embodiment of the invention, the client version is managed through the unified management node and the client warehouse, and is dynamically released to the host machine in the cloud environment according to the requirement, and the client of the latest version on the host machine is dynamically loaded through the unified loading unit. The method helps the user to reduce version operations caused by upgrading the client version.
To further illustrate the present solution, the present invention provides a specific application example of the client dynamic publishing method in the cloud environment, which specifically includes the following contents, and refer to fig. 5.
In this specific application example, a dynamic publishing system of a monitoring client in a cloud environment is provided, referring to fig. 6, the system includes: client management device 1, client warehouse 2, dynamic release device 3, dynamic loading device 4, wherein:
the client management device 1: the method is used for managing the life cycle of the client, and comprises uploading of a client version medium, release management of the client version, operation management and statistics of the client.
The client side warehouse 2: for uniformly storing the client version media.
The dynamic distribution device 3: and pushing a target client medium from the unified warehouse to a corresponding directory of a target host according to a version upgrading instruction provided by the client management device 1, and simultaneously checking and updating configuration.
The dynamic loading device 4: and in the starting process of the application server, the target application acquires the client side with the corresponding version according to the version label and realizes the loading of the client side through the public script.
Fig. 7 is a schematic diagram of an internal structure of the client management apparatus 1, where the client management apparatus 1 includes a client medium uploading unit 11, a version release management unit 12, and a client version statistics unit 13. Wherein: the client medium uploading unit 11 is responsible for releasing the latest client version to the client repository 2; the version release management unit 12 is responsible for docking the dynamic release device 3 and performing dynamic release triggering; the client version counting unit 13 is responsible for counting the client version and the historical stock version in the current operation stage, and is connected with the client media uploading unit 11 and the version release management unit 12.
Fig. 8 is a schematic diagram of an internal structure of the dynamic distribution apparatus 3, and as shown in fig. 8, the dynamic distribution apparatus 3 includes a version obtaining unit 31, a version uploading unit 32, a version checking unit 33, and a version distribution unit 34. Wherein: the version acquiring unit 31 is responsible for acquiring a required client version medium from the client warehouse 2; the version uploading unit 32 is responsible for uploading the acquired client version media to a target path of a target host; the version checking unit 33 is responsible for checking whether the client version is complete; the version release unit 34 is responsible for updating the client version label, and the target client can be acquired by the application after the update.
Fig. 9 is a diagram illustrating an internal configuration of the dynamic loading apparatus 4, where the dynamic loading apparatus 4 includes a client checking unit 41, a client pulling unit 42, and a client loading unit 43, where: the client checking unit 41 is responsible for checking the client version and validity of the corresponding tag at startup; the client pulling unit 42 is responsible for checking that the passed client medium is pulled into the target container; the client loading unit 43 loads the pulled latest client script through the common loading script, and ensures dynamic release of the latest client.
Fig. 5 shows a method for dynamically publishing a client in a cloud environment provided by a specific application example.
S1: and the distributed monitoring publisher publishes the latest client version to the client management unified warehouse through the client management device.
S2: the client management device manages the running states of all the host machine clients, is connected with the dynamic release device according to requirements, and sends client instructions to the target host machine.
S3: and the dynamic issuing device pushes the target client-side medium from the unified warehouse to the corresponding host according to the instruction in the step S2, and sends the dynamic issuing instruction.
S4: according to the step S3, the host machine receives the release instruction, carries out md5 verification on the local version medium, and modifies the client start label into the target client version after the verification is passed.
S5: and when the container in the host machine is started, acquiring the latest version client from the host machine according to the client label, and completing the loading operation of the latest client.
As can be seen from the above description, in the dynamic client publishing method and system in the cloud environment provided by the embodiments of the present invention, the latest client is first sent to each host; then, sending a client updating instruction to each host machine; and finally, updating the client of each host according to the client updating instruction. The invention solves the problems of difficulty and compatibility in upgrading the distributed monitoring client side component. The invention supports the decoupling between the upgrading of the monitoring client and the application upgrading, and the client management system can dynamically release the latest client, automatically select the upgrading strategy of the client and manage the version of the client. Specifically, the invention has the following beneficial effects:
1. the release process of the public client version is completely transparent to the application, and the application does not need to manually change the client version for upgrading.
2. And monitoring the running condition of the client version in the production environment in real time, and performing dynamic gray scale upgrading.
3. The number of running versions in production is reduced, the over-old versions are discarded in time, and the difficulty of compatibility of different versions is reduced.
Based on the same inventive concept, the embodiment of the present application further provides a client dynamic publishing device in a cloud environment, which can be used to implement the method described in the foregoing embodiment, such as the following embodiments. The principle of solving the problems of the client dynamic release device in the cloud environment is similar to that of the client dynamic release method in the cloud environment, so that the implementation of the client dynamic release device in the cloud environment can be realized by the client dynamic release method in the cloud environment, and repeated parts are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. While the system described in the embodiments below is preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
An embodiment of the present invention provides a specific implementation manner of a dynamic client publishing device in a cloud environment, which is capable of implementing a dynamic client publishing method in a cloud environment, and referring to fig. 10, the dynamic client publishing device in the cloud environment specifically includes the following contents:
a client sending unit 10, configured to send the latest client to each host;
an update instruction sending unit 20, configured to send a client update instruction to each host;
and the client updating unit 30 is configured to update the clients of the hosts according to the client updating instruction.
In an embodiment, referring to fig. 11, the client dynamic publishing device in the cloud environment further includes:
and the label setting unit 40 is configured to, in response to the client update instruction, verify the latest client by each host and set a label for the latest client.
In an embodiment, the client updating unit is specifically configured to, when the container of each host is started, obtain the latest client according to the tag, so as to complete client updating;
the client sending unit is specifically configured to send the latest client to a data warehouse, and send the latest client to each host in a unified manner through the data warehouse;
the check is an md5 check.
As can be seen from the above description, the dynamic client publishing device in the cloud environment according to the embodiment of the present invention first sends the latest client to each host; then, sending a client updating instruction to each host machine; and finally, updating the client of each host according to the client updating instruction. The invention solves the problems of difficulty and compatibility in upgrading the distributed monitoring client side component. The invention supports the decoupling between the upgrading of the monitoring client and the application upgrading, and the client management system can dynamically release the latest client, automatically select the upgrading strategy of the client and manage the version of the client. Specifically, the invention has the following beneficial effects:
1. the release process of the public client version is completely transparent to the application, and the application does not need to manually change the client version for upgrading.
2. And monitoring the running condition of the client version in the production environment in real time, and performing dynamic gray scale upgrading.
3. The number of running versions in production is reduced, the over-old versions are discarded in time, and the difficulty of compatibility of different versions is reduced.
The apparatuses, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is an electronic device, which may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
In a typical example, the electronic device specifically includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the processor implements the steps of the client dynamic publishing method in the cloud environment, where the steps include:
step 100: and sending the latest client to each host machine.
Step 200: and sending a client updating instruction to each host machine.
Step 300: and updating the client of each host machine according to the client updating instruction.
Referring now to FIG. 12, shown is a schematic diagram of an electronic device 600 suitable for use in implementing embodiments of the present application.
As shown in fig. 12, the electronic apparatus 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate works and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM)) 603. In the RAM603, various programs and data necessary for the operation of the system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted as necessary on the storage section 608.
In particular, according to an embodiment of the present invention, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, an embodiment of the present invention includes a computer-readable storage medium, on which a computer program is stored, the computer program, when being executed by a processor, implementing the steps of the client dynamic publishing method in the cloud environment, the steps including:
step 100: and sending the latest client to each host machine.
Step 200: and sending a client updating instruction to each host machine.
Step 300: and updating the client of each host machine according to the client updating instruction.
In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A client dynamic release method in a cloud environment is characterized by comprising the following steps:
sending the latest client to each host machine;
sending a client updating instruction to each host machine;
and updating the client of each host machine according to the client updating instruction.
2. The client dynamic publishing method according to claim 1, further comprising:
and responding to the client updating instruction, and each host machine checks the latest client and sets a label for the latest client.
3. The dynamic client publishing method according to claim 2, wherein the updating the clients of the hosts according to the client updating instruction includes:
and when the container of each host machine is started, acquiring the latest client according to the label so as to finish client updating.
4. The dynamic client publishing method according to claim 1, wherein the sending the latest client to each host comprises:
and sending the latest client to a data warehouse, and uniformly sending the latest client to each host machine through the data warehouse.
5. The client dynamic publishing method according to claim 2, wherein the check is an md5 check.
6. A dynamic client publishing device in a cloud environment is characterized by comprising:
the client sending unit is used for sending the latest client to each host;
the updating instruction sending unit is used for sending a client updating instruction to each host machine;
and the client updating unit is used for updating the clients of the host machines according to the client updating instruction.
7. The client dynamic publishing device according to claim 6, further comprising:
and the label setting unit is used for responding to the client updating instruction, and each host machine checks the latest client and sets a label for the latest client.
8. The client dynamic publishing device according to claim 7, wherein the client updating unit is specifically configured to, when the container of each host is started, obtain the latest client according to the tag to complete client updating;
the client sending unit is specifically configured to send the latest client to a data warehouse, and send the latest client to each host in a unified manner through the data warehouse;
the check is an md5 check.
9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the client dynamic publishing method in the cloud environment according to any one of claims 1 to 5 when executing the program.
10. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the client dynamic publishing method in the cloud environment according to any one of claims 1 to 5 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010602752.0A CN111782242A (en) | 2020-06-29 | 2020-06-29 | Client dynamic release method and device in cloud environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010602752.0A CN111782242A (en) | 2020-06-29 | 2020-06-29 | Client dynamic release method and device in cloud environment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111782242A true CN111782242A (en) | 2020-10-16 |
Family
ID=72761339
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010602752.0A Pending CN111782242A (en) | 2020-06-29 | 2020-06-29 | Client dynamic release method and device in cloud environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111782242A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140173560A1 (en) * | 2012-12-13 | 2014-06-19 | International Business Machines Corporation | Dynamically updating code without requiring processes to restart |
| CN109495532A (en) * | 2017-09-13 | 2019-03-19 | 北京京东尚科信息技术有限公司 | Client update method and device |
| CN109656599A (en) * | 2018-12-28 | 2019-04-19 | 苏州思必驰信息科技有限公司 | The method and system updated for client release |
-
2020
- 2020-06-29 CN CN202010602752.0A patent/CN111782242A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140173560A1 (en) * | 2012-12-13 | 2014-06-19 | International Business Machines Corporation | Dynamically updating code without requiring processes to restart |
| CN109495532A (en) * | 2017-09-13 | 2019-03-19 | 北京京东尚科信息技术有限公司 | Client update method and device |
| CN109656599A (en) * | 2018-12-28 | 2019-04-19 | 苏州思必驰信息科技有限公司 | The method and system updated for client release |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109547570B (en) | Service registration method, device, registration center management equipment and storage medium | |
| CN108279932B (en) | Method and device for dynamically configuring user interface of mobile terminal | |
| EP3364631B1 (en) | Dynamic orchestration of microservices | |
| CN109814881A (en) | Method and apparatus for disposing data-base cluster | |
| US20200159591A1 (en) | Application program interface based service lookup in a service architecture | |
| CN111090423B (en) | Webhook framework system and method for realizing active calling and event triggering | |
| CN113760324A (en) | Method and device for constructing micro front-end application | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN115248692A (en) | Device and method for supporting cloud deployment of multiple deep learning framework models | |
| CN117112122A (en) | Cluster deployment method and device | |
| CN110807162A (en) | Method and device for loading occupation bitmap | |
| CN113535220B (en) | Code packet management method and device | |
| CN113077260A (en) | Data access method and device based on block chain and electronic equipment | |
| CN116208498A (en) | Method, device, equipment and medium for node differential configuration of OpenStack cloud platform | |
| WO2022199324A1 (en) | Run-time communications protocol parameter adjustment in containerized applications | |
| CN111782242A (en) | Client dynamic release method and device in cloud environment | |
| CN113612643B (en) | Network configuration method, device and equipment of cloud mobile phone and storage medium | |
| CN117337429A (en) | Deploying a machine learning model | |
| CN112099841A (en) | Method and system for generating configuration file | |
| CN113765983A (en) | Site service deployment method and device | |
| CN112083945A (en) | NPM installation package update prompting method and device, electronic equipment and storage medium | |
| CN113805858B (en) | Method and device for continuously deploying software developed by scripting language | |
| CN115904361B (en) | Data processing method, device, equipment and medium applied to micro-service | |
| CN117112500B (en) | Resource management method, device, equipment and storage medium | |
| CN113805958B (en) | Third party service access method and system based on OSB API specification |
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 |