Method for realizing computing node virtualization based on Open Stack and cloud platform

By scheduling compute nodes according to the virtual machine type and configuring the Libvirt connection address in Open Stack, the existing cloud computing platform lacks the ability of Type1 virtual machines, and high-performance and secure Type1 virtual machine creation is achieved.

CN119806726APending Publication Date: 2025-04-11KYLAND TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411811326.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-12-10
Publication Date
2025-04-11

AI Technical Summary

Technical Problem

The existing cloud computing platform lacks the ability to provide Type1 virtual machines, resulting in the inability to directly access hardware resources, affecting performance and security.

Method used

By implementing the virtualization of computing nodes in Open Stack, the compute nodes are scheduled according to the virtualization type of the virtual machine, and connecting to the hypervisor by configuring the Libvirt connection address of the nova-compute service to create a Type1 virtual machine.

Benefits of technology

It realizes the creation of a real-time virtual machine with Type1 virtualization on the Open Stack platform, improving the real-time and performance of the virtual machine.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119806726A_ABST
    Figure CN119806726A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a method for realizing computing node virtualization based on OpenStack and a cloud platform, and the method comprises the steps: installing a nova-complex service on a first computing node, and configuring an interface address corresponding to a Libvirt connection address of the nova-complex according to the virtualization type of the first computing node; the control node dispatches a second computing node for the to-be-created virtual machine and sends a request for creating the virtual machine to a nova-complex service of the second computing node, and the second computing node is a first computing node meeting the virtualization type of the to-be-created virtual machine; and creating the virtual machine to be created through a Libvirt interface which is connected with the Libvirt connection address of the nova-component of the second computing node by the nova-component service of the second computing node. According to the technical scheme, the computing node meeting the requirement is scheduled according to the virtualization type of the virtual machine, the scheduled computing node creates the virtual machine through the interface connected with the Libvirt connection address of the nova-complex configured according to the virtualization type of the computing node, and therefore creation of the type1 virtual machine is achieved through OpenStack.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of operating system technology, and in particular to a method and a cloud platform for implementing computing node virtualization without Open Stack. Background Art

[0002] Type 1 virtualization: runs directly on physical hardware and does not rely on the host operating system. This type of virtualization can directly access hardware resources and provide higher performance and security. Type 2 virtualization: runs on the host operating system and exists as an application. This type of virtualization cannot directly access hardware resources, but allocates resources through the host operating system.

[0003] Cloud computing is an Internet-based computing method that provides dynamic and scalable IT resources and services through the network. Currently, both public and private clouds provide Type 2 virtual machines, and neither provides Type 1 virtual machines. There is a lack of cloud platforms that provide Type 1 virtual machines in the current market. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a method and cloud platform for implementing computing node virtualization based on Open Stack, scheduling computing nodes that meet the requirements according to the virtualization type of the virtual machine, and the scheduled computing nodes create virtual machines through interfaces connected to the Libvirt connection address of nova-compute configured according to their virtualization type, thereby implementing type 1 virtual machine creation through Open Stack.

[0005] In a first aspect, an embodiment of the present application provides a method for implementing computing node virtualization based on Open Stack, including: installing a nova-compute service on a first computing node, and configuring an interface address corresponding to the Libvirt connection address of the nova-compute according to the virtualization type of the first computing node; a control node schedules a second computing node for the virtual machine to be created, and sends a request to create a virtual machine to the nova-compute service of the second computing node, the second computing node being the first computing node that meets the virtualization type of the virtual machine to be created; the nova-compute service of the second computing node creates the virtual machine to be created through the Libvirt interface connected to the Libvirt connection address of the nova-compute of the second computing node.

[0006] As described above, computing nodes that meet the requirements are scheduled according to the virtualization type of the virtual machine. The scheduled computing nodes create virtual machines through interfaces connected to the Libvirt connection addresses of nova-compute configured according to their virtualization types, thereby creating real-time virtual machines based on type1 virtualization on computing nodes with type1 virtualization through Open Stack, thereby improving the real-time performance of real-time virtual machines.

[0007] In a possible implementation of the first aspect, when the first computing node is a type 1 virtualization type, the Libvirt connection address of nova-compute of the first computing node is configured as the libvirt interface address of the hypervisor of the first computing node; the hypervisor of the first computing node encapsulates an open libvirt standard interface. The interface encapsulates a virtual machine management component of the hypervisor.

[0008] From the above, by configuring the Libvirt connection address of the nova-compute service of the first computing node to be the libvirt interface address of the hypervisor of the first computing node, the nova-compute service is connected to the hypervisor of the computing node in the type 1 virtualized computing node, so as to directly create a type 1 virtual machine using the standard libvirt developed by the hypervisor encapsulation.

[0009] In a possible implementation of the first aspect, after the nova-compute service is installed on the first virtual machine of the first computing node and before the first computing node is scheduled, it also includes: the nova-compute service of the first computing node configures the virtualization type of the first computing node and registers the virtualization type of the first computing node with the control node.

[0010] As described above, by configuring the virtualization type of the computing node in the nova-compute service of the type1 virtualized computing node and registering the virtualization type of the first computing node in the control node, the computing node is scheduled to the type1 virtualized virtual machine.

[0011] In a possible implementation of the first aspect, after the nova-compute service is installed on the first virtual machine of the first computing node and before the first computing node is scheduled, it also includes: the nova-compute service of each first computing node configures the image directory of the virtual machine according to the virtualization type of the first computing node, wherein when the first computing node is a virtualization type of type1, the image directory of the virtual machine of the first computing node is the image path directory of the hypervisor of the first computing node.

[0012] As described above, by specifying the image directory of the virtual machine on the type1 virtualization node as the image path directory of the hypervisor of the first computing node, the hypervisor obtains the image of the virtual machine from its image path directory.

[0013] In a possible implementation of the first aspect, after the second computing node is scheduled and before the nova-compute service of the second computing node creates the virtual machine to be created, it also includes: when the second computing node is a virtualization type of type 1, the nova-compute service of the second computing node obtains the network card MAC address of the virtual machine to be created from Neutron and sends it to the hypervisor of the second computing node.

[0014] As described above, the MAC address of the network card of the virtual machine to be created obtained from Neutron by the nova-compute service of the scheduled computing node is sent to the hypervisor of the computing node, so that the Type 1 virtual machine network card created in the hypervisor can obtain the correct IP address through the DHCP network service provided by the platform.

[0015] In a possible implementation manner of the first aspect, the control node schedules the second computing node according to the virtualization type of the virtual machine to be created through a filter based on the virtualization type.

[0016] As described above, the virtualization type scheduling computing node of the virtual machine to be created is selected by the filter based on the virtualization type, so as to schedule the type1 virtualized virtual machine to the typ1 virtualized computing node, thereby realizing the creation of the type1 virtualized virtual machine.

[0017] In a possible implementation manner of the first aspect, before the control node schedules the virtual machine to be created, the method further includes: uploading the virtual machine image to be created to the control node and specifying a virtualization type.

[0018] As described above, when uploading the virtual machine image to be created to the control node, the virtualization type is specified, so that the type1 virtualized virtual machine can be scheduled to the typ1 virtualized computing node, thereby realizing the creation of the type1 virtualized virtual machine.

[0019] In the second aspect, an embodiment of the present application provides a cloud platform for implementing virtualization of computing nodes based on Open Stack, including: a control node and a computing node; each control node includes a node scheduling module, which is used to schedule a computing node that meets the virtualization type requirements for the virtual machine to be created, and send a request to create a virtual machine to the nova-compute service of the computing node; each computing node includes a Nova startup module, which is used to install the nova-compute service on the computing node, and configure the interface address corresponding to the Libvirt connection address of the nova-compute according to the virtualization type of the computing node; each computing node also includes a virtual machine creation module, which is used to call the nova-compute service of the computing node when the computing node is scheduled by the control node to create the virtual machine to be created through the Libvirt interface connected to the Libvirt connection address of the nova-compute service of the computing node.

[0020] As described above, the computing nodes that meet the requirements are scheduled according to the virtualization type of the virtual machine. The scheduled computing nodes create virtual machines through the Libvirt connection address of nova-compute configured according to their virtualization type, so that real-time virtual machines based on type1 virtualization are created on type1 virtualized computing nodes through OpenStack, thereby improving the real-time performance of real-time virtual machines.

[0021] In a possible implementation of the second aspect, when the first computing node is a virtualization type of type 1, the Libvirt connection address of the nova-compute service of the first computing node is the libvirt interface address of the hypervisor of the first computing node; the hypervisor of the first computing node encapsulates an open libvirt standard interface, wherein the first computing node is any computing node. The interface encapsulates the virtual machine management of the hypervisor.

[0022] From the above, by configuring the Libvirt connection address of the nova-compute service of the first computing node to be the libvirt interface address of the hypervisor of the first computing node, the nova-compute service is connected to the hypervisor of the computing node in the type 1 virtualized computing node, so as to directly create a type 1 virtual machine using the standard libvirt developed by the hypervisor encapsulation.

[0023] In a possible implementation of the second aspect, the Nova startup module of each computing node is also used to configure the virtualization type of the first computing node by the nova-compute service of the computing node after the nova-compute service is installed on the first virtual machine of the computing node and before the computing node is scheduled, and register the virtualization type of the computing node with the control node.

[0024] As described above, by configuring the virtualization type of the computing node in the nova-compute service of the computing node of type1 virtualization and registering the virtualization type of the computing node in the control node, the computing node is scheduled to the virtual machine of type1 virtualization.

[0025] In a possible implementation of the second aspect, the Nova startup module of each computing node is also used to configure the image directory of the virtual machine by the nova-compute service of each computing node according to the virtualization type of the computing node after the nova-compute service is installed on the first virtual machine of the computing node and before the computing node is scheduled, wherein when the computing node is a virtualization type of type1, the image directory of the virtual machine of the computing node is the image path directory of the hypervisor of the computing node.

[0026] As described above, by specifying the image directory of the virtual machine virtualized by type 1 on the computing node as the image path directory of the hypervisor of the computing node, the hypervisor obtains the image of the virtual machine from its image path directory.

[0027] In a possible implementation of the second aspect, the Nova startup module of each computing node is also used to send the network card MAC address of the virtual machine to be created obtained from Neutron by the nova-compute service of the computing node to the hypervisor of the computing node after the computing node is scheduled and before the nova-compute service of the computing node creates the virtual machine to be created.

[0028] As described above, the MAC address of the network card of the virtual machine to be created obtained from Neutron by the nova-compute service of the scheduled computing node is sent to the hypervisor of the computing node, so that the Type 1 virtual machine network card created in the hypervisor can obtain the correct IP address through the DHCP network service provided by the platform.

[0029] In a possible implementation of the second aspect, the node scheduling module of the control node is specifically configured to schedule the second computing node according to the virtualization type of the virtual machine to be created through a filter based on the virtualization type by the control node.

[0030] As described above, the virtualization type scheduling computing node of the virtual machine to be created is selected by the filter based on the virtualization type, so as to schedule the type1 virtualized virtual machine to the typ1 virtualized computing node, thereby realizing the creation of the type1 virtualized virtual machine.

[0031] In a possible implementation manner of the second aspect, before the control node schedules the virtual machine to be created, it also includes: an image uploading module, which is used for the client to upload the virtual machine image to be created to the control node and specify the virtualization type.

[0032] As described above, when the client uploads the virtual machine image to be created to the control node, the virtualization type is specified, so that the type1 virtualized virtual machine is scheduled to the typ1 virtualized computing node, thereby realizing the creation of the type1 virtualized virtual machine. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 This is a flow chart of a method for implementing computing node virtualization based on Open Stack in the present application;

[0034] Figure 2 A schematic diagram of the structure of a type 1 virtualized computing node in Embodiment 2 of a method for implementing computing node virtualization based on Open Stack of the present application;

[0035] Figure 3 This is a flow chart of Embodiment 2 of a method for implementing computing node virtualization based on Open Stack of the present application;

[0036] Figure 4 This is a flow chart of step S340 of Embodiment 2 of a method for implementing computing node virtualization based on Open Stack of the present application;

[0037] Figure 5 A schematic diagram of the structure of a cloud platform embodiment of the present application. DETAILED DESCRIPTION

[0038] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0039] In the following description, the terms "first\second\third, etc." or module A, module B, module C, etc. are only used to distinguish similar objects, or to distinguish different embodiments, and do not represent a specific ordering of the objects. It can be understood that the specific order or sequence can be interchanged where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0040] In the following description, the numbers representing the steps, such as S110, S120, etc., do not necessarily mean that the steps must be executed in this manner. If permitted, the order of the previous and next steps can be interchanged, or they can be executed simultaneously.

[0041] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0042] An embodiment of the present application provides a method and a cloud platform for implementing computing node virtualization based on Open Stack. The cloud platform implements computing node virtualization based on Open Stack. The method includes: installing a nova-compute service on a first computing node, and configuring a Libvirt connection address of the nova-compute service according to a virtualization type of the first computing node; a control node schedules a second computing node for a virtual machine to be created, and sends a request to create a virtual machine to the nova-compute service of the second computing node, where the second computing node is the first computing node that meets the virtualization type of the virtual machine to be created; and the nova-compute service of the second computing node creates the virtual machine to be created through a Libvirt interface connected to the Libvirt connection address of the nova-compute service of the second computing node.

[0043] The technical solution of the present application schedules a computing node that meets the requirements according to the virtualization type of the virtual machine. The scheduled computing node creates a virtual machine through the Libvirt connection address of the nova-compute service configured according to its virtualization type, thereby realizing type 1 virtual machine creation through Open Stack.

[0044] The following describes various embodiments of the present application in conjunction with the accompanying drawings. Figure 1 A method for implementing computing node virtualization based on OpenStack is introduced in the present application.

[0045] Figure 1 The flowchart of a method for implementing computing node virtualization based on Open Stack is shown, and includes steps S110 to S130.

[0046] S110: Install the nova-compute service on the first computing node, and configure the interface address corresponding to the Libvirt connection address of the nova-compute service according to the virtualization type of the first computing node.

[0047] Among them, when the virtualization type of the first computing node is type1, a first virtual machine is installed on the hypervisor of the first computing node, and the nova-compute service is installed and started on the first virtual machine; when the virtualization type of the first computing node is type2, a first virtual machine is installed on the host operating system of the first computing node, and the nova-compute service is installed and started on the first virtual machine.

[0048] In some embodiments, when the first computing node is of type 1 virtualization type, the Libvirt connection address of the nova-compute service of the first computing node is configured to be the libvirt interface address of the hypervisor of the first computing node, that is, the corresponding interface address is the libvirt interface address of the hypervisor of the first computing node. The process is implemented by a newly added custom driver of the nova-compute service. The open libvirt standard interface is encapsulated in the hypervisor of the first computing node, and the interface is used to encapsulate the virtual machine management of the hypervisor. When the first computing node is of type 2 virtualization type, the Libvirt connection address of the nova-compute service of the first computing node is the default libvirt interface address of nova-compute, that is, the corresponding interface address is the default libvirt interface address of nova-compute.

[0049] In some embodiments, after the nova-compute service is installed on the first virtual machine of the first computing node and before the first computing node is scheduled, it also includes: the nova-compute service of each first computing node configures the image directory of the virtual machine according to the virtualization type of the first computing node, wherein, when the first computing node is a virtualization type of type1, the image directory of the virtual machine of the first computing node is the image path directory of the hypervisor of the first computing node, and the process is implemented by a custom driver newly added by the nova-compute service. When the first computing node is a virtualization type of type2, the image directory of the virtual machine of the first computing node is the default directory of the image path of the host operating system where the virtual machine is located.

[0050] In some embodiments, after the nova-compute service is installed on the first virtual machine of the first computing node and before the first computing node is scheduled, the process further includes: the nova-compute service of the first computing node configures the virtualization type of the first computing node and registers the virtualization type of the first computing node with the control node. The process is implemented by a new module in the manager of the nova-compute service, which configures the virtualization type attribute of the computing node and configures the nova-compute service driver type according to the virtualization type of the computing node.

[0051] S120: The control node schedules a second computing node for the virtual machine to be created, and sends a request to create the virtual machine to the nova-compute service of the second computing node.

[0052] The second computing node is a first computing node that meets the virtualization type of the virtual machine to be created, and the control node is a control node of Open Stack.

[0053] In some embodiments, the control node schedules the second computing node according to the virtualization type of the virtual machine to be created through a filter based on the virtualization type, so that the real-time virtual machine is allocated to the computing node that supports type1 virtualization to improve the real-time performance of the real-time virtual machine, wherein the filter based on the virtualization type is implemented by adding a new customized filter.

[0054] In some embodiments, after the second computing node is scheduled and before the nova-compute service of the second computing node creates the virtual machine to be created, it also includes: when the second computing node is a type 1 virtualization type, the nova-compute service of the second computing node obtains the network card MAC address of the virtual machine to be created from Neutron and sends it to the hypervisor of the second computing node, so that the created Type 1 virtual machine network card can obtain the correct IP address through the DHCP network service provided by the platform, wherein the process is implemented by a custom driver newly added by the nova-compute service.

[0055] In some embodiments, before the control node schedules the virtual machine to be created, it also includes: uploading the virtual machine image to be created to the control node, and specifying the virtualization type of the virtual machine image, so as to schedule a computing node that meets the virtualization type according to the virtualization type of the virtual machine image, and the real-time virtual machine is allocated to the computing node that supports type1 virtualization to improve the real-time performance of the real-time virtual machine.

[0056] S130: The nova-compute service of the second computing node creates the virtual machine to be created through the Libvirt interface connected to the Libvirt connection address of the nova-compute of the second computing node.

[0057] The nova-compute service of the second computing node downloads the image of the virtual machine to be created to the image address corresponding to the virtualization type of the second computing node, and then creates it. When the second computing node is a type1 virtualization type, the image of the virtual machine to be created is downloaded to the image address of the hypervisor of the second computing node. When the second computing node is a type2 virtualization type, the image of the virtual machine to be created is downloaded to the default image address of the nova-compute service of the host operating system of the second computing node.

[0058] When the second computing node is of type 1 virtualization type, the nova-compute service of the second computing node creates a virtual machine through the Libvirt standard interface developed by the hypervisor encapsulation of the second computing node. When the second computing node is of type 2 virtualization type, the nova-compute service of the second computing node creates a virtual machine through the default Libvirt interface of the nova-compute service of the second computing node.

[0059] In summary, a method for implementing computing node virtualization based on Open Stack, embodiment 1, schedules computing nodes that meet the requirements according to the virtualization type of the virtual machine, and the scheduled computing nodes create virtual machines through the Libvirt connection address of nova-compute configured according to their virtualization types, thereby creating real-time virtual machines based on type1 virtualization on type1 virtualized computing nodes through Open Stack, thereby improving the real-time performance of real-time virtual machines.

[0060] Combine the following Figures 2 to 4 A second embodiment of a method for implementing computing node virtualization based on Open Stack of the present application is introduced.

[0061] A method for implementing computing node virtualization based on Open Stack Example 2 is a detailed implementation method of Example 1 of the method for implementing computing node virtualization based on OpenStack, which has all its advantages and adds a customized modification method of its Nova source code.

[0062] For simplicity of description, a computing node based on type 1 virtualization is directly taken as an example to first introduce a computing node based on type 1 virtualization.

[0063] Figure 2 The structure of a type 1 virtualized computing node in Embodiment 2 of a method for implementing computing node virtualization based on Open Stack is shown, which includes: a hardware resource layer 230 , a hypervisor layer 220 , and a nova-compute service layer 210 .

[0064] The hardware resource layer 230 includes: various hardware resources such as the physical CPU, memory mem, and hard disk of the target machine.

[0065] The hypervisor layer 220 includes a type 1 hypervisor and an open Libvirt standard interface (called a hypervisor Libvirt interface) encapsulated by the hypervisor, which encapsulates the virtual machine management of the hypervisor. The type 1 virtualized hypervisor provides hardware resources for each virtual machine on it, and the hypervisor Libvirt interface is called by the nova-compute service layer 210 to create a virtual machine.

[0066] The nova-compute service layer 210 runs the nova-compute service. The OpenStack control node creates a virtual machine through the nova-compute service on the computing node. The driver of the nova-compute service on the type1 virtualized computing node is the type1 libvert driver. This driver is a newly added customized driver, not the default driver (libvert driver) that comes with nova-compute, and is implemented by modifying the Nova source code.

[0067] Figure 3 A process of a second embodiment of a method for implementing computing node virtualization based on Open Stack is shown, which includes steps S310 to S340.

[0068] S310: Modify the Nova source code and add the customized driver type1 libvert driver of nova-compute, the virtualization type attribute virtul_type of the computing node, and the filter virtul_type_filter based on the virtualization type of the control node.

[0069] Among them, this step includes the following sub-steps.

[0070] 1) Add a new directory under nova / virt / in the Nova source code, and add the type1libvirtdriver code to the directory. type1libvirtdriver is used to drive the compute nodes of type1 virtualization to achieve the following functions.

[0071] The original driver in the Nova source code is LibvirtDriver, which is used for the nova-compute service of type2 virtualized computing nodes and type1libvirtdriver of type1 virtualized computing nodes to implement the following functions.

[0072] (1) The libvirt interface connection address in the nova.conf file of the nova-compute service of the computing node is the libvirt interface address of the hypervisor of the type 1 virtualized computing node. The hypervisor's libvirt interface encapsulates the hypervisor's virtual machine management functions. Virtual machine management includes life cycle management functions such as virtual machine creation, virtual machine startup, virtual machine monitoring, virtual machine pause, virtual machine stop, and virtual machine deletion.

[0073] The nova-compute service of the computing node uses the Libvirt SDK to connect to the hypervisor of the computing node through the connection address, so that Nova-compute calls the hypervisor to perform lifecycle management of the type 1 virtual machine.

[0074] The Libvirt interface connection address in nova.conf is the libvirt interface address of the Nova source code corresponding to the operating system run by the nova-compute service before it is modified.

[0075] (2) Modify the storage path of the virtual machine image downloaded by the computing node of type 1 virtualization to the path address of the hypervisor image of the computing node.

[0076] The virtual machine image address downloaded by the nova-compute service of the computing node is the image address in the Nova source code corresponding to the host operating system where the nova-compute service is located before modification, which is different from the path address of the hypervisor image.

[0077] (3) The MAC address information of the network card of the virtual machine to be created on the type 1 virtualized computing node obtained from Neutron is sent to the hypervisor of the computing node through the interface connection address of Libvirt, so that when the Type 1 virtual machine network card is created by the hypervisor, the correct IP address can be obtained through the DHCP network service provided by the platform.

[0078] 2) Add the virtualization type attribute virtul_type of the compute node in the nova / compute / manager code of the Nova source code, and determine the driver type of the nova-compute service of the compute node.

[0079] When virtul_type is 1, it indicates that the driver of the nova-compute service of the computing node is type1LibvirtDriver, which is the newly added customized driver nova-compute service driver; when virtul_type is 2, it indicates that the driver of the nova-compute service of the computing node is libvirtdriver, which is the default driver of the nova-compute service.

[0080] 3) Add the virtualization type-based filter virtul_type_filter in the nova / scheduler / filters / directory of the Nova source code.

[0081] Among them, for the virtual machine of the image virtualization type attribute virtul_type=1, the virtul_type_filter is scheduled to the computing node whose computing node virtualization tag type virtul_type is 1, so as to deploy the real-time virtual machine on the computing node of type1 virtualization.

[0082] S320: Upload the real-time operating system virtual machine RTOS image to the control node, and specify the image virtualization type virtul_type=1.

[0083] The virtual machine images are stored in the control node according to the virtualization type virtul_type, and the computing nodes are also distinguished according to the virtualization type virtul_type. The real-time operating system virtual machine RTOS is the operating system of the real-time virtual machine.

[0084] S330: Preinstall a Linux virtual machine on the type 1 virtualized computing node, install the nova-compute service on the virtual machine, configure its driver, and start the nova-compute service to connect it to the hypervisor of the computing node.

[0085] The driver of the type1 virtualized computing node is configured as type1libvirtdriver in nova.conf, that is, compute_driver of nova-compute = type1libvirtdriver.

[0086] After starting the nova-compute service on the computer node, the nova-compute service also registers the computing node with the control node, and indicates its virtualization type virtul_type in the registration information to facilitate the scheduling of the control node.

[0087] S340: The control node schedules a type 1 virtualized computing node for the type 1 virtualized virtual machine, and creates a virtual machine through the nova-compute service on the scheduled computing node.

[0088] in, Figure 4 The detailed process of this step is shown, including steps S410 to S460.

[0089] S410: receiving a client request nova-api to create a virtual machine of the RTOS operating system.

[0090] Among them, the virtualization type of the RTOS is type1 virtualization type.

[0091] S420: nova-api creates a type 1 virtual machine record in the database and sends a request to nova-scheduler through RPC.

[0092] Among them, nova-scheduler is the scheduler of the control node, which includes a customized virtual_type_filter based on the virtualization type virtual_type

[0093] S430: nova-scheduler filters through the virtual_type_filter filter and returns the available type 1 computing nodes to nova-conductor.

[0094] The virtual_type_filter filter filters out the scheduled computing nodes from the type 1 computing nodes.

[0095] S440: nova-conductor sends a request to create a virtual machine to the scheduled type 1 computing node nova-compute service through RPC.

[0096] S450: The nova-compute service calls the hypervisor of the compute node through the type1LibvirtDriver driver to create a Type1 virtual machine.

[0097] The nova-compute service also requests the glance-api to download the virtual machine image through HTTP.

[0098] S460: After receiving the hypervisor creation result, the nova-compute service calls nova-conductor through the RPC interface to update the virtual machine information to the database.

[0099] Among them, step S460 is Figure 4 The process includes S460-1: the nova-compute service receives the hypervisor creation result, S460-2: feedbacks the creation result to nova-conductor through the RPC interface, and S460-3: nova-conductor updates the virtual machine information to the database.

[0100] Among them, step S410 is executed on the client of the cloud platform based on Open Stack, steps S420 to S440 and S460-3 are executed on the control node of the cloud platform based on Open Stack, and steps S450 to S460-2 are executed on the computing node.

[0101] In summary, a method for implementing computing node virtualization based on Open Stack in Example 2 modifies the Nova source code, adds a customized driver type1 libvert driver of nova-compute, a virtualization type attribute virtul_type of the computing node, and a filter virtul_type_filter based on the virtualization type of the control node, and the Libvirt connection address of nova-compute configured by type1libvertdriver on the computing node of type1 is the Libvirt interface address of the hypervisor, and the computing node of type1 is scheduled for the virtual machine of type1. The scheduled computing node connects to the hypervisor through the Libvirt connection address of nova-compute, and creates a virtual machine through the hypervisor, thereby implementing the creation of the virtual machine of type1 through Open Stack.

[0102] Combine the following Figure 5 A cloud platform embodiment of the present application is introduced.

[0103] A cloud platform embodiment runs a method for implementing computing node virtualization based on Open Stack. The method described in embodiment 1 has all its advantages.

[0104] Figure 5 The structure of a cloud platform embodiment is shown, which includes: a control node 510 and several computing nodes 520, each computing node 520 includes a Nova startup module 5210 and a virtual machine creation module 5230, and the control node 510 includes a node scheduling module 5120.

[0105] The node scheduling module 5120 of the control node 510 is used for the control node 510 to schedule a computing node 520 that meets the virtualization type of the virtual machine to be created for the virtual machine to be created, and send a request to create a virtual machine to the nova-compute service of the computing node 520. For its method and advantages, please refer to step S120 of the first embodiment of a method for realizing computing node virtualization based on Open Stack.

[0106] The Nova startup module 5210 of each computing node 520 is used to install the nova-compute service on the computing node 520, and configure the interface address corresponding to the Libvirt connection address of the nova-compute service according to the virtualization type of the computing node 520. For its method and advantages, please refer to step S110 of the first embodiment of a method for realizing computing node virtualization based on Open Stack.

[0107] The virtual machine creation module 5230 of each computing node 520 is used to create the virtual machine to be created by the nova-compute service of the computing node 520 through the Libvirt interface connected to the Libvirt connection address of the nova-compute of the computing node 520. For its method and advantages, please refer to step S130 of the first embodiment of a method for realizing computing node virtualization based on Open Stack.

[0108] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may also include more other equivalent embodiments without departing from the concept of the present application, all of which belong to the scope of protection of the present application.

Claims

1. A method for implementing computing node virtualization based on Open Stack, characterized in that: include: Install the nova-compute service on the first computing node, and configure the interface address corresponding to the Libvirt connection address of the nova-compute according to the virtualization type of the first computing node; The control node schedules a second computing node for the virtual machine to be created, and sends a request to create the virtual machine to the nova-compute service of the second computing node, where the second computing node is the first computing node that meets the virtualization type of the virtual machine to be created; The nova-compute service of the second computing node creates the virtual machine to be created through the Libvirt interface connected to the Libvirt connection address of the nova-compute of the second computing node.

2. The method according to claim 1, characterized in that: When the first computing node is of type 1 virtualization type, the Li bv irt connection address of nova-compute of the first computing node is configured as the libvirt interface address of the hypervisor of the first computing node.

3. The method according to claim 1, characterized in that: After the nova-compute service is installed on the first virtual machine of the first computing node and before the first computing node is scheduled, the method further includes: The nova-compute service of the first computing node configures a virtualization type of the first computing node and registers the virtualization type of the first computing node with the control node.

4. The method according to claim 1, characterized in that: After the nova-compute service is installed on the first virtual machine of the first computing node and before the first computing node is scheduled, the method further includes: The nova-compute service of each first computing node configures the image directory of the virtual machine according to the virtualization type of the first computing node, wherein, when the first computing node is a virtualization type of type1, the image directory of the virtual machine of the first computing node is the image path directory of the hypervisor of the first computing node.

5. The method according to claim 1, characterized in that: After the second computing node is scheduled and before the nova-compute service of the second computing node creates the virtual machine to be created, the method further includes: When the second computing node is of type 1 virtualization type, the nova-compute service of the second computing node sends the network card MAC address of the virtual machine to be created obtained from Neutron to the hypervisor of the second computing node.

6. The method according to claim 1, characterized in that: The control node schedules the second computing node according to the virtualization type of the virtual machine to be created through a filter based on the virtualization type.

7. The method according to claim 1, characterized in that: Before the control node schedules the virtual machine to be created, the process further includes: Upload the virtual machine image to be created to the control node and specify the virtualization type.

8. A cloud platform, characterized in that: Used to implement virtualization of computing nodes based on Open Stack, including control nodes and computing nodes; Each control node includes a node scheduling module, which is used to schedule a computing node that meets the virtualization type requirements for the virtual machine to be created, and send a request to create the virtual machine to the nova-compute service of the computing node; Each computing node includes a Nova startup module, which is used to install the nova-compute service on the computing node and configure the interface address corresponding to the Li bv irt connection address of the nova-compute according to the virtualization type of the computing node; Each computing node also includes a virtual machine creation module, which is used to call the nova-compute service of the computing node to create the virtual machine to be created through the Libvirt interface connected to the Libvirt connection address of the nova-compute service of the computing node when the computing node is scheduled by the control node.

9. The cloud platform according to claim 8, characterized in that: When the computing node is of type 1 virtualization type, the Li bv irt connection address of nova-compute of the computing node is the libvirt interface address of the hypervisor of the first computing node.

10. The cloud platform according to claim 8, characterized in that: The Nova startup module of each computing node is also used to configure the virtualization type of the first computing node by the nova-compute service of the computing node after the nova-compute service is installed on the first virtual machine of the computing node and before the computing node is scheduled, and register the virtualization type of the first computing node with the control node.