Merge lp:~lazypower/charms/trusty/hdp-zookeeper/fix_readme_proof into lp:~asanjar/charms/trusty/hdp-zookeeper/trunk

Proposed by Charles Butler
Status: Merged
Merged at revision: 15
Proposed branch: lp:~lazypower/charms/trusty/hdp-zookeeper/fix_readme_proof
Merge into: lp:~asanjar/charms/trusty/hdp-zookeeper/trunk
Diff against target: 47 lines (+20/-16)
1 file modified
README.md (+20/-16)
To merge this branch: bzr merge lp:~lazypower/charms/trusty/hdp-zookeeper/fix_readme_proof
Reviewer Review Type Date Requested Status
amir sanjar Pending
Review via email: mp+233763@code.launchpad.net

Description of the change

fixup readme for charm proof

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'README.md'
2--- README.md 2014-09-08 17:12:11 +0000
3+++ README.md 2014-09-08 17:19:46 +0000
4@@ -1,15 +1,18 @@
5-# Hortonworks Overview
6-Hortonworks zookeeper for HDP 2.1
7-ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization,
8-and providing group services. All of these kinds of services are used in some form or another by distributed applications.
9-Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable.
10-Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them ,which make
11-them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these
12- services lead to management complexity when the applications are deployed.
13-
14-Learn more about ZooKeeper got to
15-http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1.3/bk_installing_manually_book/content/rpm-zookeeper.html
16-# Hortonworks Usage
17+# Hortonworks zookeeper for HDP 2.1
18+
19+ZooKeeper is a centralized service for maintaining configuration information, naming, providing
20+distributed synchronization, and providing group services. All of these kinds of services are used
21+in some form or another by distributed applications. Each time they are implemented there is a lot
22+of work that goes into fixing the bugs and race conditions that are inevitable.
23+
24+Because of the difficulty of implementing these kinds of services, applications initially usually
25+skimp on them ,which make them brittle in the presence of change and difficult to manage. Even when
26+done correctly, different implementations of these services lead to management complexity when the
27+applications are deployed.
28+
29+To learn more about ZooKeeper visit the upstream [docs](http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1.3/bk_installing_manually_book/content/rpm-zookeeper.html)
30+
31+# Deployment Strategy
32
33 Step by step instructions to create a zookeeper quorum :
34
35@@ -37,7 +40,8 @@
36
37 ## zookeeper Upstream Project Name
38
39-- Upstream website: http://zookeeper.apache.org/
40-- Upstream bug tracker :https://issues.apache.org/jira/browse/ZOOKEEPER/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
41-- Upstream mailing list or contact information
42-- Feel free to add things if it's useful for users
43+- [Hortonworks Zookeeper Website](http://hortonworks.com/hadoop/zookeeper/)
44+- [Upstream bug tracker](https://issues.apache.org/jira/browse/ZOOKEEPER/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
45+)
46+- [Upstream mailing list]()
47+

Subscribers

People subscribed via source and target branches