samba-technical Digest, Vol 41, Issue 42

[Stéphane Purnelle]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

samba-technical-request at lists.samba.org a écrit :
> Send samba-technical mailing list submissions to
>     samba-technical at lists.samba.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>     https://lists.samba.org/mailman/listinfo/samba-technical
> or, via email, send a message with subject or body 'help' to
>     samba-technical-request at lists.samba.org
>
> You can reach the person managing the list at
>     samba-technical-owner at lists.samba.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of samba-technical digest..."
>
>
> Today's Topics:
>
>    1. Re: svn commit: samba r15795 (simo)
>    2. Re: dead records in locking.tdb (was: Locking database
>       cleanup?) (John E. Malmberg)
>    3. [samba4] nt status returned when credentials are incorrect
>       (Rafal Szczesniak)
>    4. Re: Samba 3.0.23pre1 and recycle.so (Thomas Bork)
>    5. Re: Samba 3.0.23pre1 and recycle.so (Thomas Bork)
>    6. Re: Samba 3.0.23pre1 and recycle.so (Volker Lendecke)
>    7. Re: Samba 3.0.23pre1 and recycle.so (simo)
>    8. Re: Samba 3.0.23pre1 and recycle.so (Thomas Bork)
>    9. Re: svn commit: samba r15781 - in trunk/source: printing
>       rpc_server    smbd (Jeremy Allison)
>   10. Re: [samba4] nt status returned when credentials are
>       incorrect (Andrew Bartlett)
>   11. New Samba 3 messaging implementations (Aleksey Fedoseev)

> Hi Team!
>
>
> We are working on implementing Samba 3 for clusters. I've published the
> introduction, several clustering problems and proposed decisions (they
> were inspired by Volker's work) on the Samba wiki:
> http://wiki.samba.org/index.php/Clustered_Samba.
>
>
>
> Any cluster implementation has to be based on some kind of messaging.
> The first step we planned is to implement socket-based (or any
> non-local) messaging in the trunk/samba-3 branch - upon that we'll be
> able to extend the messaging with tcp- or any other transport like MPI
> for cluster version of Samba.
>
> Our messaging research is published on the wiki:
> http://wiki.samba.org/index.php/Messaging. There three messaging
> implementations (tdb-based, unix-dgram-sockets from Samba4 and
> unix-stream-sockets) are listed, benchmarked and compared. Patches to
> the current Samba 3 branch can be downloaded there.
>
> The main quesion is - what messaging extension can be added to trunk
> branch, so we'll continue clustering research and shall implement
> messaging-based locking for clusters?..
>

I think that the best way is the tdb-based combined with the first
method for messaging information exchange.
However, I suggest that is not smbd which make the communication with
other's nodes, but a
'tdblockd' daemon which replicate each modification between node (like
a super slurpd).

This alternative can permit to administrator to use a different
network for replication system.
A other advantage is that there are no change of smbd code for add
this task or thread.
Example :
    LAN1 : 10/100 Mb for client purpose
    LAN2 : 1Gb for backup and replication tasks.





- --
Stéphane Purnelle <stephane.purnelle at tiscali.be>
Site Web : http://www.linuxplusvalue.be
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEc2Pm8tswkE3d0ecRAt6MAJwK+pZEPtAUghEdJjOzZ+NqsX2bPwCeKLig
6CtUafOPBEfCuASDQN+gyVk=
=GzK6
-----END PGP SIGNATURE-----