[one-users] base path of vmfs system datastore

[Tino Vazquez]

Hi,

There must be an error monitoring the datastores, do you see any
relevant in oned.log? Otherwise send it though for analysis.

It would be useful to know the output of:

onedatastore show <ds_id> -x

where ds_id is the id of the system datastore.

There is no problem in using local storage for VMware datastores, I've
updated the documentation to reflect this (it was indeed misleading).

Please consider upgrading to 4.4.

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 abuse at c12g.com and delete the e-mail and
attachments and any copy from your system. C12G thanks you for your
cooperation.


On Mon, Dec 2, 2013 at 10:36 AM, Daems Dirk <dirk.daems at vito.be> wrote:
> Hi,
>
> I created both the system and image datastores.
> In the oned.log file I see that my new 'VMWareImageDatastore' can be monitored successfully.
>
> However, when I try to deploy an image in that VMFS image datastore, I get an error indicating that there is not enough space in the datastore.
> But in the vSphere client there is 275 GB free space and the image is several times smaller.
>
> Currently (for testing), my VMFS volumes are not exported through a SAN, so I don't use iSCSI but a serial attached SCSI drive.
> Could that be the problem? Is it mandatory to use iSCSI?
> From the documentation [1] it looks like it is mandatory to use iSCSI; see 'Infrastructure Configuration', second bullet:
>
> "The ESX servers needs to present or mount as iSCSI both the system datastore and the image datastore (naming them with just the <datastore-id>, for instance 0 for the system datastore and 1 for the image datastore)."
>
> [1] - http://opennebula.org/documentation:rel4.2:vmware_ds#configuring_the_datastore_drivers_for_vmware
>
> Regards,
> Dirk
>
> -----Original Message-----
> From: Tino Vazquez [mailto:cvazquez at c12g.com]
> Sent: donderdag 28 november 2013 18:05
> To: Daems Dirk
> Cc: users at lists.opennebula.org
> Subject: Re: [one-users] base path of vmfs system datastore
>
> 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 abuse at 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.daems at 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 at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
> VITO Disclaimer: http://www.vito.be/e-maildisclaimer
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org