From 89e3c74cf3697e1afec5d7bd775d9e29f673d75e Mon Sep 17 00:00:00 2001 From: Atin Mukherjee Date: Fri, 29 Jan 2016 13:05:24 +0530 Subject: fix broken image in GD2 design Change-Id: I64b18a3812aef5e1735602dd517b1fc6357ee864 Signed-off-by: Atin Mukherjee Reviewed-on: http://review.gluster.org/13314 Reviewed-by: Prashanth Pai Reviewed-by: Jeff Darcy Tested-by: Jeff Darcy --- design/GlusterD2/GD2-Design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'design/GlusterD2') diff --git a/design/GlusterD2/GD2-Design.md b/design/GlusterD2/GD2-Design.md index dafd7d1..0a6a2bb 100644 --- a/design/GlusterD2/GD2-Design.md +++ b/design/GlusterD2/GD2-Design.md @@ -22,7 +22,7 @@ Non trivial effort is involved in adding management support for a new feature. A ## Architectural Overview -[[images/gd2-arch.png]] +![Glusterd 2.0 Architecture](images/gd2-arch.png) The core of GD2 is the centralized store. GD2 will maintain the cluster configuration data, which includes peer and volume information, in a central store instead of maintining it on each peer. It is planned to use [etcd](https://coreos.com/etcd/) to provide the centralized store. etcd servers will only run on a subset of the cluster, tentatively being called the monitor cluster. All other nodes of the cluster will be clients of the monitor cluster. -- cgit