[Openstack] How to configure ESX datastore as a cinder backend storage

Rajshree Thorat rajshree.thorat at gslab.com
Mon Jan 27 04:52:08 UTC 2014


Hi,

Thanks Akash. This works for me.
Attached volumes are visible after re-scanning the iscsi bus.

Regards,
Rajshree

On 1/27/2014 9:57 AM, Akash Bambal wrote:
> Rajshree,
> Can you try re-scanning the iscsi bus after the volume is attached?
>
> - Akash
>
>
> On Fri, Jan 24, 2014 at 6:03 PM, Rajshree Thorat 
> <rajshree.thorat at gslab.com <mailto:rajshree.thorat at gslab.com>> wrote:
>
>     Hi All,
>
>     The problem is solved by pointing vmware_wsdl_location parameter
>     to right location where VMware SDK placed.
>     Now I could successfully attach cinder volumes to instances.
>     However, I had to reboot the instance to get it to
>     pick up the attached volume.
>
>     Is there a way to pick up the attached volume without rebooting
>     guest virtual machine?
>
>     Regards,
>     Rajshree
>
>
>     On 1/24/2014 3:57 PM, Rajshree Thorat wrote:
>
>         Hi All,
>
>         I'm deploying OpenStack Havana for provisioning VMs using ESXi
>         as a hypervisor.
>         I want to use ESX datastore as a cinder backend storage.
>         However, when I try to create a volume,
>         it gives me the following error.
>
>         2014-01-23 06:35:02.960 2862 ERROR
>         cinder.scheduler.filters.capacity_filter
>         [req-e9444c9b-4abb-411b-9476-80213e4c47a1
>         dc1ab39557d7405ebcf35d98885c8dcd
>         1d2b0c8ade234ca08bcef380acdeb8b9] Free capacity not set:
>         volume node info collection broken.
>         2014-01-23 06:35:02.961 2862 ERROR
>         cinder.volume.flows.create_volume
>         [req-e9444c9b-4abb-411b-9476-80213e4c47a1
>         dc1ab39557d7405ebcf35d98885c8dcd
>         1d2b0c8ade234ca08bcef380acdeb8b9] Failed to
>         schedule_create_volume: No valid host was found.
>
>         Provided is the driver configuration file which I am using.
>
>         volume_driver=cinder.volume.drivers.vmware.vmdk.VMwareEsxVmdkDriver
>         vmware_host_ip=<vmware_host_ip>
>         vmware_host_username=<vmware_host_username>
>         vmware_host_password=<vmware_host_password>
>
>         Does anyone have any idea? Pointers in the right direction are
>         always welcome.
>
>         Thanks in advance.
>
>         Regards,
>         Rajshree
>
>
>     -- 
>     Regards,
>     Rajshree
>
>

-- 
Regards,
Rajshree

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140127/c45a321a/attachment.html>


More information about the Openstack mailing list