Re: [Aoetools-discuss] [aoetools-discuss] Client being able tointeract with local server

[PongráczI <pongraczi@po...>]

 
> 
> Can you define "Interact?" What do you desire the clients to do with the 
> server?
> 
> j
> 

Accessing to the same block device is possible on the server, using the same block device which you passed as argument to vblade.
You do not need access via aoe, as the device is the same.

For example:
/dev/sdc1 is your aoe device (vbladed 114 1 eth0 /dev/sdc1 )
You can access to this block device on the client as /dev/etherd/e114.1 and as /dev/sdc1 on the server.

I hope it helps.
Anyway, if you have only a server, you can try to use a virtual machine (virtualbox or kvm) to access to the etherd device. 

All depends on your purpose.
Cheers,
István

[Aoetools-discuss] [aoetools-discuss] Client being able to interact with local server

[Erlend Hoel <erlend.hoel@gm...>]

Hello, all!

First of all, please accept my humble apologies if this is the number
one question you don't like to get.  I am under the impression that
there have been others who have wished for this functionality, and
from what I gathered, they were told it didn't exist because it was
never a design goal.

I understand and accept that.  And for all I know, perhaps there are
some weighty and valid reasons why this should be so.  I am
nevertheless in a situation where I desire this functionality (let's
just say that experimentation rates higher on my list of priorities
than performance)

Would this be very hard to implement?  And, related to what I
mentioned above:  Is there a reason why one would _not_ wish to
include this functionality in the standard distribution?

Thank you for your time. :-)

Best regards,
Erlend

Re: [Aoetools-discuss] [aoetools-discuss] Client being able to interact with local server

[Joshua J. Kugler <joshua@az...>]

On Tuesday, July 09, 2013 23:27:07 Erlend Hoel wrote:
> Hello, all!
> 
> First of all, please accept my humble apologies if this is the number
> one question you don't like to get.  I am under the impression that
> there have been others who have wished for this functionality, and
> from what I gathered, they were told it didn't exist because it was
> never a design goal.
> 
> I understand and accept that.  And for all I know, perhaps there are
> some weighty and valid reasons why this should be so.  I am
> nevertheless in a situation where I desire this functionality (let's
> just say that experimentation rates higher on my list of priorities
> than performance)
> 
> Would this be very hard to implement?  And, related to what I
> mentioned above:  Is there a reason why one would _not_ wish to
> include this functionality in the standard distribution?

Can you define "Interact?" What do you desire the clients to do with the 
server?

j

-- 
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
joshua@... - Jabber: pedahzur@...
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A

Re: [Aoetools-discuss] [aoetools-discuss] Client being able tointeract with local server

[PongráczI <pongraczi@po...>]

 
> 
> Can you define "Interact?" What do you desire the clients to do with the 
> server?
> 
> j
> 

Accessing to the same block device is possible on the server, using the same block device which you passed as argument to vblade.
You do not need access via aoe, as the device is the same.

For example:
/dev/sdc1 is your aoe device (vbladed 114 1 eth0 /dev/sdc1 )
You can access to this block device on the client as /dev/etherd/e114.1 and as /dev/sdc1 on the server.

I hope it helps.
Anyway, if you have only a server, you can try to use a virtual machine (virtualbox or kvm) to access to the etherd device. 

All depends on your purpose.
Cheers,
István