cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RCF] removing dead files from CVS HEAD
Date: Mon, 30 Apr 2007 15:55:32 -0400	[thread overview]
Message-ID: <20070430195532.GG4012@redhat.com> (raw)
In-Reply-To: <4635FBBF.3070301@ubuntu.com>

On Mon, Apr 30, 2007 at 04:22:55PM +0200, Fabio Massimo Di Nitto wrote:

> clumon/*  (moved to conga)
> cs-deploy-tool/* (last changelog update is from 2005. seems abandoned)

Stan should be able to answer these..

> csnap*/* (seems abandoned)
> ddraid/* (seems abandoned)

It basically is.  DRBD 0.8 and cmirror + gnbd/iscsi provide similar
solutions to the same problem, and are either close to or fully
production-ready.

> SUBDIRS  = apc bladecenter brocade bullpap drac egenera ilo ipmilan
> SUBDIRS += manual mcdata rps10 rsa rsb scsi sanbox2 vixel wti xvm
> 
> DISABLEDSUBDIRS  = baytech cpint ibmblade primergy rackswitch
> DISABLEDSUBDIRS += rib vmware xcat xen zvm

> there are a bunch of modules that we don't build or install. Does anybody know
> what is the plan for those?

The disabled fence agents are only really disabled probably because
historically, we've kept the CVS pool as Red-Hat-centric as possible.
That is, we disable things we don't support.  From a community
perspective, several agents here should still built per-default.

baytech - This is specific to an old Bay Technologies switch IIRC; I do
not think this is even made anymore.  Probably safe to nuke.

cpint - I don't know what this is.

ibmblade - I don't know what this is.

primergy - I don't know what this is.

rackswitch - I don't know what this is.

rib - Old pre-iLO fencing agent.  I don't know if it's safe to remove or
not; I assume it's superceded by iLO, so it might be safe to remove.

rps10 - 2-node clusters only - very useful; not network-based power
switch.  Actually, I don't know why this isn't enabled *now*; it should
be.

xcat -  I don't know what this is.

xen - kind of superceded by fence_xvm I think - may be safe to remove;
Patrick would know.

zvm - Don't nuke this; z/i/p series support will probably require this.

vmware - gsx/esx specific fencing agent.  Red Hat doesn't currently ship
this agent, but it's community developed, and people use it IIRC.

-- Lon

-- 
Lon Hohberger - Software Engineer - Red Hat, Inc.



  parent reply	other threads:[~2007-04-30 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 14:22 [Cluster-devel] [RCF] removing dead files from CVS HEAD Fabio Massimo Di Nitto
2007-04-30 16:36 ` David Teigland
2007-04-30 19:48   ` Kevin Anderson
2007-04-30 19:49 ` Kevin Anderson
2007-04-30 19:55 ` Lon Hohberger [this message]
2007-05-01  4:02   ` Fabio Massimo Di Nitto
2007-05-01  7:47   ` Patrick Caulfield
2007-05-01  8:22   ` [Cluster-devel] [PATCH] make fence agents list configurable Fabio Massimo Di Nitto
2007-05-02 11:58     ` Patrick Caulfield
2007-05-01 15:05 ` [Cluster-devel] [RCF] removing dead files from CVS HEAD James Parsons
2007-05-01 15:13   ` Fabio Massimo Di Nitto
2007-05-01 15:22   ` David Teigland

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=20070430195532.GG4012@redhat.com \
    --to=lhh@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).