Shulou(Shulou.com)05/31 Report--

How to analyze the solution of VMware access to Openstack? in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

Analysis of VMware access to Openstack

There are currently two VMware-related Driver (ESXDriver,VCDriver) in the Nova project in Openstack.

As can be clearly seen from the name, one is the Driver involving ESX and the other is the Driver involving VCenter.

ESXDriver was first contributed by Citrix, and VCDriver was provided by Vmware.

ESXDriver connects ESX to Openstack as Hypervisor, and VCDriver connects Vcenter cluster as Hypervisor to Openstack.

The ESXDriver approach leads to the loss of some clustering features of Vmware, while the VCDriver approach solves these failures, and of course introduces some new problems (to be discussed later).

VCDriver more reflects the complementarity of Vmware and Openstack, on the one hand, the existing stock of VMware is very large, and many enterprise applications are not developed according to the idea of cloud; on the other hand, new applications are developed based on the idea of cloud. The two complement each other to meet the needs of users, which is also in line with the current consensus among vendors on the trend of hybrid cloud.

ESXDriver

There is a slight difference between ESXDriver and other Hypervisor access methods.

There are mainly the following shortcomings:

Unlike KVM and others, VM runs on ESXi and is not the node where nova-compute is located.

ESXDriver limit, only one ESXi host is supported per nova-compute service.

Advanced features on VCenter, such as DRS, are not supported.

VCDriver

This paper mainly introduces VCDriver access. In this way, if the cluster is connected as a Hypervisor, it will naturally have the HA,DRS,VMotion capability.

Currently, each compute node can only support one hypervisor at the same time. Grizzly can only support one VCenter cluster per compute service, and the Havana version has removed this restriction.

Each cluster in VCDriver must have a Datastore to configure and use.

Because cluster is presented as a hypervisor, it also brings the problem of resources across ESXi nodes. Specifically, the CPU and memory resources presented as a Hypervisor as a whole are very sufficient, but the creation of a virtual machine is to find that the resources of any node do not meet the needs of the virtual machine.

Access icon

Access method

Configuration of the nova.conf file. (use VCDriver to connect C1 cluster)

[DEFAULT] compute_driver = vmwareapi.VMwareVCDriver [vmware] host_password = Huawei-123 host_username = Administrator@vsphere.local host_ip = 186.100.21.221 # datastore_regex = NOT DEFINED cluster_name = C1 # multiple cluster can be configured

Explanation:

Compute_driver specifies the Driver to be used.

Host_password/username/ip is used to connect to the vcenter server. Cluseter_name specifies the Vmware cluster to be managed, and multiple clusters can be specified starting with the Havana version.

Datastore_regex datastore configuration format that specifies the datastore that can be used.

Use of mirrors

As you can see from the illustration above, the image is downloaded from Glance to Vmware's datastore.

The process is to call glance API on the compute node to download the image and then use VMware's API to write the image to datastore.

Such a transmission process undoubtedly consumes compute resources and is inefficient.

The process of creating volumes based on mirrors in Cinder is similar and will not be repeated here.

# virt/vmwareapi/vmware_images.pydef fetch_image (context, image, instance, * * kwargs): "" Download image from the glance image server. "" LOG.debug (_ ("Downloading image% s from glance image server")% image, instance=instance) (image_service, image_id) = glance.get_remote_image_service (context, image) metadata = image_service.show (context, image_id) file_size = int (metadata ['size']) read_iter = image_service.download (context) Image_id) read_file_handle = read_write_util.GlanceFileRead (read_iter) write_file_handle = read_write_util.VMwareHTTPWriteFile (kwargs.get ("host"), kwargs.get ("data_center_name"), kwargs.get ("datastore_name"), kwargs.get ("cookies"), kwargs.get ("file_path"), file_size) start_transfer (context, read_file_handle, file_size) Write_file_handle=write_file_handle) LOG.debug (_ ("Downloaded image s from glance image server")% image, instance=instance)

A better way is to use datastore as the back end of glance, so that you don't have to download images like this when creating virtual machines.

So much for the answers to the analysis questions on how to access VMware to Openstack. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.