All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Wipfel <rawipfel@novell.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Clustered Samba/CTDB on ocfs2 ?
Date: Mon Jun  4 08:48:10 2007	[thread overview]
Message-ID: <4663DFCF.C5C7.00CF.0@novell.com> (raw)
In-Reply-To: <18019.47337.745002.756250@samba.org>

>>> On Mon, Jun 4, 2007 at  1:02 AM, in message
<18019.47337.745002.756250@samba.org>, <tridge@samba.org> wrote: 
> Mark,
> 
>  > Ok -  understood. Out of curiousity, where is this stuff in its lifetime
>  > (i.e., alpha, aeta, post release, etc). Once we verify that things are
>  > working with Ocfs2 as expected, we could start pointing people asking 
> about
>  > Samba to the CTDB stuff.
> 
> The CTDB stuff has come a long way in the last few weeks. If you or
> anyone else on this list wants to do some testing with OCFS2 then I
> think it would be a good time to start.
> 
> See http://ctdb.samba.org/ and
> http://wiki.samba.org/index.php/CTDB_Setup#Managing_Network_Interfaces 
> for some documentation other information.

Would Samba work with something like the
cluster iptables load sharing stuff? 
http://lists.community.tummy.com/pipermail/linux-ha/2007-May/025390.html
(guess the point is to create a single system
image file server cluster)

- Robert

  reply	other threads:[~2007-06-04  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 13:29 [Ocfs2-devel] Clustered Samba/CTDB on ocfs2 ? tridge
2007-05-02 13:45 ` Mark Fasheh
2007-05-02 14:11   ` tridge
2007-05-02 14:29     ` Mark Fasheh
2007-05-02 14:46       ` tridge
2007-06-04  0:01       ` tridge
2007-06-04  8:48         ` Robert Wipfel [this message]
2007-06-06  3:32           ` tridge
2007-06-08  9:06             ` Robert Wipfel
2007-06-04 15:00         ` Mark Fasheh
2007-06-05  4:11           ` tridge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4663DFCF.C5C7.00CF.0@novell.com \
    --to=rawipfel@novell.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.