Virtualization instance management service scheduling method, system, equipment and medium
Patent Information
- Application Number
- CN202311084918.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-25
- Publication Date
- 2025-02-25
Smart Images
Figure CN119520613A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of Internet technology, and in particular to a virtualization instance management service scheduling method, system, device and readable storage medium. Background Art
[0002] Hyper-convergence is a product form in the post-virtualization era. The core functions of hyper-convergence are distributed storage systems (storage virtualization) and a unified resource management platform. It establishes a distributed storage system in the cloud computing data center scenario, and the storage virtualization solution is highly scalable. Each physical node in the hyper-converged cloud platform cluster has an iSCSI target service, where iSCSI refers to the Internet Small Computer System Interface, also known as IP-SAN, which is a storage technology based on the Internet and SCSI-3 protocol.
[0003] With the continuous development of Internet-related technologies, resource scheduling in hyper-converged cloud platform clusters and cloud platform virtual machine scheduling technologies are changing with each passing day, but there are still some defects in the existing technologies that are difficult to make up for. For example: when scheduling virtual machine and other virtualized instance components, only the resource satisfaction of the target physical node and the affinity of the virtualized instance to the physical node are considered, and the affinity of the cloud platform's system services to the virtualized instance is not considered from the cloud platform itself; there is a lack of application awareness, and the affinity of the system service to the application cannot be scheduled according to the application type. In particular, for cluster applications with multiple virtualized instances, there is a lack of affinity strategies for scheduling shared system services to multiple virtualized instances at the same time.
[0004] Therefore, in view of the above technical problems, it is necessary to provide a virtualization instance management service scheduling method, system, device and readable storage medium.
[0005] The information disclosed in this background technology section is only intended to enhance the understanding of the overall background of the invention and should not be regarded as an acknowledgment or any form of suggestion that the information constitutes the prior art already known to a person skilled in the art. Summary of the invention
[0006] The purpose of the present invention is to provide a virtualization instance management service scheduling method, which can increase the perception of applications when scheduling virtualization instance components such as virtual machines based on the affinity of the virtualization instance to the physical node, and schedule the affinity of system services to the application according to the application type.
[0007] To achieve the above purpose, the technical solution provided by the present invention is as follows:
[0008] In a first aspect, the present invention provides a virtualization instance management service scheduling method, which comprises:
[0009] Schedule standard virtualized instances in applications to physical nodes on the cloud platform;
[0010] In response to an iSCSI login request of the management service of the standard virtualization instance, obtaining information of the physical node where the standard virtualization instance is located;
[0011] Based on the information of the physical node where the standard virtualization instance is located, the login request is redirected to the iSCSI target service of the physical node.
[0012] In one or more embodiments, the standard virtualization instance includes:
[0013] If the application has only one virtualized instance, the virtualized instance is a standard virtualized instance;
[0014] If the application has multiple virtualized instances, the virtualized instance with the greatest load pressure is the standard virtualized instance.
[0015] In one or more embodiments, the method further comprises:
[0016] Setting the priority of the virtualized instance;
[0017] Set the physical node load pressure threshold;
[0018] A physical node having a load pressure less than the load pressure threshold and having the smallest communication delay with the physical node where the standard virtualization instance is located is selected as a standby node.
[0019] In one or more embodiments, the method further comprises:
[0020] If the load pressure of the physical node is greater than the load pressure threshold, redirecting the iSCSI login request of the management service of the virtualized instance with the lowest priority on the node to the iSCSI target service of the standby node;
[0021] If the load pressure of the iSCSI target service of the physical node is less than the load pressure threshold and the management services of the virtualized instances on the node are not all on the node, the login request of the management service of the virtualized instance with the highest priority on the physical node is redirected to the iSCSI target service of the physical node.
[0022] In one or more embodiments, the method further comprises:
[0023] If the application has multiple virtualized instances, the management services of the virtualized instances other than the standard virtualized instance under the same application are also redirected to the iSCSI target service of the physical node where the standard virtualized instance is located.
[0024] In one or more embodiments, the method further comprises:
[0025] Periodically traverse all virtualized instances of the same application and redirect standard virtualized instances to the iSCSI target service of the physical node where they are located.
[0026] In one or more embodiments, the virtualization instance management service is qemu-kvm.
[0027] In a second aspect, the present invention provides a virtualization instance scheduling system, which includes:
[0028] The scheduling module is used to schedule standard virtualized instances in applications to physical nodes on the cloud platform;
[0029] An acquisition module, configured to obtain information of a physical node where the standard virtualization instance is located in response to a login request of a virtualization instance management service;
[0030] The redirection module is used for redirecting the iSCSI login request to the iSCSI target service of the physical node where the virtualization instance is located based on the information of the physical node where the standard virtualization instance is located.
[0031] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the virtualization instance management service scheduling method by executing the computer instructions.
[0032] In a fourth aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the virtualization instance management service scheduling method.
[0033] Compared with the prior art, the virtualization instance management service scheduling method provided by the present invention schedules the standard virtualization instance in the application to the physical node of the cloud platform; in response to the iSCSI login request of the management service of the standard virtualization instance, obtains the information of the physical node where the standard virtualization instance is located; based on the information of the physical node where the standard virtualization instance is located, redirects the login request to the iSCSI target end service of the physical node. The virtualization instance management service scheduling method has the following advantages:
[0034] (1) When scheduling virtualized instance components such as virtual machines, not only the resource satisfaction of the target physical node is considered, but also the affinity of the virtualized instance to the physical node is emphasized.
[0035] (2) Consider the affinity of the cloud platform’s system services to virtualized instances from the cloud platform’s perspective, increase awareness of applications, and schedule the affinity of system services to applications based on application types. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 It is a schematic diagram of an application scenario of a virtualization instance management service scheduling method in one embodiment of the present invention;
[0037] Figure 2 It is a flow chart of virtualization instance management service scheduling in one embodiment of the present invention;
[0038] Figure 3 is a structural block diagram of a virtualization instance management service scheduling system in one embodiment of the present invention;
[0039] Figure 4 It is a structural block diagram of an electronic device in one embodiment of the present invention. DETAILED DESCRIPTION
[0040] The specific implementation modes of the present invention are described in detail below in conjunction with the accompanying drawings, but it should be understood that the protection scope of the present invention is not limited by the specific implementation modes.
[0041] Unless explicitly stated otherwise, throughout the specification and claims, the term “comprise” or variations such as “include” or “comprising”, etc., will be understood to include the stated elements or components but not to exclude other elements or components.
[0042] In order to facilitate understanding of the technical solutions of the present application, the technical terms that may appear in the present invention are first explained in detail below.
[0043] iSCSI (Internet Small Computer System Interface): also known as IP-SAN, is a storage technology based on the Internet and SCSI-3 protocol. It was proposed by IETF and became an official standard on February 11, 2003. It is a storage technology based on the Internet and SCSI-3 protocol, using TCP / IP ports 860 and 3260 as communication channels. By using the iSCSI protocol to exchange SCSI commands between two computers, the computers can simulate the SAN as a local storage device through a high-speed LAN hub. iSCSI uses the TCP / IP protocol (usually using TCP ports 860 and 3260). In essence, iSCSI allows two hosts to negotiate with each other through an IP network and then exchange SCSI commands. In this way, iSCSI uses a wide area network to simulate a commonly used high-performance local storage bus, thereby creating a storage area network (SAN).
[0044] Virtual machine: A virtual machine usually includes the entire operating system and applications, and runs a real operating system. In essence, a virtual machine is a different operating system installed on hardware virtualized by a hypervisor, while a container is a different process running on a host machine. From the user experience point of view, virtual machines are heavyweight, occupy a lot of physical resources, and take a long time to start. Containers occupy fewer physical resources and start quickly. Relatively speaking, virtual machines are more thoroughly isolated, while containers are less so.
[0045] Container: A container is a sandbox technology that is used to isolate applications from the outside world and to facilitate the transfer of the sandbox to other host machines. In essence, it is a special process.
[0046] Affinity: Affinity, in short, is who is close to. Based on this definition, we can get affinity is that something is close to something else. Since they are close, we need to bring these two things closer, or put them together or close to each other to achieve some benefits. In cloud computing research, affinity can generally reduce network latency between containers (virtual machines) or reduce communication energy consumption.
[0047] Hyper-convergence: Hyper-converged Infrastructure (HCI), also known as hyper-convergence architecture, is a product form in the virtualization era. It means that in the same unit device (x86 server), not only computing, network, storage and server virtualization resources and technologies are available, but also cache acceleration, deduplication, online data compression, backup software, snapshot technology and other elements are included. Multiple nodes can be aggregated through the network to achieve modular seamless horizontal expansion (scale-out) to form a unified resource pool. It simplifies deployment, reduces the difficulty and cost of operation and maintenance, improves the reliability and availability of equipment, and saves expenses.
[0048] In the existing technical solutions, there are methods for scheduling virtual machines and virtual machine-related instance components, including but not limited to: weighted comparison of resource information of other nodes with resource information of the first normally working node, and selection of target nodes based on comparison results; anti-affinity screening based on screening rules and information of each node to obtain target nodes; obtaining online Pod running status data and preset Pod running permission conditions; comparing the Pod running status data with the Pod running permission conditions, and generating target nodes based on comparison results, etc. However, there are still inevitable problems that the affinity of the cloud platform's system services to virtualized instances is not considered from the cloud platform itself; there is a lack of application awareness, and the affinity of system services to applications cannot be scheduled according to application types.
[0049] The inventor of the present invention has discovered the main shortcomings of the prior art and proposed a new technical implementation idea based on the shortcomings of the prior art: scheduling the service based on the affinity between the management service of the virtualization instance and the corresponding physical node, that is, by redirecting the iSCSI request of the virtualization instance to the same physical node or a nearby physical node as the virtualization instance, the iSCSI request access of the virtualization instance is accelerated and the storage access performance of the virtualization instance is improved.
[0050] Please refer to Figure 1 , which shows a schematic diagram of an application scenario of the virtualization instance management service scheduling method provided by the present invention. Figure 1The implementation scenario shown includes multiple physical nodes, multiple virtualization instances, and iSCSI requests for the management service of the virtualization instances corresponding to each virtualization instance. Specifically, the resource information of the physical node is first detected, and the virtualization instance is scheduled to a physical node that meets resource constraints. The management service of the virtualization instance will request a login from the iSCSI redirection service. In response to the login request, the iSCSI redirection service obtains network information such as the IP address of the physical node where the virtualization instance is located. Based on information such as the IP address of the physical node where the virtualization instance is located, the login request is preferentially redirected to the iSCSI target service of the physical node where the virtualization instance is located. If the load pressure of the physical node where the virtualization instance is located is too large, the login request is preferentially redirected to another node whose load pressure has not reached a threshold and whose communication delay with the virtualization instance is minimal, so as to maintain the affinity between the management service of the virtualization instance and the physical node.
[0051] It should be noted that the virtualization instance management service scheduling method of the embodiment of the present invention can be applied to the virtualization instance management service scheduling system of the embodiment of the present invention. The virtualization instance management service scheduling system can be configured in a terminal. The terminal can include but is not limited to a PC (Personal Computer), a PDA (tablet computer), a smart phone, a smart wearable device, and the like.
[0052] Please refer to Figure 2 FIG. 1 is a flow chart of virtualization instance management service scheduling in one embodiment of the present invention. The virtualization instance management service scheduling method specifically includes the following steps:
[0053] S201: Scheduling a standard virtualized instance in the application to a physical node of the cloud platform;
[0054] It should be noted that the virtualization instance includes but is not limited to a container, a virtual machine, etc., and the embodiment of the present invention does not limit this.
[0055] It should also be noted that the standard virtualization instance includes: if the application has only one virtualization instance, the virtualization instance is a standard virtualization instance; if the application has multiple virtualization instances, the virtualization instance with the greatest load pressure is the standard virtualization instance.
[0056] In particular, since the load pressure is prone to change, it is necessary to regularly traverse the virtualized instances under the application and redetermine the standard virtualized instances.
[0057] S202: Responding to an iSCSI login request of the management service of the standard virtualization instance, obtaining information of a physical node where the standard virtualization instance is located;
[0058] It should be noted that the physical node may be a computer, a router, a switch or other network equipment; the physical nodes may be connected together via wired or wireless technology, such as twisted pair, fiber optic cable, wireless local area network, etc., and the embodiments of the present invention do not limit the above contents.
[0059] S203: Based on the information of the physical node where the standard virtualization instance is located, redirect the login request to the iSCSI target service of the physical node.
[0060] It should be noted that in the study of cloud computing, affinity can reduce network delays between virtualized instances or reduce communication energy consumption. The iSCSI login request of the management service of the virtualized instance is redirected to the iSCSI target service of the physical node where the virtualized instance is located, so as to achieve the purpose of considering the affinity of the system services of the cloud platform to the virtualized instance from the cloud platform itself.
[0061] For example, create a virtual instance and configure a virtual disk. The virtual disk is provided by the iSCSI storage system and is provided to the virtual instance through the iSCSI target. When configuring the virtual disk for the virtual instance, the virtual instance management program, such as qemu-kvm, sends a request to the iSCSI redirector to establish a connection. The iSCSI redirector will redirect the request to the physical node where the virtual instance is located to establish a connection based on the situation of the physical node where the virtual instance is located (network information and load pressure, etc.). After that, the virtual instance directly communicates with the iSCSI target on the same physical node or adjacent physical node, with lower latency and better communication performance, and can reduce dependence on network hardware performance and reduce the preemption of other service network communication performance.
[0062] In an exemplary embodiment, the method also includes: setting the priority of the virtualization instance; setting a physical node load pressure threshold; screening the physical node with the smallest communication delay with the physical node where the standard virtualization instance is located among the physical nodes whose load pressure is less than the load pressure threshold as a backup node; if the load pressure of the physical node where the standard virtualization instance is located is greater than the load pressure threshold, redirecting the iSCSI login request of the management service of the virtualization instance with the lowest priority on the node to the iSCSI target service of the backup node; if the load pressure of the iSCSI target service of the physical node where the standard virtualization instance is located is less than the load pressure threshold and the management services of the virtualization instance on the node are not all on the node, redirecting the login request of the management service of the virtualization instance with the highest priority on the physical node to the iSCSI target service of the physical node.
[0063] For example, a physical node A is mounted with management services of three virtualized instances and the virtualized instances corresponding to the management services, namely virtualized instance a, virtualized instance b, and virtualized instance c. The priorities of the virtualized instances are set to virtualized instance a>virtualized instance b>virtualized instance c, and the load pressure threshold of the physical node is set to x. When the load pressure threshold of the physical node is greater than or equal to x, the iSCSI login request of the management service of the virtualized instance c is redirected to the iSCSI target service of a backup node; if after the redirection, the load pressure of the physical node is still greater than its load pressure threshold x, the management service of the virtualized instance is redirected to the backup node in order from low to high priority. The backup node refers to a physical node with a load pressure less than the load pressure threshold x and the smallest communication delay with the virtualized instance with the highest load pressure among the virtualized instances a, b, and c.
[0064] For another example, a physical node is mounted with three virtualization instances, namely virtualization instance d, virtualization instance e, and virtualization instance f, and the management service of virtualization instance d is also mounted. The priority of virtualization instance e and virtualization instance f is virtualization instance e>virtualization instance f. At this time, if it is detected that the load pressure of the physical node is less than its load pressure threshold, the management service of virtualization instance e will be redirected to the physical node where virtualization instance e is located first; if the physical node still does not reach its load pressure threshold after redirection, the management service of virtualization instance f will be redirected to the physical node.
[0065] In another exemplary embodiment, the method further includes: if the application has multiple virtualization instances, the management service of the virtualization instances other than the standard virtualization instance under the same application is also redirected to the iSCSI target service of the physical node where the standard virtualization instance is located.
[0066] It should also be noted that there are many situations in actual applications that may cause changes in the standard virtualization instance or the login request mount location of the management service of the standard virtualization instance, for example: the request pressure of the iSCSI target service of the physical node changes, causing the load pressure of the physical node to exceed or fall below the threshold, the virtualization instance fails to evacuate or migrate, the physical node where the iSCSI target service is located fails, etc. Therefore, the method also includes periodically traversing all virtualization instances of the same application and redirecting the standard virtualization instance to the iSCSI target service of the physical node where it is located.
[0067] For example, a cluster application includes three virtualization instances, namely virtualization instance g, virtualization instance h, and virtualization instance i, wherein virtualization instance g is mounted to physical node a, virtualization instance h is mounted to physical node b, and virtualization instance i is mounted to physical node c. In one stage, all virtualization instances under the application are traversed, and the virtualization instance g is the virtualization instance with the largest load pressure in the cluster application. Therefore, in this stage, the virtualization instance g is the standard virtualization instance of the application, so the iSCSI login request of the management service of the virtualization instance g is preferentially redirected to the physical node a. Since the virtualization instance g, virtualization instance h, and virtualization instance i belong to different virtualization instances under the same application, the iSCSI login request of the management service of the virtualization instance h and virtualization instance i also needs to be redirected to the physical node a. In another stage, all virtualization instances under the application are traversed, and it is found that the load pressure of the virtualization instance h increases, exceeding the virtualization instance g, and becomes the virtualization instance with the largest load pressure under the application. Therefore, in this stage, the standard virtualization instance of the application is changed to the virtualization instance h. Therefore, in order to use the standard virtualization instance as the affinity object of the iSCSI target service, the iSCSI login request of the management service of the virtualization instance h is redirected from the physical node a to the physical node b. Since the virtualization instance g, the virtualization instance h, and the virtualization instance i belong to different virtualization instances under the same application, the iSCSI login requests of the management services of the virtualization instance g and the virtualization instance i also need to be redirected to the physical node b.
[0068] Please refer to Figure 3 As shown, based on the same inventive concept as the aforementioned virtualization instance management service scheduling method, an embodiment of the present invention provides a virtualization instance management service scheduling system 300, which includes: a scheduling module 301, an acquisition module 302, and a redirection module 303.
[0069] Specifically, the scheduling module 301 is used to schedule the standard virtualization instance in the application to the physical node of the cloud platform; the acquisition module 302 is used to respond to the login request of the virtualization instance management service and obtain the information of the physical node where the standard virtualization instance is located; the redirection module 303 is used to redirect the iSCSI login request to the iSCSI target service of the physical node where the virtualization instance is located based on the information of the physical node where the standard virtualization instance is located.
[0070] It should be noted that the redirection module 303 is also used to set the priority of the virtualization instance; set the load pressure threshold of the physical node; screen the physical node with the smallest communication delay with the physical node where the standard virtualization instance is located among the physical nodes whose load pressure is less than the load pressure threshold as the backup node; when the load pressure of the physical node where the standard virtualization instance is located is greater than the load pressure threshold, redirect the iSCSI login request of the management service of the virtualization instance with the lowest priority on the node to the iSCSI target service of the backup node; when the load pressure of the iSCSI target service of the physical node where the standard virtualization instance is located is less than the load pressure threshold and the management services of the virtualization instance on the node are not all on the node, redirect the login request of the management service of the virtualization instance with the highest priority on the physical node to the iSCSI target service of the physical node.
[0071] The redirection module 303 is also used to redirect the management services of virtualization instances other than the standard virtualization instance under the same application to the iSCSI target service of the physical node where the standard virtualization instance is located; periodically traverse all virtualization instances of the same application and redirect the standard virtualization instance to the iSCSI target service of the physical node where it is located.
[0072] Please refer to Figure 4 As shown, an embodiment of the present invention further provides an electronic device 400, which includes at least one processor 401, a memory 402 (such as a non-volatile memory), a memory 403, and a communication interface 404, and the at least one processor 401, the memory 402, the memory 403, and the communication interface 404 are connected together via a bus 405. At least one processor 401 is used to call at least one program instruction stored or encoded in the memory 402, so that the at least one processor 401 performs various operations and functions of the virtualization instance management service scheduling method described in various embodiments of this specification.
[0073] In an embodiment of the present specification, the electronic device 400 may include, but is not limited to, a personal computer, a server computer, a workstation, a desktop computer, a laptop computer, a notebook computer, a mobile electronic device, a smart phone, a tablet computer, a cellular phone, a personal digital assistant (PDA), a handheld device, a messaging device, a wearable electronic device, a consumer electronic device, and the like.
[0074] An embodiment of the present invention also provides a computer-readable medium, which carries computer execution instructions. When the computer execution instructions are executed by a processor, they can be used to implement various operations and functions of the virtualization instance management service scheduling method described in various embodiments of this specification.
[0075] The computer-readable medium in the present invention can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, a system, device or component of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.
[0076] In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, device, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0077] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0078] The present invention is described with reference to flowcharts and / or block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as a combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0079] The foregoing description of specific exemplary embodiments of the present invention is for the purpose of illustration and demonstration. These descriptions are not intended to limit the present invention to the precise form disclosed, and it is clear that many changes and variations can be made based on the above teachings. The purpose of selecting and describing the exemplary embodiments is to explain the specific principles of the present invention and its practical application, so that those skilled in the art can realize and utilize various different exemplary embodiments of the present invention and various different selections and changes. The scope of the present invention is intended to be limited by the claims and their equivalents.
Claims
1. A virtualization instance management service scheduling method, characterized in that: include: Schedule standard virtualized instances in applications to physical nodes on the cloud platform; In response to an iSCSI login request of the management service of the standard virtualization instance, obtaining information of the physical node where the standard virtualization instance is located; Based on the information of the physical node where the standard virtualization instance is located, the login request is redirected to the iSCSI target service of the physical node.
2. The virtualization instance management service scheduling method according to claim 1, characterized in that: The standard virtualization examples include: If the application has only one virtualized instance, the virtualized instance is a standard virtualized instance; If the application has multiple virtualized instances, the virtualized instance with the greatest load pressure is the standard virtualized instance.
3. The virtualization instance management service scheduling method according to claim 1, characterized in that: The method further comprises: Setting the priority of the virtualized instance; Set the physical node load pressure threshold; A physical node having a load pressure less than the load pressure threshold and having the smallest communication delay with the physical node where the standard virtualization instance is located is selected as a standby node.
4. The virtualization instance management service scheduling method according to claim 3, characterized in that: The method further comprises: If the load pressure of the physical node is greater than the load pressure threshold, redirecting the iSCSI login request of the management service of the virtualized instance with the lowest priority on the node to the iSCSI target service of the standby node; If the load pressure of the iSCSI target service of the physical node is less than the load pressure threshold and the management services of the virtualized instances on the node are not all on the node, the login request of the management service of the virtualized instance with the highest priority on the physical node is redirected to the iSCSI target service of the physical node.
5. The virtualization instance management service scheduling method according to claim 1, characterized in that: The method further comprises: If the application has multiple virtualized instances, the management services of the virtualized instances other than the standard virtualized instance under the same application are also redirected to the iSCSI target service of the physical node where the standard virtualized instance is located.
6. The virtualization instance management service scheduling method according to claim 1, characterized in that: The method further comprises: Periodically traverse all virtualized instances of the same application and redirect standard virtualized instances to the iSCSI target service of the physical node where they are located.
7. The virtualization instance management service scheduling method according to claim 1, characterized in that: The virtualization instance management service is qemu-kvm.
8. A virtualization instance scheduling system, characterized in that: include: The scheduling module is used to schedule standard virtualized instances in applications to physical nodes on the cloud platform; An acquisition module, configured to obtain information of a physical node where the standard virtualization instance is located in response to a login request of a virtualization instance management service; The redirection module is used to redirect the login request to the iSCSI target service of the physical node based on the information of the physical node where the standard virtualization instance is located.
9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the virtualization instance management service scheduling method according to any one of claims 1 to 7 by executing the computer instructions.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the virtualization instance management service scheduling method according to any one of claims 1 to 7.