Hi Brad, >These are failing because the ESX host is mounting NFS using the uuid that's >generated from the signature. I tried searching >the list, but I'm not sure how others are dealing with this. I notice the >documentation says that it needs to be mounted with >datastore ID only; e.g. /vmfs/volumes/0 and /vmfs/volumes/1, however, I've >found no way to get the ESX host to actually do >this.
OpenNebula supports ESX 5.x, so it may be a good idea to update. In any case, it should work in ESX 4.x as well, can't you name the NFS based datastore as "0" and "1"? What error is it giving? If there are errors, you can try creating it with a different name and then renaming it. Hope it helps, -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 [email protected] and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On 25 June 2014 20:10, Brad <[email protected]> wrote: > Hi, > > I just started using OpenNebula and was following the quickstart guide when > I hit a snag. When I run onedatastore show <ID>, I see under DATASTORE > CAPACITY that TOTAL/FREE/USED are all 0M. I then executed > /var/lib/one/remotes/datastore/vmfs/monitor with the arguments found in > /var/log/one/oned.log after breaking the monitor script; I then executed it > with bash -x. I saw the problem immediately: > > USED_MB=$(du -sLm /vmfs/volumes/1 2>/dev/null | cut -f1) > DF_STR=$(df -m | grep /vmfs/volumes/1 | sed -e '\''s/ \+/:/g'\'') > > These are failing because the ESX host is mounting NFS using the uuid that's > generated from the signature. I tried searching the list, but I'm not sure > how others are dealing with this. I notice the documentation says that it > needs to be mounted with the datastore ID only; e.g. /vmfs/volumes/0 and > /vmfs/volumes/1, however, I've found no way to get the ESX host to actually > do this. As I'm working with an existing (large-ish) cluster, I'd also like > to avoid screwing anything up for others, so any suggestions will be > appreciated. > > Right now I'm working on getting it to be this instead: > DF_STR=$(df -m | grep `ls -al /vmfs/volumes/ | grep " 1 -> " | awk '{print > $11}'`| sed -e '\''s/ \+/:/g'\'') > > This seems ham fisted to me, and I'm hoping there's some option in > VMware/OpenNebula I'm missing somewhere. > > If this is a version issue, I think I'll be moving from the 4.x to 5.x on > all of my ESX hosts at some point next week. > > Thanks! > Brad > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
