From 7bc15d8eb864c193321df31659872b24a2a71dea Mon Sep 17 00:00:00 2001
From: Ravishankar N <ravishankar@redhat.com>
Date: Wed, 19 Aug 2015 16:39:41 +0530
Subject: Update outcast.md to arbiter.md

Change-Id: I743e71f6d53ad09ddb2cb6da2242c1b1ed584bd0
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
---
 Feature Planning/GlusterFS 3.7/Outcast.md |  95 ----------------------------
 Feature Planning/GlusterFS 3.7/arbiter.md | 100 ++++++++++++++++++++++++++++++
 2 files changed, 100 insertions(+), 95 deletions(-)
 delete mode 100644 Feature Planning/GlusterFS 3.7/Outcast.md
 create mode 100644 Feature Planning/GlusterFS 3.7/arbiter.md

diff --git a/Feature Planning/GlusterFS 3.7/Outcast.md b/Feature Planning/GlusterFS 3.7/Outcast.md
deleted file mode 100644
index 9314ca2..0000000
--- a/Feature Planning/GlusterFS 3.7/Outcast.md	
+++ /dev/null
@@ -1,95 +0,0 @@
-Feature
--------
-
-This feature provides a way of preventing split-brains in time.
-
-Summary
--------
-
-Please see <http://review.gluster.org/#/c/9656/>
-
-Owners
-------
-
-Pranith Kumar Karampuri  
-Ravishankar N
-
-Current status
---------------
-
-Feature complete.
-
-Code patches: <http://review.gluster.org/#/c/10257/> and
-<http://review.gluster.org/#/c/10258/>
-
-Detailed Description
---------------------
-
-Benefit to GlusterFS
---------------------
-
-It prevents split-brains in time.
-
-Scope
------
-
-### Nature of proposed change
-
-### Implications on manageability
-
-None
-
-### Implications on presentation layer
-
-None
-
-### Implications on persistence layer
-
-None
-
-### Implications on 'GlusterFS' backend
-
-None
-
-### Modification to GlusterFS metadata
-
-None
-
-### Implications on 'glusterd'
-
-None
-
-How To Test
------------
-
-If we bring down bricks and perform writes in such a way that arbiter
-brick is the only source online, writes/reads will be made to fail with
-ENOTCONN. See 'tests/basic/afr/arbiter.t' in the glusterfs tree for
-examples.
-
-User Experience
----------------
-
-Similar to a normal replica 3 volume. The only change is the syntax in
-volume creation. See
-<https://github.com/gluster/glusterfs/blob/master/doc/features/afr-arbiter-volumes.md>
-
-Dependencies
-------------
-
-None
-
-Documentation
--------------
-
----
-
-Status
-------
-
-Feature completed. See 'Current status' section for the patches.
-
-Comments and Discussion
------------------------
-
----
diff --git a/Feature Planning/GlusterFS 3.7/arbiter.md b/Feature Planning/GlusterFS 3.7/arbiter.md
new file mode 100644
index 0000000..797f005
--- /dev/null
+++ b/Feature Planning/GlusterFS 3.7/arbiter.md	
@@ -0,0 +1,100 @@
+Feature
+-------
+
+This feature provides a way of preventing split-brains in replica 3 gluster volumes both in time and space.
+
+Summary
+-------
+
+Please see <http://review.gluster.org/#/c/9656/> for the design discussions
+
+Owners
+------
+
+Pranith Kumar Karampuri  
+Ravishankar N
+
+Current status
+--------------
+
+Feature complete.
+
+Code patches: <http://review.gluster.org/#/c/10257/> and
+<http://review.gluster.org/#/c/10258/>
+
+Detailed Description
+--------------------
+Arbiter volumes are replica 3 volumes where the 3rd brick of the replica is
+automatically configured as an arbiter node. What this means is that the 3rd
+brick will store only the file name and metadata, but does not contain any data.
+This configuration is helpful in avoiding split-brains while providing the same
+level of consistency as a normal replica 3 volume.
+
+Benefit to GlusterFS
+--------------------
+
+It prevents split-brains in replica 3 volumes and consumes lesser space than a normal replica 3 volume.
+
+Scope
+-----
+
+### Nature of proposed change
+
+### Implications on manageability
+
+None
+
+### Implications on presentation layer
+
+None
+
+### Implications on persistence layer
+
+None
+
+### Implications on 'GlusterFS' backend
+
+None
+
+### Modification to GlusterFS metadata
+
+None
+
+### Implications on 'glusterd'
+
+None
+
+How To Test
+-----------
+
+If we bring down bricks and perform writes in such a way that arbiter
+brick is the only source online, writes/reads will be made to fail with
+ENOTCONN. See 'tests/basic/afr/arbiter.t' in the glusterfs tree for
+examples.
+
+User Experience
+---------------
+
+Similar to a normal replica 3 volume. The only change is the syntax in
+volume creation. See
+<https://github.com/gluster/glusterfs-specs/blob/master/Features/afr-arbiter-volumes.md>
+
+Dependencies
+------------
+
+None
+
+Documentation
+-------------
+
+---
+
+Status
+------
+
+Feature completed. See 'Current status' section for the patches.
+
+Comments and Discussion
+-----------------------
+Some optimizations are under way.
+---
-- 
cgit