Ask Your Question
0

Openstack juno and vmware images error

asked 2015-01-14 07:17:01 -0500

NoNoNoo gravatar image

I'm trying to use openstack juno with vmware integration but I have problems when I try to import and glance images.

I used the following software:

  • For openstack juno installation I used the software Openstack Juno Mirantis 6.0.
  • For VMWare installation I used vCenter 5.0 and ESXi 5.0.

Mirantis openstack installation provides a cirros image called TestVM. I think that the installation of vcenter and openstack is correct because I can create instances of different flavor using TestVM image.

[root@node-39 ~]# glance image-show TestVM
+-------------------------------+-------------------------------------------------+
| Property                      | Value                                           |
+-------------------------------+-------------------------------------------------+
| Property 'hypervisor_type'    | vmware                                          |
| Property 'murano_image_info'  | {"title": "Murano Demo", "type": "cirros.demo"} |
| Property 'vmware_adaptertype' | lsilogic                                        |
| Property 'vmware_disktype'    | sparse                                          |
| checksum                      | 55cb970e727c382e06cdd0976e9c7a73                |
| container_format              | bare                                            |
| created_at                    | 2015-01-09T19:59:50                             |
| deleted                       | False                                           |
| disk_format                   | vmdk                                            |
| id                            | ce90ba99-1095-4977-ad32-71580b4be207            |
| is_public                     | True                                            |
| min_disk                      | 0                                               |
| min_ram                       | 64                                              |
| name                          | TestVM                                          |
| owner                         | 37fa82a9ff644564b3fdfc3b5d8a4357                |
| protected                     | False                                           |
| size                          | 19791872                                        |
| status                        | active                                          |
| updated_at                    | 2015-01-09T19:59:51                             |
+-------------------------------+-------------------------------------------------+

I have problem when I try to launch an instance using any other image. For example I created a cirros image using qemu-img following the guide http://docs.openstack.org/juno/config-reference/content/vmware.html#VMware_images (http://docs.openstack.org/juno/config...) and a centos image downloaded by http://dev.centos.org/centos/hyper-v/CentOS-6.4-x86_64-Minimal-VMware.image.vmdk.bz2 (http://dev.centos.org/centos/hyper-v/...) but when i launch the instance with these images they remain in spawning state.

The nova-compute configuration file is http://pastebin.com/zkk1PQQ1

The nova.conf configuration file is http://pastebin.com/0Nv5Xwda

I obtain the following error in compute.log:

2015-01-14 12:43:46.267 3319 ERROR oslo.vmware.api [-] Task: (returnval){
   value = "session[52029b61-29f5-26b4-6d0f-ef2078885fa2]5255558e-7fe0-3594-982b-d6be9ac40db8"
   _type = "Task"
 } failed with error: File [datastore2] 172.20.1.1_base/9bbcb88d-6ae8-4d8d-9f35-ec8712289869 was not found.
2015-01-14 12:43:46.267 3319 ERROR oslo.vmware.common.loopingcall [-] in fixed duration looping call
2015-01-14 12:43:46.267 3319 TRACE oslo.vmware.common.loopingcall Traceback (most recent call last):
2015-01-14 12:43:46.267 3319 TRACE oslo.vmware.common.loopingcall   File "/usr/lib/python2.6/site-packages/oslo/vmware/common/loopingcall.py", line 76, in _inner
2015-01-14 12:43:46.267 3319 TRACE oslo.vmware.common.loopingcall     self.f(*self.args, **self.kw)
2015-01-14 12:43:46.267 3319 TRACE oslo.vmware.common.loopingcall   File "/usr/lib/python2.6/site-packages/oslo/vmware/api.py", line 419, in _poll_task
2015-01-14 12:43:46.267 3319 TRACE oslo.vmware.common.loopingcall     raise task_ex
2015-01-14 12:43:46.267 3319 TRACE oslo.vmware.common.loopingcall FileNotFoundException: File [datastore2] 172.20.1.1_base/9bbcb88d-6ae8-4d8d-9f35-ec8712289869 was not found

9bbcb88d-6ae8-4d8d-9f35-ec8712289869 is the glance id of the my image and I can see that a directory 172.20.1.1_base/9bbcb88d-6ae8-4d8d-9f35-ec8712289869 hasn't been created in VMFS datastore "datastore2".

Here there is the log of nova-compute http://pastebin.com/4abhQ1dF

Here there is the log of all glance services but there isn't any error http://pastebin.com/7QzjzDev

The unique difference that i found between "TestVM" image that is working and the other images is the value of the property vmware_adaptertype that is "lsilogic" for TestVM ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2015-01-15 06:32:21 -0500

NoNoNoo gravatar image

updated 2015-01-15 06:58:54 -0500

At the end i solved the problem updating to vCenter 5.5 and ESXi 5.5, using the same glance images the instance launch has worked. A list of vCenter and Esx version supported by Openstack (that I haven't found in any documentation) should be really useful.

edit flag offensive delete link more

Comments

i have this error also with vCenter 5.5 and ESXi 5.5. :( still struggle to solve it

wimbo gravatar imagewimbo ( 2015-09-16 02:39:31 -0500 )edit
0

answered 2015-01-14 08:49:09 -0500

dbaxps gravatar image

updated 2015-01-14 08:51:28 -0500

Following :- https://www-304.ibm.com/support/knowl...
I would try command

glance image-create  \
--name my_vmware_windows_image \
--disk-format vmdk  \
--container-format bare \
--is-public False \
--property vmware_disktype="preallocated"   \
--property vmware_adaptertype="lsiLogic"  \
--property vmware_ostype="Windows764_Guest"  \
< /tmp/Win764-flat.vmdk

assuming that Win764-flat.vmdk has been created in VMWARE env ( no qemu-img involvment )

If the image did not come from the qemu-img utility, the vmware_disktype and vmware_adaptertype might be different. To determine the image adapter type from an image file, use the following command and look for the ddb.adapterType= line:

$ head -20 <vmdk file name>
edit flag offensive delete link more

Comments

I tried to following the instruction in your link. I created a centos image in VMWare preallocated and with lsiLogic adapter type and import it in Glance. Using vCenter 5.0 and Esx 5.0 I obtain the same error. I tried to update to vCenter 5.5 and ESX 5.5 and the problem was solved.

NoNoNoo gravatar imageNoNoNoo ( 2015-01-15 06:31:14 -0500 )edit

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-01-14 07:17:01 -0500

Seen: 1,034 times

Last updated: Jan 15 '15