On 02/29/2012 08:06 PM, Dan Kenigsberg wrote:
On Wed, Feb 29, 2012 at 07:42:15PM +0530, Deepak C Shetty wrote:
On 02/27/2012 04:55 AM, Ayal Baron wrote:
Any help on documenting this so people would not have to dig into the code would be greatly appreciated.
Great, let me start and get back if i land up into issues. thanks for the pointer.
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.
On Wed, Mar 14, 2012 at 07:04:47PM +0530, Deepak C Shetty wrote:
On 02/29/2012 08:06 PM, Dan Kenigsberg wrote:
On Wed, Feb 29, 2012 at 07:42:15PM +0530, Deepak C Shetty wrote:
On 02/27/2012 04:55 AM, Ayal Baron wrote:
Any help on documenting this so people would not have to dig into the code would be greatly appreciated.
Great, let me start and get back if i land up into issues. thanks for the pointer.
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.
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 ?
On 06/17/2012 06:20 PM, Deepak C Shetty wrote:
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 ?
'Guess i got confused.. the standalone example does use connectStorageServer followed by createStorageDomain. Scratch the question .. my bad..
vdsm-devel@lists.fedorahosted.org