From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] Integration with external clustering
Date: Tue Oct 18 18:47:50 2005 [thread overview]
Message-ID: <20051018234757.GD25876@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20051018230323.GE2813@marowsky-bree.de>
Hi Lars,
On Wed, Oct 19, 2005 at 01:03:23AM +0200, Lars Marowsky-Bree wrote:
> > Have you also considered what this will or won't do to possible
> > interaction with the CMan stack? We'd love OCFS2 to handle both stacks.
>
> This is hard for us to judge, but given that CMan in recent mailing list
> discussions seems to be moving towards a user-space driven membership
> too, it's fairly likely useable here too.
Right, and we're only interested in the new (userspace only) CMan, so no
need to consider the kernel code.
> My goal is for the user to only add a single resource entry (a so-called
> "clone" resource type) to the configuration for each OCFS2 filesystem,
> and then he'd be done; the cluster would auto-generate everything else.
Do you mean that the user would have to add a configuration entry for every
single OCFS2 mount on their machine? Unless that's done automatically and
transparently (perhaps from mount.ocfs2), it's pretty much a non starter.
We've always wanted the users path (once the cluster stack is installed and
configured) to be as easy as a local filesystem: mkfs.ocfs2 /dev/foo; mount
/dev/foo /ocfs2.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2005-10-18 18:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 16:52 [Ocfs2-devel] [RFC] Integration with external clustering Jeff Mahoney
2005-10-18 17:18 ` Joel Becker
2005-10-18 18:03 ` Lars Marowsky-Bree
2005-10-18 18:27 ` Joel Becker
2005-10-18 18:50 ` Mark Fasheh
2005-10-19 8:26 ` Lars Marowsky-Bree
2005-10-19 12:49 ` Joel Becker
2005-10-19 17:41 ` Jeff Mahoney
2005-10-20 7:39 ` Lars Marowsky-Bree
2005-10-19 16:30 ` Jeff Mahoney
2005-10-20 5:24 ` Lars Marowsky-Bree
2005-10-20 10:03 ` Joel Becker
2005-10-20 10:25 ` David Teigland
2005-10-20 10:42 ` Joel Becker
2005-10-20 10:45 ` Lars Marowsky-Bree
2005-10-21 4:05 ` Andrew Beekhof
2005-10-24 6:41 ` Lars Marowsky-Bree
2005-10-24 8:39 ` Andrew Beekhof
2005-10-21 4:09 ` Christoph Hellwig
2005-10-21 9:29 ` Robert Wipfel
2005-11-06 23:01 ` Christoph Hellwig
2005-11-07 6:08 ` Lars Marowsky-Bree
2005-10-20 6:04 ` Andrew Beekhof
2005-10-18 18:47 ` Mark Fasheh [this message]
2005-10-19 8:35 ` Lars Marowsky-Bree
2005-10-18 18:20 ` Jeff Mahoney
2005-10-19 14:57 ` Lars Marowsky-Bree
2005-10-19 17:42 ` David Teigland
2005-10-20 5:58 ` Lars Marowsky-Bree
2005-10-20 9:45 ` David Teigland
2005-10-28 10:11 ` [Ocfs2-devel] " Lars Marowsky-Bree
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=20051018234757.GD25876@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.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.