A cloud physical machine monitoring service deployment method, system, storage medium and device

Abstract

The application provides a cloud physical machine monitoring service deployment method, system, storage medium and equipment, and the method comprises the following steps: storing a Telegraf execution file to a cloud platform, and adding a cloud physical monitoring service switch to a server of a to-be-deployed monitoring service of the cloud platform; in response to the cloud physical monitoring service switch of the server being in an open state, deploying a first Telegraf service for the server based on the Telegraf execution file, and deploying an Ironic service for the server; starting the first Telegraf service and a specified listening port thereof; starting the Ironic service, and downloading the Telegraf execution file to a to-be-monitored cloud physical machine through the Ironic service, so that the cloud physical machine starts a second Telegraf service based on the Telegraf execution file, and transmits monitoring information to the listening port through a data output port of the second Telegraf service, thereby realizing monitoring of the cloud physical machine by the cloud platform. The application provides a complete cloud physical machine monitoring scheme, which can guarantee real-time monitoring of the state of the cloud physical machine by the cloud platform, and further guarantee stable operation of the cloud platform.

Description

Technical Field

[0001] This invention relates to the field of cloud platform technology, and in particular to a method, system, storage medium, and device for deploying cloud physical machine monitoring services. Background Technology

[0002] Kubernetes (k8s) is an open-source container cluster management system and a leading solution for distributed architecture based on container technology. Building upon Docker (container) technology, it provides a complete set of functions for containerized applications, including deployment, operation, resource scheduling, service discovery, and dynamic scaling, significantly improving the ease of managing large-scale container clusters.

[0003] OpenStack is an open-source cloud computing management platform project, composed of several main components that work together to perform specific tasks. OpenStack supports almost all types of cloud environments, and its goal is to provide a simple-to-implement, scalable, feature-rich, and standardized cloud computing management platform. After years of development, OpenStack's technology has become increasingly mature and stable, offering high availability while also providing flexible scalability. Therefore, OpenStack has been widely adopted across various industries.

[0004] The current issues with monitoring cloud physical machines on the OpenStack cloud platform include: the lack of monitoring services for cloud physical machines created through bare metal services on the current OpenStack cloud platform, which makes it impossible to monitor the resource usage and health status of cloud physical machines. Summary of the Invention

[0005] In view of this, the purpose of this invention is to propose a cloud physical machine monitoring service deployment method, system, storage medium and device to solve the problem that cloud physical machines created by the current cloud platform through bare metal services do not have relevant monitoring services, resulting in the inability to monitor the resource usage and health status of cloud physical machines.

[0006] To achieve the above objectives, the present invention provides a method for deploying a cloud physical machine monitoring service, comprising the following steps:

[0007] Store the Telegraf executable file on the cloud platform and set up the cloud physical monitoring service switch on the server where the monitoring service to be deployed is to be deployed on the cloud platform.

[0008] In response to the server's cloud physical monitoring service being enabled, the first Telegraf service is deployed on the server based on the Telegraf executable file, and the Ironic service is also deployed on the server.

[0009] Start the first Telegraf service and its specified listening port;

[0010] Start the Ironic service and distribute the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service. This enables the cloud physical machine to start a second Telegraf service based on the Telegraf executable file. The monitoring information is then transmitted to the listening port through the data output port of the second Telegraf service, so that the cloud platform can monitor the cloud physical machine.

[0011] In some embodiments, starting the first Telegraf service and its specified listening port includes:

[0012] During the startup process of the first Telegraf service, the listening port of the first Telegraf service is specified through Configmap, the first configuration file containing the listening port parameter is mounted to the container, and the first Telegraf service is started to enable the listening function of the listening port.

[0013] In some embodiments, starting the Ironic service and distributing the Telegraf executable file to the cloud physical machine to be monitored via the Ironic service, so that the cloud physical machine starts a second Telegraf service based on the Telegraf executable file, includes:

[0014] During the Ironic service startup process, the Telegraf executable file is mounted to Conductor, the data output port is specified through Configmap, and the second configuration file containing the data output port parameters and server address is mounted to Conductor. The Ironic service is started, and the Telegraf executable file and the second configuration file are distributed to cloud physical machines. The second Telegraf service is started on the cloud physical machines.

[0015] In some embodiments, storing the Telegraf executable file on a cloud platform includes:

[0016] Build a container image with the Telegraf executable installed, and push the container image to the cloud platform.

[0017] In some embodiments, setting a cloud physical monitoring service switch on the server for which the monitoring service is to be deployed on the cloud platform includes:

[0018] Configure the cloud physical monitoring service switch on the server where the monitoring service is to be deployed in the global control file.

[0019] In some embodiments, the method further includes:

[0020] In response to the cloud physical monitoring service being turned off on some servers, the deployment of the first Telegraf service and Ironic service is refused on some servers.

[0021] In some embodiments, the method further includes:

[0022] Specify the server on which the monitoring service will be deployed using the Inventory file.

[0023] Another aspect of the present invention provides a cloud physical machine monitoring service deployment system, comprising:

[0024] The file storage module is configured to store the Telegraf executable file on the cloud platform and to set the cloud physical monitoring service switch for the server on the cloud platform where the monitoring service to be deployed.

[0025] The service deployment module configures the cloud physical monitoring service switch for responding to the server to be enabled, deploys the first Telegraf service for the server based on the Telegraf executable file, and deploys the Ironic service for the server.

[0026] The startup module is configured to start the first Telegraf service and its specified listening port; and

[0027] The monitoring service deployment module is configured to start the Ironic service and distribute the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service. This enables the cloud physical machine to start a second Telegraf service based on the Telegraf executable file, and transmits monitoring information to the listening port through the data output port of the second Telegraf service, so that the cloud platform can monitor the cloud physical machine.

[0028] In another aspect, the present invention provides a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the above-described method.

[0029] In another aspect, the present invention provides a computer device including a memory and a processor, wherein the memory stores a computer program that, when executed by the processor, performs the above-described method.

[0030] The present invention has at least the following beneficial technical effects:

[0031] The cloud physical machine monitoring service deployment method of the present invention stores the Telegraf executable file in the cloud platform, adds a cloud physical monitoring service switch to the server on the cloud platform where the monitoring service is to be deployed, and deploys a first Telegraf service and an Ironic service to the server based on the Telegraf executable file when the cloud physical monitoring service is enabled. The first Telegraf service and its designated listening port are started, and the Ironic service is also started. The Telegraf executable file is then distributed to the cloud physical machine to be monitored via the Ironic service. The cloud physical machine then starts a second Telegraf service based on the Telegraf executable file, and transmits monitoring information to the listening port through the data output port of the second Telegraf service. This enables the cloud platform to monitor the cloud physical machine, thus realizing a complete cloud physical machine monitoring scheme that ensures real-time monitoring of the cloud physical machine's status and guarantees the stable operation of the cloud platform. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a schematic diagram of a cloud physical machine monitoring service deployment method provided according to an embodiment of the present invention;

[0034] Figure 2 A schematic diagram illustrating the process of building a Telegraf container image according to an embodiment of the present invention;

[0035] Figure 3 This is a schematic diagram illustrating the deployment process of the Telegraf service according to an embodiment of the present invention;

[0036] Figure 4 This is a schematic diagram illustrating the deployment process of Ironic services according to an embodiment of the present invention;

[0037] Figure 5 This is a schematic diagram of a cloud physical machine monitoring service deployment system provided according to an embodiment of the present invention;

[0038] Figure 6 A schematic diagram of a computer-readable storage medium for implementing a cloud physical machine monitoring service deployment method according to an embodiment of the present invention;

[0039] Figure 7This is a schematic diagram of the hardware structure of a computer device for implementing a cloud physical machine monitoring service deployment method according to an embodiment of the present invention. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to specific examples and the accompanying drawings.

[0041] It should be noted that all uses of "first" and "second" in the embodiments of the present invention are for the purpose of distinguishing two different entities or different parameters with the same name. Therefore, "first" and "second" are merely for convenience of expression and should not be construed as limiting the embodiments of the present invention. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, such as other steps or units inherent in a process, method, system, product, or device that includes a series of steps or units.

[0042] Based on the above objectives, the first aspect of the present invention provides an embodiment of a cloud physical machine monitoring service deployment method. Figure 1 This diagram illustrates an embodiment of the cloud physical machine monitoring service deployment method provided by the present invention. Figure 1 As shown, the embodiments of the present invention include the following steps:

[0043] Step S10: Store the Telegraf executable file on the cloud platform and set the cloud physical monitoring service switch on the server to be deployed for the monitoring service on the cloud platform.

[0044] Step S20: In response to the server's cloud physical monitoring service switch being turned on, deploy the first Telegraf service for the server based on the Telegraf executable file, and deploy the Ironic service for the server.

[0045] Step S30: Start the first Telegraf service and its specified listening port;

[0046] Step S40: Start the Ironic service and distribute the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service, so that the cloud physical machine starts the second Telegraf service based on the Telegraf executable file, and transmits the monitoring information to the listening port through the data output port of the second Telegraf service, so that the cloud platform can monitor the cloud physical machine.

[0047] Telegraf is an open-source data collection agent primarily used to collect time-series data, such as server CPU (Central Processing Unit) metrics, memory metrics, and data generated by various IoT (Internet of Things) devices.

[0048] The cloud physical machine monitoring service deployment method of this invention involves storing a Telegraf executable file on a cloud platform, adding a cloud physical monitoring service switch to the server on the cloud platform where the monitoring service is to be deployed, and deploying a first Telegraf service and an Ironic service on the server based on the Telegraf executable file when the cloud physical monitoring service is enabled. The first Telegraf service and its designated listening port are started, and the Ironic service is also started. The Telegraf executable file is then distributed to the cloud physical machine to be monitored via the Ironic service. The cloud physical machine then starts a second Telegraf service based on the Telegraf executable file, and the monitoring information is transmitted to the listening port via the data output port of the second Telegraf service. This enables the cloud platform to monitor the cloud physical machine, thus achieving a complete cloud physical machine monitoring solution that ensures real-time monitoring of the cloud physical machine's status and guarantees the stable operation of the cloud platform.

[0049] In some embodiments, starting the first Telegraf service and its specified listening port includes: during the startup process of the first Telegraf service, specifying the listening port of the first Telegraf service through a Configmap, mounting the first configuration file containing the listening port parameter to the container, and starting the first Telegraf service to enable the listening function of the listening port.

[0050] In some embodiments, starting the Ironic service and distributing the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service, so that the cloud physical machine starts the second Telegraf service based on the Telegraf executable file, includes: during the Ironic service startup process, mounting the Telegraf executable file to Conductor, specifying the data output port through Configmap, mounting the second configuration file containing the data output port parameters and server address to Conductor, starting the Ironic service, distributing the Telegraf executable file and the second configuration file to the cloud physical machine, and starting the second Telegraf service on the cloud physical machine.

[0051] In some embodiments, storing the Telegraf executable file on a cloud platform includes: building a container image with the Telegraf executable file installed, and pushing the container image to the cloud platform.

[0052] In some embodiments, setting a cloud physical monitoring service switch for a server on a cloud platform where a monitoring service is to be deployed includes: setting a cloud physical monitoring service switch for the server in a global control file.

[0053] In some embodiments, the method further includes: in response to the cloud physical monitoring service switch of a portion of the servers being turned off, refusing to deploy the first Telegraf service and the Ironic service on the portion of the servers.

[0054] In some embodiments, the method further includes: specifying the server for which the monitoring service is to be deployed via an Inventory file.

[0055] Figure 2 A schematic diagram illustrating the process of building a Telegraf container image according to an embodiment of the present invention is shown. Figure 3 A schematic diagram illustrating the deployment process of the Telegraf service according to an embodiment of the present invention is shown. Figure 4 A schematic diagram illustrating the deployment process of Ironic services according to an embodiment of the present invention is shown. Figure 2-4 As shown, the specific implementation steps of the cloud physical machine monitoring service deployment method of the present invention are as follows:

[0056] (1) Build a container image with the Telegraf executable installed;

[0057] (2) Push the image to the image repository corresponding to the OpenStack (an open-source cloud computing management platform project) environment;

[0058] (3) Add a switch to enable or disable cloud physical monitoring service in the global control file;

[0059] (4) Specify Telegraf and Ironic (Ironic is a project for bare-metal deployment and installation, providing the function of installing operating systems on servers and managing the entire lifecycle of server operation) service deployment nodes through the Inventory file.

[0060] (5) Design the deployment process for Telegraf service:

[0061] A. Enable Telegraf service deployment;

[0062] The B.Configmap file (an application interface resource object used to store non-key / value data, such as configuration files, environment variables, and command-line arguments) configures the Telegraf socket_listener (the listening port of the Telegraf service, which listens on the port in the operating system) parameter, specifying the data port that the Telegraf service listens on.

[0063] C. Generate a Telegraf-etc Configmap (the name of TelegrafConfigmap contains the configuration files that the Telegraf service depends on, including the port listening information specified earlier) using Helm (a command-line client tool);

[0064] D. Mount Telegraf-etc to the Telegraf Pod (a Pod is a group of containers that share storage, network, and declarations of how to run these containers; the Telegraf service mentioned earlier runs in a Pod, and the Telegraf service requires a configuration file to run, which needs to be mounted to the Pod by Telegraf-etc), and generate Telegraf.conf (the configuration file that the Telegraf service depends on) inside od as the service startup configuration file;

[0065] E. Start the Telegraf monitoring service on the cloud physical machine and enable business listening on the specified port of socket_listener (the listening port of the Telegraf service, which will listen to the service on that port in the operating system);

[0066] (6) Design the Ironic service startup process:

[0067] A. Start the Ironic service deployment;

[0068] B. Map the Telegraf executable to the Ironic-conductor Pod (a sub-service of the Ironic service that can send server-side data to bare metal nodes; here, this service is used to send the Telegraf executable to the bare metal node to be monitored) via hostPath (a method of mounting files in the Pod, where hostpath maps a specific file in the operating system to the Pod).

[0069] Configure the Telegraf socket_writer (Telegraf service data output port) parameter in the C.Configmap file to specify the monitoring data output port;

[0070] D. Obtain the IP address of the monitoring node and inject the IP into the Configmap;

[0071] E. Generate the Configmap into a Telegraf configuration file and mount it to Ironic-conductor (a sub-service of the Ironic service, which can send server-side data to bare-metal nodes; here, this service is used to send the Telegraf service executable to the bare-metal node to be monitored).

[0072] F. Start the Ironic Conductor service;

[0073] G. Distribute the Telegraf executable and Telegraf.conf mounted in the Ironic-conductor Pod to the created cloud physical machine system;

[0074] H. Start the Telegraf service in the cloud physical machine, and transmit the monitoring information to the cloud platform Telegraf service through socket_write, so that the cloud platform can monitor the cloud physical machine.

[0075] The above implementation of the cloud physical machine monitoring service deployment method first constructs a container image integrating the Telegraf executable. Simultaneously, the global control file in the deployment code is modified to add a switch to enable or disable the cloud physical machine monitoring service, and the monitoring service deployment node is specified through the Inventory file. During the Telegraf service startup process, the Configmap specifies the Telegraf monitoring port via socket_listener, maps it to a Telegraf.conf configuration file, and mounts it to the Pod. The Telegraf service is then started to listen for data on the specified port. During the Ironic service startup process, the Telegraf executable is mounted to Ironic-conductor. The Configmap specifies the monitoring node IP and data output port via socket_writer, maps it to a Telegraf.conf configuration file, and mounts it to Ironic-conductor. The Ironic service is then started, and the Telegraf executable and Telegraf.conf are distributed to the cloud physical machine operating system. The Telegraf service is then started on the cloud physical machine, outputting cloud physical machine monitoring information to the Telegraf service on the monitoring node.

[0076] A second aspect of this invention also provides a cloud physical machine monitoring service deployment system. Figure 5 This diagram illustrates an embodiment of the cloud physical machine monitoring service deployment system provided by the present invention. Figure 5 As shown, a cloud physical machine monitoring service deployment system includes: a file storage module 10, configured to store Telegraf executable files in the cloud platform and add a cloud physical monitoring service switch to the server on the cloud platform where the monitoring service is to be deployed; a service deployment module 20, configured to deploy a first Telegraf service and an Ironic service to the server based on the Telegraf executable file in response to the corresponding on / off state of the cloud physical monitoring service on the server; a startup module 30, configured to start the first Telegraf service and its specified listening port; and a monitoring service deployment module 40, configured to start the Ironic service, distribute the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service, and enable the cloud physical machine to start a second Telegraf service based on the Telegraf executable file, and transmit monitoring information to the listening port through the data output port of the second Telegraf service, so that the cloud platform can monitor the cloud physical machine.

[0077] The cloud physical machine monitoring service deployment system of this invention stores the Telegraf executable file on the cloud platform, adds a cloud physical monitoring service switch to the server on the cloud platform where the monitoring service is to be deployed, and deploys a first Telegraf service and an Ironic service on the server based on the Telegraf executable file when the cloud physical monitoring service is enabled. The system also starts the first Telegraf service and its designated listening port, and then uses the Ironic service to distribute the Telegraf executable file to the cloud physical machine to be monitored. The cloud physical machine then starts a second Telegraf service based on the Telegraf executable file, and transmits monitoring information to the listening port through the data output port of the second Telegraf service. This enables the cloud platform to monitor the cloud physical machine, thus achieving a complete cloud physical machine monitoring solution that ensures real-time monitoring of the cloud physical machine's status and guarantees the stable operation of the cloud platform.

[0078] In some embodiments, the startup module 30 is further configured to specify the listening port of the first Telegraf service through a Configmap during the startup process of the first Telegraf service, mount the first configuration file containing the listening port parameter to the container, and start the first Telegraf service to enable the listening function of the listening port.

[0079] In some embodiments, the monitoring service deployment module 40 includes a second startup module configured to mount the Telegraf executable file to Conductor during the Ironic service startup process, specify the data output port through Configmap, mount the second configuration file containing data output port parameters and server address to Conductor, start the Ironic service, distribute the Telegraf executable file and the second configuration file to the cloud physical machine, and start the second Telegraf service on the cloud physical machine.

[0080] In some embodiments, the file storage module 10 is further configured to build a container image with the Telegraf executable installed and push the container image to the cloud platform.

[0081] In some embodiments, the file storage module 10 includes a switch addition module, configured to add a cloud physical monitoring service switch to the server to which the monitoring service is to be deployed in the global control file.

[0082] In some embodiments, the system further includes a deployment denial module configured to refuse deployment of the first Telegraf service and the Ironic service on the partial servers in response to the cloud physical monitoring service corresponding to the shutdown state of the partial servers.

[0083] In some embodiments, the system further includes a designation module configured to specify the server for which the monitoring service to be deployed is to be specified via an Inventory file.

[0084] A third aspect of the present invention also provides a computer-readable storage medium. Figure 6 A schematic diagram of a computer-readable storage medium for implementing a cloud physical machine monitoring service deployment method according to an embodiment of the present invention is shown. Figure 6 As shown, the computer-readable storage medium 3 stores computer program instructions 31. When executed by the processor, the computer program instructions 31 perform the following steps:

[0085] Store the Telegraf executable file on the cloud platform and set up the cloud physical monitoring service switch on the server where the monitoring service to be deployed is to be deployed on the cloud platform.

[0086] In response to the server's cloud physical monitoring service being enabled, the first Telegraf service is deployed on the server based on the Telegraf executable file, and the Ironic service is also deployed on the server.

[0087] Start the first Telegraf service and its specified listening port;

[0088] Start the Ironic service and distribute the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service. This enables the cloud physical machine to start a second Telegraf service based on the Telegraf executable file. The monitoring information is then transmitted to the listening port through the data output port of the second Telegraf service, so that the cloud platform can monitor the cloud physical machine.

[0089] In some embodiments, starting the first Telegraf service and its specified listening port includes: during the startup process of the first Telegraf service, specifying the listening port of the first Telegraf service through a Configmap, mounting the first configuration file containing the listening port parameter to the container, and starting the first Telegraf service to enable the listening function of the listening port.

[0090] In some embodiments, starting the Ironic service and distributing the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service, so that the cloud physical machine starts the second Telegraf service based on the Telegraf executable file, includes: during the Ironic service startup process, mounting the Telegraf executable file to Conductor, specifying the data output port through Configmap, mounting the second configuration file containing the data output port parameters and server address to Conductor, starting the Ironic service, distributing the Telegraf executable file and the second configuration file to the cloud physical machine, and starting the second Telegraf service on the cloud physical machine.

[0091] In some embodiments, storing the Telegraf executable file on a cloud platform includes: building a container image with the Telegraf executable file installed, and pushing the container image to the cloud platform.

[0092] In some embodiments, setting a cloud physical monitoring service switch for a server on a cloud platform where a monitoring service is to be deployed includes: setting a cloud physical monitoring service switch for the server in a global control file.

[0093] In some embodiments, the steps further include: in response to the cloud physical monitoring service switch of some servers being in a closed state, refusing to deploy the first Telegraf service and the Ironic service on some servers.

[0094] In some embodiments, the step further includes: specifying the server for which the monitoring service is to be deployed via an Inventory file.

[0095] It should be understood that, where there is no conflict, all the embodiments, features and advantages described above for the cloud physical machine monitoring service deployment method according to the present invention are equally applicable to the cloud physical machine monitoring service deployment system and storage medium according to the present invention.

[0096] A fourth aspect of the present invention also provides a computer device, including as follows: Figure 7 The memory 402 and processor 401 shown are provided. The memory 402 stores a computer program that, when executed by the processor 401, implements the method of any of the above embodiments.

[0097] like Figure 7 The diagram shown is a hardware structure schematic of an embodiment of the computer device for implementing the cloud physical machine monitoring service deployment method provided by the present invention. Figure 7 Taking the computer device shown as an example, this computer device includes a processor 401 and a memory 402, and may also include an input device 403 and an output device 404. The processor 401, memory 402, input device 403, and output device 404 can be connected via a bus or other means. Figure 7 Taking a bus connection as an example, input device 403 can receive input digital or character information, and generate key signal inputs related to user settings and function control of the cloud physical machine monitoring service deployment system. Output device 404 may include display devices such as a display screen.

[0098] Memory 402, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the cloud physical machine monitoring service deployment method in this embodiment. Memory 402 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created by the use of the cloud physical machine monitoring service deployment method, etc. In addition, memory 402 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 402 may optionally include memory remotely located relative to processor 401, and these remote memories can be connected to the local module via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0099] The processor 401 executes various server functions and data processing by running non-volatile software programs, instructions, and modules stored in the memory 402, thereby implementing the cloud physical machine monitoring service deployment method of the above method embodiment.

[0100] Finally, it should be noted that the computer-readable storage medium (e.g., memory) in this article may be volatile memory or non-volatile memory, or may include both volatile memory and non-volatile memory.

[0101] Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the functionality of various illustrative components, blocks, modules, circuits, and steps has been generally described. Whether this functionality is implemented as software or as hardware depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the functionality in various ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the embodiments disclosed herein.

[0102] The various exemplary logic blocks, modules, and circuits described herein can be implemented or performed using the following components designed to perform the functions herein: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP, and / or any other such configuration.

[0103] The above are exemplary embodiments disclosed in this invention. However, it should be noted that various changes and modifications can be made without departing from the scope of the embodiments of this invention as defined by the claims. The functions, steps, and / or actions of the methods according to the disclosed embodiments described herein do not need to be performed in any particular order. Furthermore, although the elements disclosed in the embodiments of this invention may be described or claimed individually, they may be understood as multiple unless explicitly limited to a singular number.

[0104] It should be understood that, as used herein, the singular form "a" is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations of one or more of the associatedly listed items. The embodiment numbers disclosed above are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0105] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A method for deploying a cloud physical machine monitoring service, characterized in that, Includes the following steps: Store the Telegraf executable file on the cloud platform, and set the cloud physical monitoring service switch on the server of the monitoring service to be deployed on the cloud platform; In response to the cloud physical monitoring service switch of the server being turned on, the first Telegraf service is deployed for the server based on the Telegraf executable file, and the Ironic service is deployed for the server; Start the first Telegraf service and its specified listening port; The Ironic service is started, and the Telegraf executable file is distributed to the cloud physical machine to be monitored through the Ironic service, so that the cloud physical machine starts a second Telegraf service based on the Telegraf executable file, and transmits monitoring information to the listening port through the data output port of the second Telegraf service, so that the cloud platform can monitor the cloud physical machine; Setting up the cloud physical monitoring service switch for the server on the cloud platform where the monitoring service is to be deployed includes: Configure the cloud physical monitoring service switch for the server where the monitoring service is to be deployed in the global control file.

2. The method according to claim 1, characterized in that, Starting the first Telegraf service and its specified listening port includes: During the startup process of the first Telegraf service, the listening port of the first Telegraf service is specified through Configmap, the first configuration file containing the listening port parameter is mounted to the container, and the first Telegraf service is started to enable the listening function of the listening port.

3. The method according to claim 1, characterized in that, Starting the Ironic service and distributing the Telegraf executable file to the cloud physical machine to be monitored via the Ironic service, so that the cloud physical machine starts the second Telegraf service based on the Telegraf executable file, includes: During the Ironic service startup process, the Telegraf executable file is mounted to the Conductor, the data output port is specified through the Configmap, and the second configuration file containing the data output port parameters and the server address is mounted to the Conductor. The Ironic service is then started, and the Telegraf executable file and the second configuration file are distributed to the cloud physical machine. The second Telegraf service is then started on the cloud physical machine.

4. The method according to claim 1, characterized in that, Storing the Telegraf executable file on a cloud platform includes: Build a container image with the Telegraf executable installed, and push the container image to the cloud platform.

5. The method according to claim 1, characterized in that, Also includes: In response to the cloud physical monitoring service being turned off on some servers, the deployment of the first Telegraf service and the Ironic service is refused on those servers.

6. The method according to claim 1, characterized in that, Also includes: The server for the monitoring service to be deployed is specified through the Inventory file.

7. A cloud physical machine monitoring service deployment system, characterized in that, include: The file storage module is configured to store the Telegraf executable file to the cloud platform and to set a cloud physical monitoring service switch for the server on the cloud platform where the monitoring service to be deployed. The service deployment module is configured to enable the cloud physical monitoring service switch in response to the server, deploy the first Telegraf service for the server based on the Telegraf executable file, and deploy the Ironic service for the server. The startup module is configured to start the first Telegraf service and its specified listening port. as well as The monitoring service deployment module is configured to start the Ironic service and distribute the Telegraf executable file to the cloud physical machine to be monitored through the Ironic service, so that the cloud physical machine starts a second Telegraf service based on the Telegraf executable file, and transmits monitoring information to the listening port through the data output port of the second Telegraf service, so that the cloud platform can monitor the cloud physical machine; Setting up the cloud physical monitoring service switch for the server on the cloud platform where the monitoring service is to be deployed includes: Configure the cloud physical monitoring service switch for the server where the monitoring service is to be deployed in the global control file.

8. A computer-readable storage medium, characterized in that, The system stores computer program instructions that, when executed by a processor, implement the method as described in any one of claims 1-6.

9. A computer device, comprising a memory and a processor, characterized in that, The memory stores a computer program, which, when executed by the processor, performs the method as described in any one of claims 1-6.

Images