Virtualized cloud host management method based on kubevirt

Through the virtualized cloud host management method based on kubevirt, a unified virtual machine management platform is set up, commercial software is migrated to open source software, and machine application process automation and seamless migration of virtual machines are realized, solving the technical complexity of the virtualization platform and the high operation and maintenance cost of the virtualization platform The problem of this problem reduces operation and maintenance costs and simplifies management processes.

CN119025221APending Publication Date: 2024-11-26BEIJING BITE YIPAI INFORMATION TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411224070.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-02
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In the existing technology, the virtualization platform technology is complex, which increases the operation and maintenance costs of enterprises. In the process of technological transformation, historical services are difficult to quickly containerize, and two sets of infrastructure platforms are required, which increases the technical complexity and cost. .

Method used

Adopt a virtualized cloud host management method based on kubevirt, set up a unified virtual machine management platform, migrate commercial software to open source software, realize machine application process automation, use distributed block storage and vm-import-operate, and support virtual machine templates and area selection , unified use of open source K8S base to reduce operation and maintenance costs and achieve seamless migration of virtual machines.

Benefits of technology

Through a unified technical architecture and automated process, the operation and maintenance costs are reduced, the management of virtualization and containerized platforms is simplified, deployment efficiency and flexibility are improved, and technical complexity is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025221A_ABST
    Figure CN119025221A_ABST
Patent Text Reader

Abstract

The invention discloses a virtual cloud host management method based on kubevirt. The virtual cloud host management method based on kubevirt comprises the following steps: 1, setting a virtual machine management unified platform; 2, migrating commercial software to open source software; 3, setting to realize automation of a machine application process; 4, providing a mirror image client; 5, setting snamrtclone, and using the distributed block storage to the snamrtclone; 6, the vm-impart-operator uses a virtual machine template problem and supports zone selection, through the technical scheme, a virtual machine management unified platform is arranged to unify the technical architecture and reduce the operation and maintenance cost, meanwhile, commercial software is migrated to open source software, and further, a work order system is opened, automation of a machine application process is achieved, a migration system is arranged to seamlessly migrate a virtual machine managed by vmware to kubevirt, and the operation and maintenance efficiency is improved. Therefore, the cost is reduced, and further, the problem of slow creation is solved by using snamrtclone and distributed block storage.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of virtualized cloud host management, and in particular to a virtualized cloud host management method based on kubevirt. Background Art

[0002] Cloud computing technology has entered a mature stage. Enterprises have higher requirements for the deployment efficiency and flexibility of application services. Traditional PaaS solutions can no longer meet current needs. Containerization and its lightweight, second-level deployment of cloud-native solutions have attracted more attention. However, in the process of this technological transformation, it is inevitable that some historical services cannot be quickly containerized. Traditional virtual machines and containerization need to coexist to provide infrastructure services for the business.

[0003] This led to new problems. The technical team needed to maintain two infrastructure platforms, virtualization and containerization. The automation systems within the enterprise needed to adapt to both platforms, which undoubtedly increased the technical complexity. Unified management of virtualization became an urgent problem to be solved.

[0004] That is, the existing technology has the following technical problems: the common virtualization platform technology is difficult and complex, which increases the enterprise expenditure. Therefore, in order to solve the above problems, a virtualization cloud host management method based on kubevirt is proposed. Summary of the invention

[0005] In this embodiment, a virtualized cloud host management method based on kubevirt is provided to solve the problem that the common virtualization platform technology in the prior art is complex and difficult, and increases the expenditure of the enterprise.

[0006] According to one aspect of the present application, a virtualized cloud host management method based on kubevirt is provided, and the virtualized cloud host management method based on kubevirt comprises the following steps:

[0007] 1. Set up a unified platform for virtual machine management;

[0008] 2. Migrate commercial software to open source software;

[0009] 3. Set up and automate the machine application process;

[0010] 4. Provide mirror client;

[0011] 5. Set snamrtclone to use distributed block storage;

[0012] 6. Issues with vm-import-operate using virtual machine template and supporting zone selection.

[0013] Furthermore, in step 1, a unified virtual machine management platform is set up to unify the technical architecture, reduce operation and maintenance costs, and uniformly adopt the open source K8S base.

[0014] Furthermore, the open source K8S base version is v1.20, the operating system version is centos75.4 kernel, and the use of 5.4 kernel requires the kernel to support the new ceph snapshot feature.

[0015] Furthermore, in step 2, a migration system is set up to seamlessly migrate the virtual machines managed by vmware to kubevirt, thereby reducing costs.

[0016] Furthermore, the migration system is implemented based on vm-v2v technology, providing a user operation interface and back-end application that can configure the migration of any virtual machine managed by VMware. The migration system includes automatic synchronization migration of network settings, system image configuration, CPU, memory and other configurations to ensure that the IP address remains unchanged after migration, and automatic retry of migration errors and other functions.

[0017] Furthermore, in step 3, the work order system is connected to automate the machine application process, and an automated virtual machine creation process is set, wherein the automated virtual machine creation process includes virtual machine form information.

[0018] Furthermore, the virtual machine form information includes information such as computer room, purpose, business line, team, subnet, virtual machine package, quantity, etc., completes the virtual machine automatic creation configuration and completes the virtual machine initialization operation (using slat), including the necessary monitoring agent, security agent, kernel version, security baseline and other related configurations. The initial configuration of the virtual machine uses cloud-int to inject a read-only disk into the virtual machine, and reads the necessary information to complete initial operations such as user creation, disk formatting, and IP configuration. Windows and Linux use a unified technology solution.

[0019] Furthermore, in step 4, when the ceph-csi method creates a pvc problem, the image client cannot correspond to the current ceph version, and the image version is incompatible with the current ceph version, resulting in the inability to create pvc, and the image needs to be remade.

[0020] Furthermore, in step 5, snamrtclone is used to use distributed block storage. When creating a system image based on block storage, the csi mechanism will flatten the pvc, resulting in slow creation. First, a pvc is created under the image namespace. This pvc is created through an image snapshot, and then a tb resource is created to pass the image to the namespace where the virtual machine needs to be created, and then the virtual machine is created through this pvc.

[0021] Furthermore, in step 6, the template needs to configure the vm-config configuration to skip template rendering. To support zone selection, the source code needs to be modified to add the spec field and processing logic. After modification, it is recompiled according to the makefile and deployed to the K8S cluster. The compilation process and dependency resolution process are not described in detail. Only the core code modification part is introduced. At the same time, the migration program is required to specially handle this field as the label of the zone value specified for the migration virtual machine so as to create it in the specified area.

[0022] Code path: pkg / apis / v2v / v1beta1 / virtualmachineimport_types.go

[0023] BeforeEach(func(){

[0024] findTemplate=func()(*oapiv1.Template,error){

[0025] return&oapiv1.Template{},nil

[0026] }

[0027] processTemplate=func(template*oapiv1.Template,name*string,namespacestring)(*kubevirtv1.VirtualMachine,error){

[0028] return&kubevirtv1.VirtualMachine{},nil

[0029] }

[0030] mapper = &mockMapper{}

[0031] targetName:="test"

[0032] zone:="zone0"

[0033] instance.Spec.TargetVMName=&targetName

[0034] instance.Spec.Zone = &zone

[0035] }).

[0036] Through the above technical solutions, a unified virtual machine management platform was set up to unify the technical architecture and reduce operation and maintenance costs. At the same time, commercial software was migrated to open source software. Furthermore, the work order system was opened up to automate the machine application process, and a migration system was set up to seamlessly migrate virtual machines managed by vmware to kubevirt, thereby reducing costs. Furthermore, snamrtclone was used to use distributed block storage to solve the problem of slow creation. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0038] Figure 1 The figure is a schematic diagram of the overall process of an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0040] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0041] In the present application, the terms "upper", "lower", "left", "right", "front", "back", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the drawings. These terms are mainly used to better describe the present application and its embodiments, and are not used to limit the indicated devices, elements or components to have a specific orientation, or to be constructed and operated in a specific orientation.

[0042] In addition, some of the above terms may be used to express other meanings in addition to indicating orientation or positional relationship. For example, the term "on" may also be used to express a certain dependency or connection relationship in some cases. For those of ordinary skill in the art, the specific meanings of these terms in this application can be understood according to specific circumstances.

[0043] In addition, the terms "installed", "set", "provided with", "connected", "connected", and "socketed" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral structure; it can be a mechanical connection, or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or it can be an internal connection between two devices, elements, or components. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0044] See also Figure 1 As shown, a virtualized cloud host management method based on kubevirt, the virtualized cloud host management method based on kubevirt comprises the following steps:

[0045] 1. Set up a unified platform for virtual machine management;

[0046] 2. Migrate commercial software to open source software;

[0047] 3. Set up and automate the machine application process;

[0048] 4. Provide mirror client;

[0049] 5. Set snamrtclone to use distributed block storage;

[0050] 6. Issues with vm-import-operate using virtual machine template and supporting zone selection.

[0051] Furthermore, in step 1, a unified virtual machine management platform is set up to unify the technical architecture, reduce operation and maintenance costs, and uniformly adopt the open source K8S base.

[0052] Furthermore, the open source K8S base version is v1.20, the operating system version is centos75.4 kernel, and the use of 5.4 kernel requires the kernel to support the new ceph snapshot feature.

[0053] Furthermore, in step 2, a migration system is set up to seamlessly migrate the virtual machines managed by vmware to kubevirt, thereby reducing costs.

[0054] Furthermore, the migration system is implemented based on vm-v2v technology, providing a user operation interface and back-end application that can configure the migration of any virtual machine managed by VMware. The migration system includes automatic synchronization migration of network settings, system image configuration, CPU, memory and other configurations to ensure that the IP address remains unchanged after migration, and automatic retry of migration errors and other functions.

[0055] Furthermore, in step 3, the work order system is connected to automate the machine application process, and an automated virtual machine creation process is set, wherein the automated virtual machine creation process includes virtual machine form information.

[0056] Furthermore, the virtual machine form information includes information such as computer room, purpose, business line, team, subnet, virtual machine package, quantity, etc., completes the virtual machine automatic creation configuration and completes the virtual machine initialization operation (using slat), including the necessary monitoring agent, security agent, kernel version, security baseline and other related configurations. The initial configuration of the virtual machine uses cloud-int to inject a read-only disk into the virtual machine, and reads the necessary information to complete initial operations such as user creation, disk formatting, and IP configuration. Windows and Linux use a unified technology solution.

[0057] Furthermore, in step 4, when the ceph-csi method creates a pvc problem, the image client cannot correspond to the current ceph version, and the image version is incompatible with the current ceph version, resulting in the inability to create pvc, and the image needs to be remade.

[0058] Furthermore, in step 5, snamrtclone is used to use distributed block storage. When creating a system image based on block storage, the csi mechanism will flatten the pvc, resulting in slow creation. First, a pvc is created under the image namespace. This pvc is created through an image snapshot, and then a tb resource is created to pass the image to the namespace where the virtual machine needs to be created, and then the virtual machine is created through this pvc.

[0059] Furthermore, in step 6, the template needs to configure the vm-config configuration to skip template rendering. To support zone selection, the source code needs to be modified to add the spec field and processing logic. After modification, it is recompiled according to the makefile and deployed to the K8S cluster. The compilation process and dependency resolution process are not described in detail. Only the core code modification part is introduced. At the same time, the migration program is required to specially handle this field as the label of the zone value specified for the migration virtual machine so as to create it in the specified area.

[0060] Code path: pkg / apis / v2v / v1beta1 / virtualmachineimport_types.go

[0061] BeforeEach(func(){

[0062] findTemplate=func()(*oapiv1.Template,error){

[0063] return&oapiv1.Template{},nil

[0064] }

[0065] processTemplate=func(template*oapiv1.Template,name*string,namespacestring)(*kubevirtv1.VirtualMachine,error){

[0066] return&kubevirtv1.VirtualMachine{},nil

[0067] }

[0068] mapper = &mockMapper{}

[0069] targetName:="test"

[0070] zone:="zone0"

[0071] instance.Spec.TargetVMName=&targetName

[0072] instance.Spec.Zone = &zone

[0073] }).

[0074] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A virtualized cloud host management method based on kubevirt, characterized in that: The kubevirt-based virtualized cloud host management method comprises the following steps: (1) Set up a unified platform for virtual machine management; (2) Migrate commercial software to open source software; (3) Set up and automate the machine application process; (4) Provide mirror client; (5) Set snamrtclone to use distributed block storage; (6) Issues with vm-import-operate using virtual machine template and supporting zone selection.

2. The kubevirt-based virtualized cloud host management method according to claim 1, characterized in that: In step 1, a unified virtual machine management platform is set up to unify the technical architecture, reduce operation and maintenance costs, and uniformly adopt the open source K8S base.

3. The kubevirt-based virtualized cloud host management method according to claim 2, characterized in that: The open source K8S base version is v1.20, the operating system version is centos75.4 kernel, and the use of 5.4 kernel requires the kernel to support the new ceph snapshot feature.

4. The kubevirt-based virtualized cloud host management method according to claim 1, characterized in that: In step 2, a migration system is set up to seamlessly migrate the virtual machines managed by vmware to kubevirt, thereby reducing costs.

5. The kubevirt-based virtualized cloud host management method according to claim 4, characterized in that: The migration system is implemented based on vm-v2v technology, providing a user interface and back-end application that can configure the migration of any vmware-managed virtual machine. The migration system includes automatic synchronous migration of network settings, system image configuration, CPU, memory and other configurations to ensure that the IP address remains unchanged after migration, and automatic retry of migration errors and other functions.

6. The kubevirt-based virtualized cloud host management method according to claim 1, characterized in that: In step 3, the work order system is connected to automate the machine application process, and an automated virtual machine creation process is set, wherein the automated virtual machine creation process includes virtual machine form information.

7. The kubevirt-based virtualized cloud host management method according to claim 1, characterized in that: The virtual machine form information includes information such as computer room, purpose, business line, team, subnet, virtual machine package, quantity, etc. Complete the automatic creation configuration of the virtual machine and complete the virtual machine initialization operation (using slat), including the necessary monitoring agent, security agent, kernel version, security baseline and other related configurations. The initial configuration of the virtual machine uses cloud-int to inject a read-only disk into the virtual machine, and read the necessary information to complete initial operations such as user creation, disk formatting, and IP configuration. Windows and Linux use a unified technology solution.

8. The kubevirt-based virtualized cloud host management method according to claim 1, characterized in that: In step 4, when the ceph-csi method creates a pvc problem, the image client cannot correspond to the current ceph version, and the image version is incompatible with the current ceph version, resulting in the inability to create pvc, and the image needs to be remade.

9. The kubevirt-based virtualized cloud host management method according to claim 1, characterized in that: In step 5, snamrtclone is used to use distributed block storage. When creating a system image based on block storage, the csi mechanism will flatten the pvc, resulting in slow creation. First, a pvc is created under the image namespace. This pvc is created through an image snapshot, and then a tb resource is created to pass the image to the namespace where the virtual machine needs to be created, and then the virtual machine is created through this pvc.

10. The kubevirt-based virtualized cloud host management method according to claim 1, characterized in that: In step 6, the template needs to configure the vm-config configuration to skip template rendering. To support zone selection, the source code needs to be modified to add the spec field and processing logic. After modification, it is recompiled according to the makefile and deployed to the K8S cluster. The compilation process and dependency resolution process are not described in detail. Only the core code modification part is introduced. At the same time, the migration program is required to specially handle this field as the label of the zone value specified for the migration virtual machine so as to create it in the specified area. Code path: