[sheepdog-users] runtime requirements?

[Miles Fidelman]

Re. the iSCCI vs. NBD options:

The iSCSI instructions are all based around standard iSCSI initiator and 
target commands, but the documentation for NBD (such as it is) says;

 1.

    Create a Sheepdog image

    $ qemu-img create sheepdog:image 4G

 2.

    Start qemu-nbd on the one of Sheepdog servers

    $ qemu-nbd sheepdog:image

Which suggests that one has to have qemu running to publish NBD volumes 
- or is that just for mounting an NBD image from within a VM?  The key 
question: can I set up Sheepdog to publish an NBD volume, and access it 
through native o/s or xen NBD drivers?

Andrew: What's your environment look like (what's Sheepdog running on, 
what kinds of virtualization environment, what kinds of VMs?).

Thanks!

Miles


Andrew J. Hobbs wrote:
> While I haven't personally had to use them in this case (yet).  I'd try the iSCSI or NBD options for sheepdog.   I routinely run benchmarks when trying new combinations, if you do for both of these situations, I'd be very interested in your results.
>
> I keep a linux image with a fully allocated disk to run benchmarks on with the below command.
>
>
> dd if=/dev/zero of=/test.out bs=4k count=1000000 oflag=direct
>
>
>
> On 03/13/2014 10:58 AM, Miles Fidelman wrote:
>
> Since I'm running Xen paravirtualized (for speed in all cases, and for 2 servers, because they don't have
> hardware virtualization available), QEMU based drivers aren't available - hence my reasons for not
> being able to use Sheepdog in the past.
>
> iSCSI solves the problem.  So would NFS.
>
> Thanks!
>
> Miles
>
>
>
>
>
>
>


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra