Hi, You are right, there is a chicken-and-egg problem with VMware and DS 0 and 1 in OpenNebula 4.2 that prevents the use of the default datastores in VMware. This is fixed in the imminent OpenNebula 4.4 Retina.
The workaround is to simply use two new datastores (say, 100 and 101), configure them with the appropriate BRIDGE_LIST and 'vmfs' drivers and DATASTORE_LOCATION, rename the DS in the ESX hosts and you should be good to go. Regards, -Tino -- OpenNebula - Flexible Enterprise Cloud Made Simple -- Constantino Vázquez Blanco, PhD, MSc Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | es.linkedin.com/in/tinova -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the "To" and "cc" box). They are the property of C12G Labs S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Thu, Nov 28, 2013 at 5:56 PM, Daems Dirk <dirk.da...@vito.be> wrote: > Hi list, > > > > I am quite new to OpenNebula. > > I installed the OpenNebula 4.2 client and configured my VMWare hypervisor. I > can create an OpenNebula host which connects to the VMWare hypervisor > without problems. > > > > However, I can’t seem to get the pre-defined system and image datastores to > work with the vmfs datastore type. I set the DATASTORE_LOCATION in the > oned.conf file to /vmfs/volumes. SSH access for the oneadmin account is > working fine. I also updated the pre-defined system (0) and image (1) > datastores using the correct attribute values for DS_MAD, TM_MAD and > BRIDGE_LIST. In the vSphere client, I created VMFS datastores reflecting the > datastore id’s 0 and 1. > > > > Now the base path of these datastores still points to > /var/lib/one/datastores/0 and /var/lib/one/datastores/0 which is not > correct. > > I would think they need to point to /vmfs/volumes/0 and /vmfs/volumes/1? > > > > Is there a way to change this? I could also create additional system and > image datastores but I though the system datastore should have id 0. In the > vmfs documentation there’s a note that the DATASTORE_LOCATION should be > configured before creating the datastore. However, as the system datastore > is auto-created how can one change the DATASTORE_LOCATION before creation? > > > > Regards, > > Dirk > > VITO Disclaimer: http://www.vito.be/e-maildisclaimer > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org