From owner-freebsd-doc@FreeBSD.ORG Sun Feb 27 16:47:38 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA401106566C; Sun, 27 Feb 2011 16:47:38 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 9A5A08FC08; Sun, 27 Feb 2011 16:47:38 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id p1RGlbrM028058; Sun, 27 Feb 2011 09:47:37 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id p1RGlb2E028055; Sun, 27 Feb 2011 09:47:37 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 27 Feb 2011 09:47:37 -0700 (MST) From: Warren Block To: Daniel Gerzo In-Reply-To: <20110227103645.GA53342@freefall.freebsd.org> Message-ID: References: <20110227103645.GA53342@freefall.freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; format=flowed Content-ID: Content-Disposition: INLINE X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Sun, 27 Feb 2011 09:47:37 -0700 (MST) Cc: freebsd-doc@freebsd.org, pjd@freebsd.org, to.my.trociny@gmail.com Subject: Re: RFC: New Handbook section - HAST X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2011 16:47:38 -0000 On Sun, 27 Feb 2011, Daniel Gerzo wrote: > I have prepared a new Handbook section covering HAST. The tech stuff > has been reviewed by Pawel and Mikolaj Golub, so from the tech point of > view it should be all correct. Unfortunately, none of us is native > English speaker, therefore I would like to ask you guys to review the > language and styling of the new section. Acronyms are supposed to be defined on their first use; not sure if every instance of HAST needs to have acronym tags. In any case, the first two paragraphs can be combined and hopefully clarified. High availability is one of the main requirements in serious business applications and highly-available storage is a key component in such environments. Highly Available STorage, or HAST, was developed by &a.pjd; as a framework which allows transparent storage of the same data across several physically separated machines connected by a TCP/IP network. HAST can be understood as a network based RAID1 (mirror), and is similar to the DRBD® storage system known from the GNU/&linux; platform. In combination with other high-availability features of &os; like CARP, HAST makes it possible to build a highly-available storage cluster that is resistant to hardware failures.