glusterd: check for same node while adding bricks in disperse volume

The optimal way for configuring disperse and replicate volumes
is to have all bricks in different nodes.

During create operation it fails saying it is not optimal, user
must use force to over-ride this behavior. Implementing same
during add-brick operation to avoid situation where all the added
bricks end up from same host. Operation will error out accordingly.
and this can be over-ridden by using force same as create.

fixes: #1047
Change-Id: I3ee9c97c1a14b73f4532893bc00187ef9355238b
Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

0 files changed, 0 insertions, 0 deletions