All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: [DRBD-announce] drbd-8.0_pre1.tar.gz
Date: Tue, 14 Mar 2006 11:53:51 +0100	[thread overview]
Message-ID: <200603141153.51388.philipp.reisner@linbit.com> (raw)

Hi there,

Finally the time has come to bring the DRBDv8 development code to 
a broader audience. Here is the ChangeLog that outlines most improvements:

8.0-pre1 (api:80/proto:80)
--------
 * Removed support for Linux-2.4.x
 * Cleanup of the wire protocol.
 * Added optional peer authentication with a shared secret.
 * Consolidated state changes into a central function.
 * Improved, tunable after-split-brain recovery strategies.
 * Always verify all IDs used in the protocol that are used as pointers.
 * Introduced the "outdate" disk state, and commands for managing it.
 * Introduced the "drbdmeta" command, and require the user to create 
   meta-data explicitly.
 * Support for primary/primary (for OCFS2, GFS...) 
 * Replaced the sync-groups with the sync-after mechanism.
 * The "common" section in the configuration file.
 * Replaced the generation counters (GCs) with data-generation-UUIDs
 * Improved performance by using Linux-2.6's BIOs with up to 32k per
   IO request. Before we transferred only up to 4k per IO request.
 * A Warning if the disk sizes are more than 10% different.
 * A connection teardown packet to differentiate between a crash
   of the peer and a peer that is shut down gracefully.
 * External imposable SyncPause states, to serialize DRBD's resynchronisation
   with the resynchronisation of backing storage's RAID configurations.
 * Backing storage can be hot added to disk less nodes.
 * Prepared for advanced integration to Heartbeat-2.0
 * Changed internal APIs so that missed writes of the meta-data super
   block are reported as they happen.
 * The http://usage.drbd.org sub project.
 * Rewrote the scanner/parser of drbd.conf. 10 times smaller/faster and 
   easier to maintain.
 * Asynchronous meta-data IO [ Code drop from the DRBD+ branch ]

Of course there is no documentation for DRBDv8 yet, nor it is feature
complete. But the still outstanding features are only minor changes.

So it is time for you to start testing this code on your testing 
and staging clusters. 

Please do:
 * stress tests
    IO pressure, memory pressure etc...

 * coverage tests
    Try to test all possible failure and recovery scenarios.

 * Performance comparison tests between drbd-0.7.x and drbd-8.0.x

 * Put OCFS2 / GFS on top of it (still untested from my side)

Please send _usefull_ reports to drbd-dev@lists.linbit.com . Please note
that that list is moderated, and we try to keep the traffic there
quite low.

Send random observations regarding DRBD-8 to drbd-user@lists.linbit.com

http://oss.linbit.com/drbd/8.0/drbd-8.0_pre1.tar.gz
http://svn.drbd.org/drbd/tags/drbd-8.0_pre1/

Thanks!
-Philipp
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria    http://www.linbit.com :

                 reply	other threads:[~2006-03-14 10:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200603141153.51388.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=drbd-announce@lists.linbit.com \
    --cc=drbd-user@lists.linbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.