Cloud platform management methods and related equipment

Abstract

This application discloses a cloud platform management method applied to a cloud management platform, comprising: generating a pull program for a target cloud platform based on configuration information; using the pull program to pull a current list of virtual machines from the target cloud platform; retrieving a historical list of virtual machines from local storage space; and updating the historical list of virtual machines based on the current list of virtual machines. By applying the technical solution provided in this application, virtual machine information in the cloud platform is obtained, providing a reliable guarantee for more secure and effective cloud platform management. This application also discloses a cloud management platform, an electronic device, and a computer-readable storage medium, which also have the above-mentioned beneficial effects.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a cloud platform management method, as well as a cloud management platform, electronic device, and computer-readable storage medium. Background Technology

[0002] With the rapid development of cloud computing technology, cloud platform security is receiving increasing attention, making a cloud security management platform an essential component. For a cloud security management platform, dynamically acquiring information about the cloud platform's assets, primarily virtual machine information, is both a fundamental and core function.

[0003] Therefore, how to obtain virtual machine information in the cloud platform in order to achieve more secure and effective cloud platform management is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] The purpose of this application is to provide a cloud platform management method that enables the acquisition of virtual machine information in the cloud platform, providing a reliable guarantee for more secure and effective cloud platform management; another purpose of this application is to provide a cloud management platform, electronic device and computer-readable storage medium, all of which have the above-mentioned beneficial effects.

[0005] Firstly, this application provides a cloud platform management method, applied to a cloud management platform, comprising:

[0006] Generate a pull program for the target cloud platform based on the configuration information;

[0007] The pull program is used to pull the current list of virtual machines from the target cloud platform;

[0008] Retrieve the historical list of virtual machines for the target cloud platform from local storage;

[0009] The historical virtual machine list is updated based on the current virtual machine list.

[0010] Optionally, before generating the pull program for the target cloud platform based on the configuration information, the method further includes:

[0011] Determine whether the information retrieval function for the target cloud platform is enabled based on the configuration information.

[0012] If so, then execute the step of generating a pull program for the target cloud platform based on the configuration information.

[0013] Optionally, the cloud platform management method may further include:

[0014] When the information retrieval function is not enabled, determine whether the retrieval program list contains historical retrieval programs related to the target cloud platform;

[0015] If so, delete the aforementioned history retrieval program.

[0016] Optionally, updating the historical virtual machine list based on the current virtual machine list includes:

[0017] The addition, deletion, and modification of virtual machines are determined based on the current virtual machine list and the historical virtual machine list;

[0018] Add the newly added virtual machine to the list of historical virtual machines;

[0019] Remove the virtual machine from the list of historical virtual machines;

[0020] Update the list of changed virtual machines in the historical virtual machine list.

[0021] Optionally, the historical virtual machine list includes a managed virtual machine list and an unmanaged virtual machine list, and adding the new virtual machine to the historical virtual machine list includes:

[0022] Determine whether the newly added virtual machine is a managed virtual machine;

[0023] If so, add the newly added virtual machine to the list of managed virtual machines;

[0024] If not, the newly added virtual machine will be added to the list of unmanaged virtual machines.

[0025] Optionally, determining whether the newly added virtual machine is a managed virtual machine includes:

[0026] Determine whether security hardening software is deployed in the newly added virtual machine;

[0027] If so, then the newly added virtual machine is determined to be the managed virtual machine;

[0028] If not, then the newly added virtual machine is determined to be a non-managed virtual machine.

[0029] Optionally, deleting the virtual machine from the list of historical virtual machines includes:

[0030] Determine whether the number of times the virtual machine has been deleted has reached a preset number;

[0031] If so, the virtual machine to be deleted will be removed from the list of historical virtual machines.

[0032] Secondly, this application also discloses a cloud management platform, including:

[0033] The generation module is used to generate a pull program for the target cloud platform based on the configuration information;

[0034] A pull module is used to pull the current list of virtual machines from the target cloud platform using the pull program;

[0035] The retrieval module is used to retrieve the historical list of virtual machines of the target cloud platform from the local storage space;

[0036] The update module is used to update the historical virtual machine list based on the current virtual machine list.

[0037] Thirdly, this application also discloses an electronic device, comprising:

[0038] Memory, used to store computer programs;

[0039] A processor, used to execute the computer program to implement any of the cloud platform management methods described above.

[0040] Fourthly, this application also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the cloud platform management methods described above.

[0041] This application provides a cloud platform management method applied to a cloud management platform, comprising: generating a pull program for a target cloud platform based on configuration information; using the pull program to pull a current list of virtual machines from the target cloud platform; retrieving a historical list of virtual machines from local storage space; and updating the historical list of virtual machines based on the current list of virtual machines.

[0042] By applying the technical solution provided in this application, a cloud management platform is created to manage the virtual machine lists of various cloud platforms, thereby facilitating the effective management of each cloud platform. Based on the cloud management platform, configuration information for generating a pull program is set for the target cloud platform, enabling the pull program to retrieve the latest virtual machine list from the target cloud platform and obtain the current virtual machine list of the target cloud platform. This current virtual machine list can then be used to update the historical virtual machine list stored locally, thus achieving the acquisition of virtual machine information in the target cloud platform and providing a reliable guarantee for more secure and effective cloud platform management.

[0043] The cloud management platform, electronic device, and computer-readable storage medium provided in this application all have the aforementioned beneficial effects, which will not be elaborated further here. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the prior art and the embodiments of this application, the accompanying drawings used in the description of the prior art and the embodiments of this application will be briefly introduced below. Of course, the accompanying drawings described below with respect to the embodiments of this application are only a part of the embodiments in this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort, and such other drawings also fall within the protection scope of this application.

[0045] Figure 1 A schematic diagram of the structure of a cloud system provided in this application;

[0046] Figure 2 A flowchart illustrating a cloud platform management method provided in this application;

[0047] Figure 3 A flowchart illustrating a method for pulling programs provided in this application;

[0048] Figure 4 A flowchart illustrating a virtual machine list update method provided in this application;

[0049] Figure 5 A schematic diagram of the structure of a cloud management platform provided in this application;

[0050] Figure 6 This is a schematic diagram of the structure of an electronic device provided in this application. Detailed Implementation

[0051] The core of this application is to provide a cloud platform management method that enables the acquisition of virtual machine information in the cloud platform, providing a reliable guarantee for more secure and effective cloud platform management. Another core aspect of this application is to provide a cloud management platform, electronic device, and computer-readable storage medium, all of which have the aforementioned beneficial effects.

[0052] To provide a clearer and more complete description of the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0053] It should be noted that the cloud platform management method provided in this application is applied to a cloud management platform. Please refer to [the relevant documentation / reference]. Figure 1 , Figure 1This is a schematic diagram of a cloud system provided in this application. The cloud system mainly includes a cloud management platform and multiple cloud platforms. The cloud management platform establishes communication relationships with each cloud platform. The cloud management platform is used to obtain virtual machine information from each cloud platform to facilitate more secure and effective management of each cloud platform. It should also be noted that the cloud platform management method provided in this application is applicable not only to multi-cloud scenarios but also to single-cloud scenarios.

[0054] This application provides a cloud platform management method.

[0055] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating a cloud platform management method provided in this application. The cloud platform management method is applied to a cloud management platform and may include the following steps S101 to S104.

[0056] S101: Generate a pull program for the target cloud platform based on the configuration information;

[0057] This step aims to generate a pull program based on the configuration information, which is the aforementioned pull program for the target cloud platform. Specifically, the target cloud platform is the cloud platform for which the cloud management platform needs to obtain virtual machine information, i.e., the cloud platform that needs to be managed; the pull program is used to pull virtual machine information from the target cloud platform, i.e., the current list of virtual machines on the target virtual machine platform described below; the configuration information is used to generate the pull information, the content of which may include, but is not limited to, relevant information of the target cloud platform (such as the address, name, username, password, etc. of the target cloud platform), information of the target data to be obtained (such as the name, category, storage location, etc. of the target data; in this embodiment, the target data is virtual machine information), and pull function configuration information (such as whether to enable the pull function, timed pull, real-time pull, or automatic pull based on preset trigger conditions, etc.), etc., which can be set by technical personnel according to actual needs, and this application does not limit this.

[0058] During the implementation process, users can input various configuration information according to their actual needs. Furthermore, after receiving the configuration information, the cloud management platform can import it into the pre-configured basic template to generate a pull program for the target cloud platform. This program can then be used to pull the latest virtual machine information from the target cloud platform, which is the current virtual machine list described below.

[0059] S102: Use the pull program to pull the current list of virtual machines from the target cloud platform;

[0060] This step aims to retrieve the current list of virtual machines (VMs) on the target cloud platform using a fetch program. After generating the fetch program based on the configuration information, it can be started to retrieve the current VM list from the target cloud platform. This current VM list represents the latest VM list on the target cloud platform, providing the most accurate VM information. Based on this, the cloud management platform can obtain VM information from the target cloud platform, ensuring secure and effective cloud platform management.

[0061] S103: Retrieve the historical list of virtual machines for the target cloud platform from local storage;

[0062] This step aims to obtain the historical virtual machine list. As mentioned above, the cloud management platform can manage multiple cloud platforms. The cloud management platform maintains a virtual machine list for each cloud platform. However, without updates, these lists are historical and lag behind the current virtual machine list maintained by the cloud platform itself. Therefore, the cloud management platform can retrieve its own historical virtual machine list for the target cloud platform to update the historical virtual machine list based on the current list obtained in S102, thereby enabling the cloud management platform to obtain the latest virtual machine information for the target cloud platform.

[0063] The historical virtual machine list can be stored in local storage. Therefore, when retrieving the historical virtual machine list of the target cloud platform, it can be retrieved directly from local storage. It's understandable that local storage contains historical virtual machine lists for multiple cloud platforms. To obtain the historical virtual machine list of the target cloud platform, relevant information about the target cloud platform, such as its name or address, can be extracted first from the configuration information. Then, based on this information, the historical virtual machine list for the target cloud platform can be searched from numerous historical virtual machine lists.

[0064] S104: Update the historical virtual machine list based on the current virtual machine list.

[0065] This step aims to update the historical virtual machine list based on the current virtual machine list, thereby enabling the cloud management platform to obtain the latest virtual machine information in the target cloud platform, providing a reliable guarantee for secure and efficient cloud platform management.

[0066] As can be seen, the cloud platform management method provided in this application creates a cloud management platform to manage the virtual machine list of each cloud platform, thereby facilitating the effective management of each cloud platform. Based on the cloud management platform, configuration information for generating a pull program is set for the target cloud platform, so that the pull program can be used to pull the latest virtual machine list in the target cloud platform to obtain the current virtual machine list of the target cloud platform. Thus, the current virtual machine list can be used to update the historical virtual machine list stored locally, thereby realizing the acquisition of virtual machine information in the target cloud platform and providing a reliable guarantee for achieving more secure and effective cloud platform management.

[0067] In one embodiment of this application, before generating the pull program for the target cloud platform based on the configuration information, the following steps may also be included:

[0068] Determine whether the information retrieval function for the target cloud platform is enabled based on the configuration information;

[0069] If so, then proceed with the step of generating a pull program for the target cloud platform based on the configuration information.

[0070] For each cloud platform managed by the cloud management platform, the information retrieval function can be enabled or disabled according to actual needs. That is, for each cloud platform, it can be preset whether to obtain virtual machine information. When the information retrieval function is enabled, the virtual machine information of the corresponding cloud platform needs to be obtained. When the information retrieval function is disabled, the virtual machine information of the corresponding cloud platform does not need to be obtained.

[0071] Therefore, before generating the pull program based on the configuration information, you can first determine whether the information pull function for the target cloud platform is enabled. If the information pull function is enabled, you can continue to execute the step of generating the pull program based on the configuration information. Otherwise, if the information pull function is not enabled, you can stop executing the step of generating the pull program based on the configuration information and exit the current operation.

[0072] Determining whether the target cloud platform has enabled the information retrieval function can be based on the configuration information. In other words, the configuration information may contain configuration items related to the information retrieval function. Therefore, after obtaining the configuration information, the configuration items related to the information retrieval function can be extracted first, and then the determination of whether the target cloud platform has enabled the information retrieval function can be made based on these configuration items.

[0073] In one embodiment of this application, the cloud platform management method may further include the following steps:

[0074] When the information retrieval function is not enabled, determine whether the retrieval program list contains historical retrieval programs related to the target cloud platform;

[0075] If so, delete the historical fetching program.

[0076] Understandably, a cloud management platform may not have a single pull program for a single cloud platform. It may set up multiple different pull programs for different information retrieval needs. Therefore, in actual operation, when receiving configuration information to determine whether to generate a pull program for the target cloud platform, the cloud management platform may already be running one or more historical pull programs for the target cloud platform, and each historical pull program is in a running state. Based on this, when it is determined that the information pull function for the target cloud platform is not enabled, the historical pull programs for the target cloud platform can be deleted at the same time to satisfy the current configuration item of disabling the information pull function.

[0077] The historical fetch procedures can be stored in a fetch procedure list, which records every historical fetch procedure for each cloud platform. Therefore, when it is determined that the information fetching function is not enabled, the fetch procedure list can be traversed to determine whether it contains a historical fetch procedure for the target management platform. If it does, the historical fetch procedure for the target management platform can be directly deleted from the fetch procedure list; otherwise, the current operation process can be exited directly.

[0078] In one embodiment of this application, updating the historical virtual machine list based on the current virtual machine list may include the following steps:

[0079] Based on the current virtual machine list and the historical virtual machine list, determine which virtual machines to add, delete, and modify;

[0080] Add the new virtual machine to the list of historical virtual machines;

[0081] Remove the virtual machine from the list of historical virtual machines;

[0082] Update the list of changed virtual machines in the historical virtual machine list.

[0083] This application provides a method for updating a historical virtual machine list based on the current virtual machine list. After obtaining the current virtual machine list and the historical virtual machine list, set operations, such as intersection and complement operations, can be performed on the two lists to calculate the number of newly added, deleted, and modified virtual machines in the current virtual machine list compared to the historical virtual machine list. Specifically, based on the time points when the cloud management platform initially obtained the historical virtual machine list and when it obtained the current virtual machine list, newly added virtual machines are those newly added by the target cloud platform between these two time points; they exist in the current virtual machine list but not in the historical virtual machine list. Deleted virtual machines are those deleted by the target cloud platform between these two time points; they exist in the historical virtual machine list but not in the current virtual machine list. Modified virtual machines are those whose virtual machine information has changed by the target cloud platform between these two time points; they exist in both the current and historical virtual machine lists.

[0084] Furthermore, for newly added virtual machines, if they exist in the current virtual machine list but not in the historical virtual machine list, they can be added to the historical virtual machine list. For deleted virtual machines, if they exist in the historical virtual machine list but not in the current list, they can be deleted from the historical virtual machine list. For updated virtual machines, although they exist in both the current and historical virtual machine lists, if the virtual machine information has changed, the information in the current virtual machine list should be used to update the historical virtual machine list, and the original virtual machine information of the changed virtual machine in the historical virtual machine list should be deleted. This completes the update of the historical virtual machine list, thus enabling the cloud management platform to obtain virtual machine information from the target cloud platform.

[0085] In one embodiment of this application, the historical virtual machine list may include a managed virtual machine list and an unmanaged virtual machine list. Adding a new virtual machine to the historical virtual machine list may include the following steps:

[0086] Determine whether the newly added virtual machine is a managed virtual machine;

[0087] If so, add the new virtual machine to the list of managed virtual machines;

[0088] If not, the newly added virtual machine will be added to the list of unmanaged virtual machines.

[0089] This application provides a method for adding new virtual machines to a historical virtual machine list. It is understood that for each cloud platform, the cloud management platform can manage all virtual machines on the cloud platform, or it can manage only a portion of the virtual machines. Therefore, the historical virtual machine list of the target cloud platform stored in the cloud management platform can include a controlled virtual machine list and an uncontrolled virtual machine list. The controlled virtual machine list records information about each virtual machine on the target cloud platform that is controlled by the cloud management platform, while the uncontrolled virtual machine list records information about each virtual machine on the target cloud platform that is not controlled by the cloud management platform. Therefore, when updating the historical virtual machine list using the current virtual machine list, the specific process involves updating both the controlled and uncontrolled virtual machine lists of the target cloud platform.

[0090] During the implementation process, after identifying a new virtual machine, it can be first determined whether it belongs to the managed virtual machines of the cloud management platform. If it is a managed virtual machine, the new virtual machine and its related information can be added to the managed virtual machine list. If it is not a managed virtual machine, the new virtual machine and its related information can be added to the unmanaged virtual machine list.

[0091] In one embodiment of this application, determining whether a newly added virtual machine is a managed virtual machine may include the following steps:

[0092] Determine whether security hardening software is deployed in the newly added virtual machine;

[0093] If so, then confirm that the newly added virtual machine is a managed virtual machine;

[0094] If not, then the newly added virtual machine is not a managed virtual machine.

[0095] This application provides a method for determining whether a newly added virtual machine is a managed virtual machine, specifically by determining whether security hardening software is deployed on the newly added virtual machine. When security hardening software is deployed on the newly added virtual machine, it can be identified as a managed virtual machine; when no security hardening software is deployed on the newly added virtual machine, it can be identified as not a managed virtual machine. The security hardening software can be deployed by technical personnel according to actual needs, and its type is not unique; this application does not limit its application.

[0096] In one embodiment of this application, deleting a virtual machine from the historical virtual machine list may include the following steps:

[0097] Determine if the number of virtual machine deletion attempts has reached the preset limit;

[0098] If so, the virtual machine will be removed from the list of historical virtual machines.

[0099] This application provides a method for deleting a virtual machine from a historical virtual machine list. It is understood that due to potential instability in communication links, data transmission between the cloud management platform and the target cloud platform may be affected, leading to delays or inaccuracies in the obtained virtual machine information. For example, a determined deleted virtual machine may not actually be deleted; rather, relevant information about that deleted virtual machine may simply not have been obtained.

[0100] Therefore, to avoid accidental deletion, a maximum number of deletion attempts can be preset, as mentioned above. After determining to delete a virtual machine, it can be first checked whether the deletion attempt has reached the preset number. If it has, the step of deleting the virtual machine from the historical virtual machine list is executed. Conversely, if the deletion attempt has not reached the preset number, due to the possibility of accidental deletion, the deletion attempt can be skipped. Instead, the deletion attempt can be incremented to update the count until the preset number is reached, at which point the virtual machine is deleted from the historical virtual machine list. The value of the preset number does not affect the implementation of this technical solution and can be set by technical personnel according to actual conditions; this application does not impose any restrictions on it. Obviously, this implementation method can effectively avoid cloud platform management risks caused by accidental deletion.

[0101] Based on the above embodiments:

[0102] This application provides another cloud platform management method.

[0103] First, before retrieving virtual machine information from the cloud platform, relevant information needs to be configured. The configuration mainly includes: cloud platform name, cloud platform IP, cloud platform username, cloud platform password, whether to enable the asset import function (i.e., the above information retrieval function), the retrieval time interval, whether to enable the automatic virtual machine deletion switch (when the switch is enabled, the virtual machine will be automatically deleted if it is not retrieved after 6 retrieval attempts), and cloud platform retrieval information configuration. The cloud platform retrieval information configuration mainly includes the cloud platform login URL (Universal Resource Locator), cloud platform asset (in this application, mainly refers to virtual machine information) retrieval URL, and the corresponding field names of the four pieces of information in the cloud platform asset retrieval URL: cloud platform asset UUID (Universally Unique Identifier), name, IP address, and operating system.

[0104] When the asset import function is disabled, the cloud platform asset retrieval operation will not be executed. Furthermore, if the asset import function was enabled before this configuration, all previous retrieval programs for that cloud platform will be destroyed. When the asset import function is enabled, a new asset import program (i.e., the retrieval program) will be generated based on the asset import template. A new thread will be started to run this program, and the thread number will be recorded. The asset import template is a general import program; by filling in the above-mentioned configuration information, a specific program—the asset retrieval program for that cloud platform—will be generated. This retrieval program will periodically retrieve the list of virtual machines from the cloud platform.

[0105] For example, please refer to Figure 3 , Figure 3 This is a flowchart illustrating a method for generating a pull program provided in this application. By importing the input configuration information into a basic template, a pull program can be generated; multiple configuration information can generate multiple pull programs. The pull program can run on a scheduled basis. Furthermore, a corresponding relationship is generated along with the pull program. When the pull function of a certain cloud platform is disabled, the corresponding pull program ID can be read from this list, thereby terminating the pull program.

[0106] Secondly, please refer to Figure 4 , Figure 4 This is a flowchart illustrating a virtual machine list update method provided in this application.

[0107] First, based on the URL obtained from the cloud platform assets, retrieve the list of all virtual machines (i.e., the current list of virtual machines mentioned above, including UUID, name, operating system, IP address, IP from the cloud platform, etc.). For the cloud management platform, there are two types of virtual machines: one with virtual machine security hardening software deployed and the other without. Among them, those with virtual machine security hardening software deployed are under the control of the cloud management platform, otherwise they are pending control.

[0108] Furthermore, the system retrieves its own stored list of virtual machines (i.e., the historical list of virtual machines mentioned above), and performs a set operation on it and the list of virtual machines obtained from the cloud platform to obtain a list of newly added virtual machines (existing only on the cloud platform), a list of deleted virtual machines (existing only on the cloud management platform), and a list of existing virtual machines (existing on both the cloud platform and the cloud management platform).

[0109] (1) Newly added virtual machine lists can be added to the historical virtual machine list, including the managed virtual machine list and the unmanaged virtual machine list. The unmanaged virtual machine list can provide a query function to view all virtual machines that are not currently managed by the cloud management platform.

[0110] (2) For the list of deleted virtual machines, the number of deletions can be recorded. Each time a virtual machine is found to have been deleted, the number of deletions is incremented by 1. If the automatic deletion switch is enabled in the configuration, the virtual machine will be deleted from the historical virtual machine list when the cumulative number of deletions exceeds the threshold (default 6 times). Otherwise, the current deletion status of the virtual machine will only be marked.

[0111] (3) For an existing list of virtual machines, it can be determined whether the virtual machine information, such as IP, operating system, virtual machine name, etc., needs to be updated. For virtual machines in the list that are not managed by the cloud management platform, if the IP, operating system, virtual machine name, etc., change, they can be updated directly. For virtual machines in the list that have been managed by the cloud management platform, the IP, operating system, etc., will not be updated, and only the virtual machine name will be synchronized.

[0112] This completes the cloud management platform's acquisition of virtual machine information from the cloud platform.

[0113] As can be seen, the cloud platform management method provided in this application creates a cloud management platform to manage the virtual machine list of each cloud platform, thereby facilitating the effective management of each cloud platform. Based on the cloud management platform, configuration information for generating a pull program is set for the target cloud platform, so that the pull program can be used to pull the latest virtual machine list in the target cloud platform to obtain the current virtual machine list of the target cloud platform. Thus, the current virtual machine list can be used to update the historical virtual machine list stored locally, thereby realizing the acquisition of virtual machine information in the target cloud platform and providing a reliable guarantee for achieving more secure and effective cloud platform management.

[0114] This application provides a cloud management platform.

[0115] Please refer to Figure 5 , Figure 5 This application provides a schematic diagram of the structure of a cloud management platform, which may include:

[0116] Generation module 1 is used to generate a pull program for the target cloud platform based on the configuration information;

[0117] Pull module 2 is used to pull the current list of virtual machines from the target cloud platform using a pull program;

[0118] Module 3 is used to retrieve the historical list of virtual machines of the target cloud platform from the local storage space;

[0119] Update module 4 is used to update the historical virtual machine list based on the current virtual machine list.

[0120] As can be seen, the technical solution provided in this application creates a cloud management platform to manage the virtual machine lists of various cloud platforms, thereby facilitating the effective management of each cloud platform. Based on the cloud management platform, configuration information for generating a pull program is set for the target cloud platform, so that the pull program can be used to pull the latest virtual machine list from the target cloud platform to obtain the current virtual machine list of the target cloud platform. Thus, the current virtual machine list can be used to update the historical virtual machine list stored locally, thereby realizing the acquisition of virtual machine information in the target cloud platform and providing a reliable guarantee for more secure and effective cloud platform management.

[0121] In one embodiment of this application, the cloud management platform may further include a function judgment module, which is used to determine whether the information retrieval function for the target cloud platform is enabled based on the configuration information before generating the retrieval program for the target cloud platform based on the configuration information; if so, the step of generating the retrieval program for the target cloud platform based on the configuration information is executed.

[0122] In one embodiment of this application, the cloud management platform may further include a program deletion module, which is used to determine whether the program retrieval list contains historical programs related to the target cloud platform when the information retrieval function is not enabled; if so, the historical program retrieval is deleted.

[0123] In one embodiment of this application, the update module 4 may include:

[0124] The filtering unit is used to determine which virtual machines to add, delete, or modify based on the current virtual machine list and the historical virtual machine list.

[0125] Add a unit to add a new virtual machine to the list of historical virtual machines;

[0126] The delete unit is used to remove a virtual machine from the list of historical virtual machines.

[0127] The update unit is used to update the changed virtual machines in the historical virtual machine list.

[0128] In one embodiment of this application, the historical virtual machine list may include a managed virtual machine list and an unmanaged virtual machine list. The above-mentioned adding unit may be specifically used to determine whether the newly added virtual machine is a managed virtual machine; if so, the newly added virtual machine is added to the managed virtual machine list; if not, the newly added virtual machine is added to the unmanaged virtual machine list.

[0129] In one embodiment of this application, the above-mentioned adding unit can be specifically used to determine whether security hardening software is deployed in the newly added virtual machine; if so, the newly added virtual machine is determined to be a managed virtual machine; if not, the newly added virtual machine is determined to be a managed virtual machine.

[0130] In one embodiment of this application, the deletion unit can be specifically used to determine whether the number of times the virtual machine has been deleted has reached a preset number; if so, the virtual machine is deleted from the historical virtual machine list.

[0131] For a description of the cloud management platform provided in this application, please refer to the above method embodiments; further details will not be provided here.

[0132] This application provides an electronic device.

[0133] Please refer to Figure 6 , Figure 6 This application provides a schematic diagram of the structure of an electronic device, which may include:

[0134] Memory, used to store computer programs;

[0135] A processor, used to execute computer programs, can implement the steps of any of the cloud platform management methods described above.

[0136] like Figure 6 The diagram shows the structural composition of an electronic device, which may include a processor 10, a memory 11, a communication interface 12, and a communication bus 13. The processor 10, memory 11, and communication interface 12 all communicate with each other through the communication bus 13.

[0137] In this embodiment, the processor 10 may be a central processing unit (CPU), an application-specific integrated circuit, a digital signal processor, a field-programmable gate array, or other programmable logic devices.

[0138] The processor 10 can call programs stored in the memory 11. Specifically, the processor 10 can execute operations in the embodiments of the cloud platform management method.

[0139] The memory 11 is used to store one or more programs. The programs may include program code, which includes computer operation instructions. In this embodiment, the memory 11 stores at least a program for implementing the following functions:

[0140] Generate a pull program for the target cloud platform based on the configuration information;

[0141] Use a pull program to retrieve the current list of virtual machines from the target cloud platform;

[0142] Retrieve the historical list of virtual machines from the target cloud platform from local storage;

[0143] Update the historical virtual machine list based on the current virtual machine list.

[0144] In one possible implementation, the memory 11 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and applications required for at least one function; and the data storage area may store data created during use.

[0145] In addition, memory 11 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

[0146] Communication interface 12 can be an interface for the communication module, used to connect with other devices or systems.

[0147] Of course, it should be noted that, Figure 6 The structure shown does not constitute a limitation on the electronic device in the embodiments of this application. In practical applications, the electronic device may include more than Figure 6 More or fewer components as shown, or combinations of certain components.

[0148] This application provides a computer-readable storage medium.

[0149] The computer-readable storage medium provided in this application embodiment stores a computer program, which, when executed by a processor, can implement the steps of any of the cloud platform management methods described above.

[0150] The computer-readable storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0151] For a description of the computer-readable storage medium provided in the embodiments of this application, please refer to the above method embodiments; further details will not be repeated here.

[0152] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0153] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0154] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0155] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this application. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of this application.

Claims

1. A cloud platform management method, characterized in that, Applications in cloud management platforms, including: Generate a pull program for the target cloud platform based on the configuration information; The pull program is used to pull the current list of virtual machines from the target cloud platform; Retrieve the historical list of virtual machines for the target cloud platform from local storage; Update the historical virtual machine list based on the current virtual machine list; Before generating the pull program for the target cloud platform based on the configuration information, the method further includes: determining whether the information pull function for the target cloud platform is enabled based on the configuration information; if so, then executing the step of generating the pull program for the target cloud platform based on the configuration information. The step of updating the historical virtual machine list based on the current virtual machine list includes: determining new virtual machines, deleted virtual machines, and modified virtual machines based on the current virtual machine list and the historical virtual machine list; adding the new virtual machines to the historical virtual machine list; deleting the deleted virtual machines from the historical virtual machine list; and updating the modified virtual machines in the historical virtual machine list. The step of deleting the virtual machine from the historical virtual machine list includes: determining whether the number of times the virtual machine has been deleted has reached a preset number; if so, deleting the virtual machine from the historical virtual machine list.

2. The cloud platform management method according to claim 1, characterized in that, Also includes: When the information retrieval function is not enabled, determine whether the retrieval program list contains historical retrieval programs related to the target cloud platform; If so, delete the aforementioned history retrieval program.

3. The cloud platform management method according to claim 1, characterized in that, The historical virtual machine list includes a managed virtual machine list and an unmanaged virtual machine list. Adding the new virtual machine to the historical virtual machine list includes: Determine whether the newly added virtual machine is a managed virtual machine; If so, add the newly added virtual machine to the list of managed virtual machines; If not, the newly added virtual machine will be added to the list of unmanaged virtual machines.

4. The cloud platform management method according to claim 3, characterized in that, The determination of whether the newly added virtual machine is a managed virtual machine includes: Determine whether security hardening software is deployed in the newly added virtual machine; If so, then the newly added virtual machine is determined to be the managed virtual machine; If not, then the newly added virtual machine is determined to be a non-managed virtual machine.

5. A cloud management platform, characterized in that, include: The generation module is used to generate a pull program for the target cloud platform based on the configuration information; A pull module is used to pull the current list of virtual machines from the target cloud platform using the pull program; The retrieval module is used to retrieve the historical list of virtual machines of the target cloud platform from the local storage space; The update module is used to update the historical virtual machine list based on the current virtual machine list; It also includes a judgment module, which is used to determine whether the information retrieval function for the target cloud platform is enabled based on the configuration information before generating the retrieval program for the target cloud platform based on the configuration information; if so, the step of generating the retrieval program for the target cloud platform based on the configuration information is executed. The update module is specifically used to determine new virtual machines, deleted virtual machines, and modified virtual machines based on the current virtual machine list and the historical virtual machine list; add the new virtual machines to the historical virtual machine list; delete the deleted virtual machines from the historical virtual machine list; and update the modified virtual machines in the historical virtual machine list. The update module is specifically used to determine whether the number of times the deleted virtual machine has been deleted has reached a preset number; if so, the deleted virtual machine is deleted from the list of historical virtual machines.

6. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the cloud platform management method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the cloud platform management method as described in any one of claims 1 to 4.

Images