summaryrefslogtreecommitdiffstats
path: root/charms/trusty/zookeeper/README.md
diff options
context:
space:
mode:
authorStuart Mackie <wsmackie@juniper.net>2016-10-07 12:24:58 -0700
committerStuart Mackie <wsmackie@juniper.net>2016-10-07 12:24:58 -0700
commit4faa7f927149a5c4ef7a03523f7bc14523cb9baa (patch)
tree0be55aa0809cc395e45baeae63db660b4e72fe83 /charms/trusty/zookeeper/README.md
parent82f1a7eb5535b30a95b1e71ff18c315d40d1e6f0 (diff)
Charms for Contrail 3.1 with Mitaka
Change-Id: Id37f3b9743d1974e31fcd7cd9c54be41bb0c47fb Signed-off-by: Stuart Mackie <wsmackie@juniper.net>
Diffstat (limited to 'charms/trusty/zookeeper/README.md')
-rw-r--r--charms/trusty/zookeeper/README.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/charms/trusty/zookeeper/README.md b/charms/trusty/zookeeper/README.md
new file mode 100644
index 0000000..7842422
--- /dev/null
+++ b/charms/trusty/zookeeper/README.md
@@ -0,0 +1,10 @@
+ZooKeeper is a centralized service for maintaining configuration information,
+naming, providing distributed synchronization, and providing group services.
+All of these kinds of services are used in some form or another by distributed
+applications. Each time they are implemented there is a lot of work that goes
+into fixing the bugs and race conditions that are inevitable. Because of the
+difficulty of implementing these kinds of services, applications initially
+usually skimp on them ,which make them brittle in the presence of change and
+difficult to manage. Even when done correctly, different implementations of
+these services lead to management complexity when the applications are
+deployed.