RE: [Linux-cluster] Re: [ANNOUNCE] OpenSSI 1.0.0 released!!

From: Walker, Bruce J (bruce.walker_at_hp.com)
Date: 07/31/04

  • Next message: Jeff Garzik: "Re: PATCH: VLAN support for 3c59x/3c90x" 
    Date:	Sat, 31 Jul 2004 09:00:34 -0700
To: "Discussion of clustering software components including GFS" <linux-cluster@redhat.com>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>

    Kevin,
       Got out of bed on the wrong side? Such anger. First, the
    clusterwide device capability is a very small part of OpenSSI so your
    comment "put the entire clustering layer on top of it" is COMPLETELY
    wrong - you clearly are commenting about something you know nothing
    about. In the 2.4 implementation, providing this one capability by
    leveraging devfs was quite economic, efficient and has been very stable.
    I'm not sure who you mean by "that's what WE want". If you mean the
    current worldwide users of OpenSSI on 2.4, they are a very happy group
    with a kick-ass clustering capability.

    About one thing you are correct. We are going to have to have a way to
    lookup and name remote devices in 2.6. I believe the remote file-op
    mechanism we are using in 2.4 will adapt easily.

    Bruce Walker
    Architect and project manager - OpenSSI project

    > -----Original Message-----
    > From: linux-cluster-bounces@redhat.com
    > [mailto:linux-cluster-bounces@redhat.com] On Behalf Of Kevin
    > P. Fleming
    > Sent: Saturday, July 31, 2004 7:41 AM
    > To: Linux Kernel Mailing List
    > Cc: linux-cluster@redhat.com;
    > opengfs-devel@lists.sourceforge.net;
    > opengfs-users@lists.sourceforge.net;
    > opendlm-devel@lists.sourceforge.net
    > Subject: [Linux-cluster] Re: [ANNOUNCE] OpenSSI 1.0.0 released!!
    >
    >
    > Aneesh Kumar K.V wrote:
    >
    > > 5. Devices
    > > * there is a clusterwide device model via the devfs code
    >
    > Yeah, that's we want, take buggy, unreliable,
    > soon-to-be-removed-from-mainline code and put an entire
    > clustering layer
    > on top of it. Too bad someone is going to need to completely
    > reimplement
    > this "clusterwide device model".
    >
    > --
    > Linux-cluster mailing list
    > Linux-cluster@redhat.com
    > http://www.redhat.com/mailman/listinfo/linux-cluster
    >
    -
    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/

  • Next message: Jeff Garzik: "Re: PATCH: VLAN support for 3c59x/3c90x"

    Relevant Pages

    • Re: [SLE] Looking for a book that describes highly available DHCP setups
      ... > dhcpd has clustering capability included, ... > Linux-HA is not sufficient, as this doesn't synchronize the DHCP ... > leases between the clustering nodes. ... Usage of ISC dhcpd's failover capabilities avoids that problem. ...
      (SuSE)
    • Re: How to map high memory for block io
      ... The way I'm proposing to fix this for mmci is to introduce a ... new capability which says "clustering is supported by this driver." ... (The side effect of this patch is that everyone ends up with clustering ...
      (Linux-Kernel)
    • How does clustering assign multiple IP addresses?
      ... This isn't so much to do with clustering per se but clustering makes use of ... this capability. ... When a virtual server is created, a single adapter can be ...
      (microsoft.public.windows.server.clustering)
    • Re: Windows 2000 server and advanced server.
      ... Asside from supporting more memory and more processors, Advanced Server has the capability to do clustering. ... Windows 2000 Server cannot do clustering. ...
      (microsoft.public.win2000.advanced_server)