From owner-freebsd-rc@FreeBSD.ORG Thu May 18 16:52:40 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0E9216A6CB for ; Thu, 18 May 2006 16:52:40 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55C6343D77 for ; Thu, 18 May 2006 16:52:33 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from localhost (monrovll-cuda1-24-53-251-44.pittpa.adelphia.net [24.53.251.44]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Thu, 18 May 2006 12:52:32 -0400 id 00056410.446CA650.00017BD4 Date: Thu, 18 May 2006 12:52:31 -0400 From: Bill Moran To: "Brian A. Seklecki" Message-Id: <20060518125231.5a1f0fa8.wmoran@collaborativefusion.com> In-Reply-To: <20060518113707.C82296@arbitor.digitalfreaks.org> References: <20060518113707.C82296@arbitor.digitalfreaks.org> Organization: Collaborative Fusion X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-ha@lists.linux-ha.org, freebsd-rc@freebsd.org Subject: Re: Integrating OCF framework w/ (Net|Free)BSD rc.d X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2006 16:52:46 -0000 "Brian A. Seklecki" wrote: > > On Tue, 16 May 2006, joerg@britannica.bec.de wrote: > > > On Tue, May 16, 2006 at 01:35:51PM -0400, Brian A. Seklecki wrote: > > [SNIP] > >> > >> I'm interested in any discussion / thoughts on a strategy or apporach for > >> coding OCF compatibility / integration into our rc.d/ system > > > > Oh my god, another over-complicated Linux "standard" which uses the > > A lot of this goes without saying. However, Linux-HA is the only available, > portable Failover Management Software (FMS) available for POSIX compliant > systems. It's under active development and the 2.x branch has some game. > > I'm not talking about changing any default behavior, I'm asking what the best > strategy would be to put hooks in place to easily enable "compatibility" mode. > > Adding new commands is easy with $extra_commands, but changing return codes > requires some if[]'s in-tree. An extra couple of cycles blown isn't that bad > of a tradeoff to bring high availability (HA) / failover features to *BSD. There was a post to questions@freebsd.org regarding recommendations for HA setup of FreeBSD. The post got no responses. While overcomplicating the rc system is A Bad Thing(tm) in my opinion, I think there is some severe lacking in this area. i.e. _something_ needs to be implemented. Linux HA/OCF seems to share a lot with the existing rcng system, and seems to be the most logical system to try to use. I work with Brian. Knowing our requirements, we're going to set this stuff up, because we need it. Both Brian and I would like to contribute our improvements back to the community. If we could get a consensus on what approach to the problem is most likely to be accepted by the community, then we _will_ be doing work over the next few months that will benefit FreeBSD, and we _will_ be contributing it back to FreeBSD. So, the upshot of this discussion is that Collaborative Fusion is going to be throwing developer resources at FreeBSD HA. We'd like feedback from the FreeBSD community on how we can best do this so that it can be integrated back into the FreeBSD source tree. We've already done _some_ research and we're looking for input. -- Bill Moran Also, I can kill you with my brain. River Tam