<div dir="ltr"><div><div><div>Hi Tylor, <br><br></div><div>I just started testing openstack+vmware,Kilo release and vcenter 5.5<br></div><div>Here is what I did to bootup a vmdk based instance: <br><br></div><div><ul><li>Install Kilo basic all in one system. </li></ul></div><div><ul><li>Install a single esxi, upload vcenter ova 5.5. </li></ul></div><div> Enable ssh access to esxi.<br></div><div><ul><li>On vnc ports on esxi's firewall:</li></ul><div style="margin-left:40px"><a href="https://github.com/openstack-vmwareapi-team/Tools">https://github.com/openstack-vmwareapi-team/Tools</a> <br>Update firewall rule for vnc:<br>A. Firewall show current rules:<br>esxcli network firewall ruleset list<br><br><ol><li>Copy zip update to vmfs datastore. </li><li>Change vib acceptance level partent: # esxcli software acceptance set --level=CommunitySupported</li><li>#esxcli software vib install -d “/vmfs/volumes/datastore1/openstackvncfirewall.zip“</li></ol></div><ul><li>Create a port group called: br100 on vswitch (started with a simple Nova network)</li><li>Update nova.conf to point to vcenter:</li></ul><p style="margin-left:40px"> volume_driver=cinder.volume.drivers.vmware.vmdk.VMwareVcVmdkDriver<br> vmware_host_ip=x.y.z.w (vcenter's IP)<br> vmware_host_username=root (needs proper permissions, i just gave it root/full)<br> vmware_host_password= (vcenter user's password)<br> vmware_volume_folder=cinder-volumes </p><p style="margin-left:40px">Restart nova service. <br></p></div><div><ul><li>Download a Cirros image in my case cirros-0.3.4-x86_64-disk.img</li></ul></div><div><ul><li>Convert to vmdk:</li></ul> #qemu-img convert -f qcow2 cirros-0.3.4-x86_64-disk.img -O vmdk cirros-0.3.4-x86_64-disk.vmdk<br></div><div><ul><li>Upload to Glance, choose vmware_adaptor -> lsiLogic else you may not be able to add/mount additional disks on the fly. </li></ul> #glance image-create --name cirros_lsilogic.vmdk --container-format bare --disk-format vmdk --property vmware_disktype="sparse" --property vmware_adaptertype="lsiLogic" --file cirros-0.3.4-x86_64-disk.vmdk<br></div><div><ul><li>Boot instance (admit from Horizon:) based on the image created before. <br></li></ul></div><div>Instance bootedup fine, and it only took me a few days for figure out up to here.. <br></div><div>Let me know which vmdk you tried I can try it on my setup. <br><br></div><div>So my next issue is getting Cinder VMDK volumes to work. </div><div>Update cinder.conf:<br> volume_driver=cinder.volume.drivers.vmware.vmdk.VMwareVcVmdkDriver<br> vmware_host_ip=x.y.z.w<br> vmware_host_username=root<br> vmware_host_password=....... <br> vmware_volume_folder=cinder-volumes <br></div><div>Restart cinder (didn't help rebooting fixed)<br></div><div>Create cinder-volume folder under vcenter. <br></div>Now this is where I'm stuck, I try to create a cinder volume then Cinder list shows new volume.. <br>$ cinder type-create thick_volume<br>$ cinder type-key thick_volume set vmware:vmdk_type=thick<br>$ cinder create --volume-type thick_volume --display-name volume1 1<br><br></div><div># cinder list (looks ok -available ..) <br>+--------------------------------------+-----------+--------------+------+--------------+----------+-------------+<br>| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |<br>+--------------------------------------+-----------+--------------+------+--------------+----------+-------------+<br>| 35365cbf-edbc-40e7-97be-82faff37acee | available | volume2 | 1 | thick_volume | false | |<br>| b27ab736-d396-4a0a-8ef8-eda9adca1d75 | available | volz | 1 | thick_volume | false | |<br>+--------------------------------------+-----------+--------------+------+--------------+----------+-------------+<br><br></div><div><br>But well unsurprisingly I don't see any of them created under vcenter's side. <br></div><br>They should showup as disks which are connected to vm's with names starting with volume-...<br>Yet nothing happens, messing about looking at logs now. <br><br></div><div>Regards,<br></div>Tzach. <br><div><div><div><div><div><div><div><div><br><br></div><div><br><br></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 28, 2015 at 7:11 PM, Tyler Couto <span dir="ltr"><<a href="mailto:tcouto@certain.com" target="_blank">tcouto@certain.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I¹m having trouble running my vmdks on kvm in openstack. It seems that KVM<br>
cannot find the boot partition. I¹ll transcribe some errors from the<br>
console:<br>
<br>
Scanning logical volumes<br>
Reading all physical volumes. This may take a whileŠ<br>
No volume groups found<br>
Activating logical volumes<br>
Volume group ³VolGroup00² not found<br>
<br>
I¹m starting from a flat vmdk that I downloaded from the on esx web UI.<br>
I¹ve tried the following:<br>
- booting flat-vmdk from a glance image<br>
- booting flat-vmdk from a volume<br>
- converting to qcow2 (qemu-img convert) and booting from glance image<br>
- removing all network related info and booting resulting flat-vmdk / qcow2<br>
<br>
I always end up with the errors above.<br>
Can anyone help me with this?<br>
<br>
Thanks,<br>
Tyler<br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><font size="4"><b><span>Tzach Shefi</span></b></font><br>Quality Engineer, Redhat OSP<br><span><a href="callto:+972-52-4534729" target="_blank">+972-54-4701080</a></span></div></div>
</div>