Hide Forgot
Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/vmware-datastore-storage-backend. Description: A VMware datastore storage backend*: The VMware driver in Nova has to copy the image from the storage backend (filesystem for example) to the datastore to be able boot the VM. We can get rid of this extra network transfer by having a datastore storage backend. In this case, Nova will need to have an image handler** that is using the location of the image instead of downloading the bits to spawn an instance more efficiently. Also, existing VMware customers will be able to create images using the "location(s)" (v2 api) to locate their existing files in the datastore. The VMware datastore will be able to have its own implementation of the Store interface***, namely configure, get, add, delete, etc. * https://github.com/openstack/glance/tree/master/glance/store ** https://review.openstack.org/#/c/33409/ *** https://github.com/openstack/glance/blob/master/glance/store/base.py More information about datastore: http://pubs.vmware.com/vi3/sdk/ReferenceGuide/vim.Datastore.html Specification URL (additional information): None
It seems it is not there: # List of which store classes and store class locations are # currently known to glance at startup. # Existing but disabled stores: # glance.store.rbd.Store, # glance.store.s3.Store, # glance.store.swift.Store, # glance.store.cinder.Store, # glance.store.gridfs.Store, #known_stores=glance.store.filesystem.Store, # glance.store.http.Store I cannot see the "vsphere", though I have read that it should be available. Here: http://docs.openstack.org/developer/glance/configuring.html On the other hand, nova should be able to have multiple location support: https://review.openstack.org/#/c/33409/ So I am confused about this.
The store is there, it's just disabled by default. In order to use it, you need to add `glance.store.vmware_datastore.Store` to the `known_stores` option and uncomment that option in the `glance-api.conf` file.
We are lacking deps on RHEL 6.5 as well as on RHEL 7.0 so I am cloning the bug to to RHEL 6.5. pssh -l root -H 10.34.68.237 -H 10.34.68.219 -i "hostname; cat /etc/redhat-release; openstack-config --set /etc/glance/glance-api.conf DEFAULT known_stores glance.store.vmware_datastore.Store; openstack-service restart glance; sleep 3; openstack-service status glance; grep 'ImportError: No module named vmware' /var/log/glance/*.log | tail -n 3" [1] 15:54:54 [SUCCESS] 10.34.68.237 jhenner-node-permanent-6v5.novalocal Red Hat Enterprise Linux Server release 6.5 (Santiago) Stopping openstack-glance-api: [FAILED] Starting openstack-glance-api: [ OK ] Stopping openstack-glance-registry: [ OK ] Starting openstack-glance-registry: [ OK ] openstack-glance-api dead but pid file exists openstack-glance-registry (pid 8092) is running... /var/log/glance/api.log:2014-06-30 09:51:14.122 7959 TRACE glance ImportError: No module named vmware /var/log/glance/api.log:2014-06-30 09:51:24.987 8070 CRITICAL glance [-] ImportError: No module named vmware /var/log/glance/api.log:2014-06-30 09:51:24.987 8070 TRACE glance ImportError: No module named vmware Stderr: Warning: Permanently added '10.34.68.237' (RSA) to the list of known hosts. [2] 15:54:54 [SUCCESS] 10.34.68.219 jhenner-node-permanent-7v0.novalocal Red Hat Enterprise Linux Server release 7.0 (Maipo) openstack-glance-api (pid 0) is failed openstack-glance-registry (pid 28301) is active /var/log/glance/api.log:2014-06-30 09:50:37.446 28214 TRACE glance ImportError: No module named vmware /var/log/glance/api.log:2014-06-30 09:50:48.183 28297 CRITICAL glance [-] ImportError: No module named vmware /var/log/glance/api.log:2014-06-30 09:50:48.183 28297 TRACE glance ImportError: No module named vmware Stderr: Warning: Permanently added '10.34.68.219' (RSA) to the list of known hosts
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0851.html