[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ha-dev
Subject:    Re: [Linux-ha-dev] [teigland@redhat.com: [PATCH 0/7] dlm: overview]
From:       Andrew Beekhof (GMail) <beekhof () gmail ! com>
Date:       2005-04-26 7:39:28
Message-ID: 3f9d7a8199fd689a2a37013f878eba9f () gmail ! com
[Download RAW message or body]


On Apr 25, 2005, at 5:19 PM, Lars Marowsky-Bree wrote:

> FYI.
>
> I think this probably could be driven by a multiple incarnation 
> resource
> agent, though it would benefit from bug #99.
>

Yup, seems like a good fit to me.  Would be nice to auto-populate the 
list of nodes, but I dont think thats going to happen.

>
> Sincerely,
>     Lars Marowsky-Brée <lmb@suse.de>
>
> -- 
> High Availability & Clustering
> SUSE Labs, Research and Development
> SUSE LINUX Products GmbH - A Novell Business
>
>
> From: David Teigland <teigland@redhat.com>
> Date: April 25, 2005 5:11:36 PM CEST
> To: linux-kernel@vger.kernel.org
> Cc: akpm@osdl.org
> Subject: [PATCH 0/7] dlm: overview
>
>
>
> Hi,
>
> This is a distributed lock manager (dlm) that we'd like to see added to
> the kernel.  The dlm programming api is very similar to that found on
> other operating systems, but this is modeled most closely after that in
> VMS.
>
> Many distributed/cluster applications use a dlm for inter-process
> synchronization where processes may live on different machines.  (GFS 
> and
> CLVM are two examples which our group also develop; GFS using the dlm 
> from
> the kernel and CLVM from userspace.)
>
> We've done a lot of work in this second version to meet the kernel's
> conventions.  Comments and suggestions are welcome; we're happy to 
> answer
> questions and make changes so this can be a widely useful feature for
> people running Linux clusters.
>
> The dlm requires configuration from userspace.  In particular, it 
> needs to
> be told which other nodes it should work with, and provided with their 
> IP
> addresses.  In a typical setup, a cluster-membership system in 
> userspace
> would do this configuration (the dlm is agnostic about what system that
> is).  A command line tool can also be used to configure it manually.
> (It's helpful to compare this with device-mapper where 
> dmsetup/LVM2/EVMS
> are all valid userland alternatives for driving device-mapper.)
>
> Features _not_ in this patchset that can be added incrementally:
> . hierarchical parent/child locks
> . lock querying interface
> . deadlock handling, lock timeouts
> . configurable method for master selection (e.g. static master
>   assignment with no resource directory)
>
> Background: we began developing this dlm from the ground up about 3 
> years
> ago at Sistina.  It became GPL after the Red Hat acquisition.
>
> The following patches are against 2.6.12-rc3 and do not touch any 
> existing
> files in the kernel.
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>
>
> _______________________________________________________
> Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
>
--
Andrew Beekhof

"Would the last person to leave please turn out the enlightenment?" - 
TISM

_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

[prev in list] [next in list] [prev in thread] [next in thread]