[Ocfs2-devel] using ethernet instead of TCP

[Ocfs2-devel] using ethernet instead of TCP

[James Harper]

Has anyone considered having the option of using Ethernet instead of TCP
for inter-node communications? Such a feature would be useful for me as
I'd like to use the same Ethernet segment for inter-node communication
as I run AoE over (much less chance of a split brain), but I don't
currently run IP on that segment. Also, running ocfs2 as the root
filesystem would be easier (I've asked on -users if this is a good idea,
as discussion of that aspect probably isn't appropriate to -devel) as IP
wouldn't need to be started before bringing the root filesystem online.

Obviously it's going to limit the cluster to the one lan segment, and
you get a lot of stuff 'for free' with TCP that would have to be written
for ocfs2 to use Ethernet (but I don't know how much the inter-node
stuff actually makes use of it), so it might be too much work for too
little gain...

Thanks

James

[Ocfs2-devel] using ethernet instead of TCP

[Wim Coekaerts]

nope not yet :)

On Sun, Apr 09, 2006 at 01:56:32PM +1000, James Harper wrote:
> Has anyone considered having the option of using Ethernet instead of TCP
> for inter-node communications? Such a feature would be useful for me as
> I'd like to use the same Ethernet segment for inter-node communication
> as I run AoE over (much less chance of a split brain), but I don't
> currently run IP on that segment. Also, running ocfs2 as the root
> filesystem would be easier (I've asked on -users if this is a good idea,
> as discussion of that aspect probably isn't appropriate to -devel) as IP
> wouldn't need to be started before bringing the root filesystem online.
> 
> Obviously it's going to limit the cluster to the one lan segment, and
> you get a lot of stuff 'for free' with TCP that would have to be written
> for ocfs2 to use Ethernet (but I don't know how much the inter-node
> stuff actually makes use of it), so it might be too much work for too
> little gain...
> 
> Thanks
> 
> James
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel

[Ocfs2-devel] using ethernet instead of TCP

[Zach Brown]

James Harper wrote:
> Has anyone considered having the option of using Ethernet instead of TCP
> for inter-node communications?

TIPC might also be interesting.

  http://tipc.sourceforge.net/

- z

[Ocfs2-devel] using ethernet instead of TCP

[James Harper]

> James Harper wrote:
> > Has anyone considered having the option of using Ethernet instead of
TCP
> > for inter-node communications?
> 
> TIPC might also be interesting.
> 
>   http://tipc.sourceforge.net/
> 

I wasn't able to see the words 'runs directly on ethernet' in any of the
documents that I just browsed, but it certainly seemed to indicate that
it would run independent of IP, which suggests that it must be able to
use Ethernet directly.

Provided there is nothing incompatible between the way it does things
and the way ocfs2 does things, it seems almost perfect for the job.

James

[Ocfs2-devel] using ethernet instead of TCP

[Michael Steinmann]

Zach Brown wrote:
> James Harper wrote:
>   
>> Has anyone considered having the option of using Ethernet instead of TCP
>> for inter-node communications?
>>     
>
> TIPC might also be interesting.
>
>   http://tipc.sourceforge.net/
>
> - z
>   

TIPC not being IP would solve security issues with the currently
IP-based inter-node connections as well. TIPC is for sure an interesting
option for loosely connected nodes that do not share the same security
realm (where the cluster traffic would have to run over an IP-based
firewall).

--
mike