Ask Your Question
2

How can I get multiple hypervisors to work

asked 2015-03-09 02:45:31 -0600

Kosala gravatar image

updated 2015-03-09 05:52:03 -0600

bishoy gravatar image

I have configured a icehouse setup with KVM and VMWare hypervisors in two different compute nodes.

controller1(keystone admin):~# nova hypervisor-list
+----+-------------------------------+
| ID | Hypervisor hostname           |
+----+-------------------------------+
| 11 | compute1.openstack.         |
| 12 | domain-c7(os-cluster)         |
+----+-------------------------------+

I have also created two cinder backends for VMDK and LVMISCSI.

controller1(keystone admin):~# cinder service-list
+------------------+---------------------------------------------+------+----------+-------+----------------------------+-----------------+
|      Binary      |                     Host                    | Zone |  Status  | State |         Updated_at         | Disabled Reason |
+------------------+---------------------------------------------+------+----------+-------+----------------------------+-----------------+
| cinder-scheduler |       controller1.openstack.xxxxxx.com      | nova | enabled  |   up  | 2015-03-09T06:05:10.000000 |       None      |
|  cinder-volume   |  controller1.openstack.xxxxxx.com@LVMConfig | nova | enabled  |   up  | 2015-03-09T06:05:11.000000 |       None      |
|  cinder-volume   | controller1.openstack.xxxxxx.com@VMDKConfig | nova | enabled  |   up  | 2015-03-09T06:05:07.000000 |       None      |
+------------------+---------------------------------------------+------+----------+-------+----------------------------+-----------------+
controller1(keystone admin):~#

I have created two sets of images with the property metatags as follows.

controller1(keystone admin):~# glance image-show Fedora_Image
+-------------------------------+--------------------------------------+
| Property                      | Value                                |
+-------------------------------+--------------------------------------+
| Property 'hypervisor_type'    | vmware                               |
| Property 'vmware_adaptertype' | ide                                  |
| Property 'vmware_disktype'    | sparse                               |
| Property 'vmware_ostype'      | rhel64Guest                          |
| checksum                      | fdd5dc6f3e3e28666ef8b5d06fe3df64     |
| container_format              | bare                                 |
| created_at                    | 2015-03-06T11:09:41                  |
| deleted                       | False                                |
| disk_format                   | vmdk                                 |
| id                            | df62bf8b-b351-45de-96fa-6cdb28e50bd9 |
| is_public                     | True                                 |
| min_disk                      | 0                                    |
| min_ram                       | 0                                    |
| name                          | Fedora_Image                         |
| protected                     | False                                |
| size                          | 441581568                            |
| status                        | active                               |
| updated_at                    | 2015-03-06T11:10:06                  |
+-------------------------------+--------------------------------------+
controller1(keystone admin):~# 
controller1(keystone admin):~# glance image-show openlab_f20
+--------------------------------+--------------------------------------+
| Property                       | Value                                |
+--------------------------------+--------------------------------------+
| Property 'hypervisor_type'     | qemu                                 |
| Property 'volume_backend_name' | LVMDisk_Backend                      |
| checksum                       | d009530079fd6567a3f0579a09c03af0     |
| container_format               | bare                                 |
| created_at                     | 2015-02-24T16:21:49                  |
| deleted                        | False                                |
| disk_format                    | qcow2                                |
| id                             | 8a06076f-9426-4bd9-b38c-e4a54e2b1815 |
| is_public                      | True                                 |
| min_disk                       | 0                                    |
| min_ram                        | 0                                    |
| name                           | openlab_f20                          |
| protected                      | False                                |
| size                           | 158443520                            |
| status                         | active                               |
| updated_at                     | 2015-03-08T18:00:09                  |
+--------------------------------+--------------------------------------+
controller1(keystone admin):~#

I can boot the VMDK image without any problems, on a newly created volume. But the QCOW2 image tries to replicate to VMDK and still fail during the mapping.

Is there any configs I can specify that QCOW2 images should only be using the LVMiSCSI backend?

What I've done wrong?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2015-03-09 07:23:34 -0600

Vinoth gravatar image

Hi. hope this will help !

http://www.vinoth6664.com/multi-hyper...

edit flag offensive delete link more
0

answered 2015-03-10 10:13:18 -0600

Kosala gravatar image

I have seen this in many sites. But still does not address the problem I have. What metadata available for cinder. How can I specify that a particular disk-type should use a particular cinder backend?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-03-09 02:45:31 -0600

Seen: 192 times

Last updated: Mar 10 '15