WO2019080012A1

WO2019080012A1 - Method for cloudstack to take over original vcenter cluster

Info

Publication number: WO2019080012A1
Application number: PCT/CN2017/107683
Authority: WO
Inventors: 李凡成; 张永苏; 梁高能
Original assignee: 深圳市互盟科技股份有限公司
Priority date: 2017-10-25
Filing date: 2017-10-25
Publication date: 2019-05-02

Abstract

Disclosed are a method for a CloudStack to take over an original vCenter cluster, comprising: acquiring cluster information of a vCenter cluster to be taken over; creating a base area and incorporating the vCenter cluster into the management of the CloudStack; collecting basic configuration information of an existing virtual machine in the vCenter cluster; creating a corresponding network, a computing scheme, a disk scheme, and an ISO file according to the basic configuration information; creating a mirrored virtual machine corresponding to the original vCenter cluster; shutting down the virtual machines in the vCenter cluster and the CloudStack; copying the disk files of the virtual machines in the original vCenter cluster to the mirrored virtual machine in the CloudStack; and starting the mirrored virtual machine in the CloudStack. Advantageously, the present invention can quickly implement CloudStack's management of the original vCenter cluster resources by means of a unified self-management interface, and the migration process is transparent and controllable, simple to implement, and easy to operate. By use of the technical solution of the present invention, a customer does not need to use two tools to manage the customer's existing virtual machine and the original virtual machine, thereby saving on the operation and maintenance costs.

Description

CloudStack takes over the original vCenter cluster method

Technical field

The present invention relates to the technical field of Internet cloud computing platform management, and in particular, to a method for CloudStack to take over an original vCenter cluster.

Background technique

In the traditional information security era, isolation is mainly used as a security means, which is divided into physical isolation, internal and external network isolation, and encryption isolation. It has been proved that this isolation method can effectively protect traditional IT architecture. With the rise of cloud computing, this traditional information security, which is isolated as the main idea, has become increasingly difficult to deal with in the new IT architecture. The typical scenario of public cloud is multi-tenant sharing, but compared with the traditional IT architecture, the original trusted boundary is completely broken, and the threat may come directly from neighboring tenants. Cloud security becomes especially important.

CloudStack is the world's leading application service software solution provider Citrix Inc., an open source cloud platform management software that works with the Apache Foundation on CloudStack Infrastructure as a Service (IaaS) product source code. CloudStack accelerates the deployment, management, and configuration of highly scalable public and private clouds (IaaS). Using CloudStack as a foundation, data center operators can quickly and easily build their own cloud services on existing infrastructure. As an open source cloud management platform, CloudStack installation and configuration is relatively simple, providing support for a variety of virtual machine platforms, based on WEB browser management is more convenient, the operation interface is also more beautiful. Now, not only telecom operators are adopting CloudStack, but more and more enterprises are also using CloudStack to build cloud platforms.

CloudStack uses a variety of host virtualization/network virtualization/storage virtualization technologies to build virtual machines and configure management to form an elastically scalable resource pool. Host virtualization supports the management of most major hypervisors, such as KVM virtual machine, XenServer, VMware, Oracle VM, Xen, etc.; network virtualization support such as security group, VLan, GRE, VxLan, etc.; storage virtualization supports local storage, ISCSI storage, network storage (Sharepoint, distributed storage, etc.) .

vCenter refers to VMware vCenter Server, which provides a scalable, scalable platform that provides the foundation for virtualization management and is the easiest and most effective way to manage VMware vSphere. Borrow Help VMware vCenter Server centrally manage all hosts and virtual machines in the data center from a single console that aggregates the performance monitoring capabilities of clusters, hosts, and virtual machines. VMware vCenter Server gives administrators an in-depth view of all the information of a virtual infrastructure's clusters, hosts, virtual machines, storage, guest operating systems, and other key components. With VMware vCenter Server, virtualized environments become easier to manage, and an administrator can manage more than 100 workloads, doubling the efficiency of managing physical infrastructure, but vCenter is commercialized The solution is costly.

With the prosperity and advancement of cloud technology virtualization open source community, CloudStack has won more and more recognition and deployment. vCenter has different levels of application in many companies. However, one of the problems currently faced is how to manage the virtualized products that customers have already used through a unified cloud computing management platform. Some companies want to reduce costs to embrace CloudStack in the open source community, but are limited to the old environment where vCenter has been deployed. If you deploy a new CloudStack environment, there will be two sets of environments that need to be managed, which will undoubtedly increase the work of the system administrator and cause confusion.

The following disadvantages exist in the process of connecting the vCenter to the CloudStack platform: First, the CloudStack can only manage the VMs initiated by the CloudStack and cannot manage the VMs initiated by the vCenter. That is, the vCenter VM cannot be managed by using the CloudStack platform. Second, it is not possible to make CloudStack and vCenter compatible, manage all virtual machines on one management platform, and also need to work back and forth between the two platforms in the administrator's daily management. Third, even if a single virtual machine is taken over to CloudStack through other database operations, when there are many virtual machines in the vCenter, the administrator repeatedly performs a large number of operations, and it is easy to cause problems such as omissions. Fourth, when CloudStack adds a vCenter cluster, it needs to gradually add storage, network, and other resources in the vCenter to the CloudStack according to the logical constraints of the CloudStack. The steps are more and more time is wasted.

Therefore, there is a need for an improved method of CloudStack taking over the original vCenter cluster.

Summary of the invention

The embodiment of the present invention provides a method for the CloudStack to take over the original vCenter cluster, including: acquiring the cluster information of the vCenter cluster to be taken over; creating a basic area, and integrating the vCenter cluster into the management of the CloudStack; The basic configuration information of the existing virtual machine is created; the corresponding network, the computing solution, the disk solution, and the ISO file are created according to the basic configuration information; the mirrored virtual machine corresponding to the original vCenter cluster is created; and the vCenter cluster is closed. with a virtual machine in the CloudStack; copying a disk file of a virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack; and starting the mirrored virtual machine in the CloudStack.

Preferably, the step of acquiring the cluster information of the vCenter cluster to be taken over includes: acquiring basic information of the vCenter cluster, including a vCenter host name, a vCenter user name, a vCenter user password, and a vCenter data center name; The basic information of the vCenter cluster is obtained by calling the SDK to obtain information about the vSwitch network, storage, and virtual machine in the vCenter cluster.

Preferably, the basic configuration information includes information about an operating system type, network information, a CPU, a memory, a hard disk, and a snapshot of a virtual machine that already exists in the vCenter cluster.

Preferably, the step of creating a corresponding network, a computing solution, a disk scheme, and an ISO file includes: creating a specified IP, a computing solution, a disk scheme in the CloudStack, and adding a corresponding ISO file according to a type classification of the operating system. .

Preferably, the step of creating a mirrored virtual machine corresponding to the original vCenter cluster includes: creating a one-to-one correspondence with the virtual machine of the original vCenter cluster according to the computing scheme, the disk scheme, and the ISO file. The mirrored virtual machine.

Preferably, the step of copying the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack includes: in the vCenter shared storage, the disk of the virtual machine in the original vCenter The vmdk file is copied to the folder of the newly created mirror virtual machine in the CloudStack, and the corresponding disk vmdk file in the CloudStack is deleted.

Preferably, the step of copying the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack further includes: renaming the copied disk vmdk file to the deleted in the CloudStack The name of the disk vmdk file.

Preferably, the step of copying the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack further includes: using the vSphere Clinet SDK, the virtual machine in the original vCenter cluster The folder name is renamed with the folder name of the corresponding mirrored virtual machine created in the CloudStack.

Preferably, the step of copying the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack further includes: deleting a folder name of the virtual machine in the original vCenter cluster, File name and file configuration information in the folder and the CloudStack The folder name of the newly created mirror virtual machine, the file name in the folder, and the file configuration information are modified one-to-one. This avoids the time cost of copying disk files.

Preferably, the step of starting the mirrored virtual machine further comprises: checking whether the mirrored virtual machine in the CloudStack starts normally, whether the disk file and the snapshot are complete, whether the network IP is used normally; and once the check passes, The migration is completed and the CloudStack begins to take over the corresponding virtual machine in the original vCenter cluster.

Advantageously, the method in which the CloudStack takes over the original vCenter cluster in the embodiment of the present invention can quickly implement the management of the original vCenter cluster resources by the CloudStack through a unified self-management interface, and the migration process is transparent and controllable, simple to implement, and easy to operate. The technical solution of the present invention can prevent the customer from using two tools to manage the existing virtual machine and the original virtual machine of the customer, thereby saving operation and maintenance costs.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

FIG. 1 is a schematic flowchart of a method for a CloudStack to take over an original vCenter cluster according to an embodiment of the present invention.

Detailed ways

The technical solutions of the present invention are further described in detail below with reference to the accompanying drawings and specific embodiments. It is apparent that the described embodiments are only a part of the embodiments of the invention, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of the present invention.

FIG. 1 is a schematic flowchart diagram of a method 100 for a CloudStack to take over an original vCenter cluster according to an embodiment of the present invention. As shown in FIG. 1, the takeover cluster method 100 can include the following steps:

Step S102: Obtain cluster information of the vCenter cluster to be taken over.

Specifically, the step S102 may include: acquiring basic information of the vCenter cluster, including a vCenter host name, a vCenter user name, a vCenter user password, and a vCenter data center name; The basic information of the obtained vCenter cluster is obtained by calling the SDK to further obtain information about the vSwitch network, the storage, and the virtual machine in the vCenter cluster.

Step S104: Create a basic area, and integrate the vCenter cluster into the management of the CloudStack.

Step S106: Statistics basic configuration information of the virtual machine that exists in the vCenter cluster. For example, the basic configuration information may include information about an operating system type, network information, CPU, memory, hard disk, and snapshot of a virtual machine that already exists in the vCenter cluster.

Step S108: Create a corresponding network, a computing solution, a disk scheme, and an ISO file according to the basic configuration information.

Specifically, step S108 may include: creating a specified IP, a computing scheme, a disk scheme in the CloudStack, and adding a corresponding ISO file according to a type classification of the operating system.

Step S110: Create a mirrored virtual machine corresponding to the original vCenter cluster.

Specifically, the step S110 may include: creating, according to the computing solution, the disk solution, and the ISO file, the mirrored virtual machine corresponding to the virtual machine of the original vCenter cluster.

Step S112: Shut down the virtual machine in the vCenter cluster and the CloudStack.

Step S114: Copy the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack.

Preferably, the step S114 may include: copying, in the vCenter shared storage, a disk vmdk file of the virtual machine in the original vCenter to a folder of the newly created mirror virtual machine in the CloudStack, and simultaneously The corresponding disk vmdk file is deleted.

Preferably, step S114 may further include: renaming the copied disk vmdk file to a name of the deleted disk vmdk file in the CloudStack.

Preferably, the step S114 may further include: renaming, by using the vSphere Clinet SDK, a folder name of the virtual machine in the original vCenter cluster and a folder name of the corresponding mirrored virtual machine created in the CloudStack.

Preferably, the step S114 may further include: a folder name of the virtual machine in the original vCenter cluster, a file name in the folder, file configuration information, and a file of the newly created mirror virtual machine in the CloudStack. The folder name, the file name in the folder, and the file configuration information are modified one-to-one. This avoids the time cost of copying disk files.

Step S116: Start the mirror virtual machine in the CloudStack.

Preferably, step S116 may further include: checking whether the mirrored virtual machine in the CloudStack starts normally, whether the disk file and the snapshot are complete, whether the network IP is used normally; and once the check passes, the migration is completed and the CloudStack starts. Takes over the corresponding virtual machine in the original vCenter cluster.

It should be noted that, through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary hardware platform, and of course, all can be implemented by hardware. Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, or the like. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or in some portions of the embodiments.

The above are only the preferred embodiments of the present invention, and the scope of the present invention is not limited thereto, and the equivalent changes made by the claims of the present invention are still within the scope of the present invention.

Claims

A method in which CloudStack takes over the original vCenter cluster, including:

Obtain cluster information of the vCenter cluster to be taken over;

Create a base area, and integrate the vCenter cluster into the management of the CloudStack;

Statistics basic configuration information of the existing virtual machine in the vCenter cluster;

Creating a corresponding network, a computing solution, a disk solution, and an ISO file according to the basic configuration information;

Create a mirrored virtual machine corresponding to the original vCenter cluster;

Shutting down the vCenter cluster and the virtual machines in the CloudStack;

Copying the disk files of the virtual machines in the original vCenter cluster to the mirrored virtual machines in the CloudStack;

The mirrored virtual machine is started in the CloudStack.
The method for taking over the cluster of the vCenter cluster to be taken over by the method of claim 1 is as follows:

Obtain basic information about the vCenter cluster, including the vCenter host name, vCenter user name, vCenter user password, and vCenter data center name;

The information about the vSwitch network, the storage, and the virtual machine in the vCenter cluster is further obtained by calling the SDK according to the basic information of the obtained vCenter cluster.
The takeover cluster method according to claim 1, wherein the basic configuration information includes information about an operating system type, network information, a CPU, a memory, a hard disk, and a snapshot of a virtual machine that is already in the vCenter cluster.
The method of taking over a cluster according to claim 1, wherein the steps of creating a corresponding network, a computing solution, a disk scheme, and an ISO file include:

Create a specified IP, computing scheme, disk scheme in the CloudStack, and add the corresponding ISO file according to the type classification of the operating system.
The method of taking over a cluster according to claim 1, wherein said creating corresponds to said The steps of the mirrored virtual machine of the original vCenter cluster include:

And creating, according to the computing solution, the disk solution, and the ISO file, the mirrored virtual machine corresponding to the virtual machine of the original vCenter cluster.
The method of taking over the clustering of the virtual machine in the original vCenter cluster to the mirroring virtual machine in the CloudStack, comprising:

In the vCenter shared storage, the disk vmdk file of the virtual machine in the original vCenter is copied to the folder of the newly created mirror virtual machine in the CloudStack, and the corresponding disk vmdk file in the CloudStack is deleted.
The method of taking over the clustering of the virtual machine according to claim 6, wherein the step of copying the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack further includes:

Rename the copied disk vmdk file to the name of the disk vmdk file deleted in the CloudStack.
The method of taking over the clustering of the virtual machine according to claim 6, wherein the step of copying the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack further includes:

The folder name of the virtual machine in the original vCenter cluster is renamed with the folder name of the corresponding mirrored virtual machine created in the CloudStack by using the vSphere Clinet SDK.
The method of taking over the clustering of the virtual machine according to claim 6, wherein the step of copying the disk file of the virtual machine in the original vCenter cluster to the mirrored virtual machine in the CloudStack further includes:

The folder name of the virtual machine in the original vCenter cluster, the file name in the folder, the file configuration information, the folder name of the newly created mirror virtual machine in the CloudStack, and the file name in the folder. The file configuration information is modified one by one.
The method of taking over the clustering virtual machine according to claim 1, wherein the step of starting the mirrored virtual machine further comprises:

Check whether the mirrored virtual machine in the CloudStack is started normally, whether the disk file and the snapshot are complete, and whether the network IP is used normally;

Once the check passes, the migration is completed and the CloudStack begins to take over the corresponding virtual machine in the original vCenter cluster.