On 06/17/2012 07:06 PM, Yair Zaslavsky wrote:
On 06/17/2012 03:50 PM, Deepak C Shetty wrote:
On 03/19/2012 03:07 PM, Dan Kenigsberg wrote:
On Wed, Mar 14, 2012 at 07:04:47PM +0530, Deepak C Shetty wrote:
On 02/29/2012 08:06 PM, Dan Kenigsberg wrote:
Let us know if you need further assistance..
If you have that python script working for LOCALFS, I'd suggest you try
making it work for SHAREDFS too.
I was able to use the VDSM_Standalone example, and modify it to use
SHAREDFS
and export glusterfs as a DATA_DOMAIN and invoke VM backed by
gluster storage.
I edited http://www.ovirt.org/wiki/Vdsm_Standalone (scroll below)&
added it as
a SHAREDFS example.
Thanks! It is great news that all you need is O_DIRECT in fuse, and that
Vdsm's SHAREDFS interface works as it is for gluster.
Regards,
Dan.
Hello,
Got more questions on this, now that I am re-visiting this.
The last time i tried using SHAREDFS, i started from createStorageDomain
verb, and it works fine.
But now we have connectStorageServer verb... which i believe is the new
way of doing things ?
If i start from connectStorageServer verb to mount using SHAREDFS (
which goes via PosixFs... MountConnection flow), that won't help me
entirely here, right ?
Because it only mounts based on the dict sent, but does not do anything
with the image and metadata stuff ( which createStorageDomain flow did ).
I am wondering if its too early to start using connectStorageServer ? If
not, how can i re-write the above vdsm standalone example using
connectStorageServer instead of createStorageDomain flow ?
Will a solution via engine (i.e - create PosixFS storage domain) be good
for you?
Well, no. I kind of mis-interpreted the problem. My Q stands canceled.
The right way indeed is to use createStorageServer followed by
createStorageDomain, which i was confused initially a bit, but now its
cleared.
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
