Merge lp:~niedbalski/charms/precise/rsyslog-forwarder-ha/markdown-modified into lp:charms/rsyslog-forwarder-ha

Proposed by Jorge Niedbalski
Status: Merged
Merged at revision: 8
Proposed branch: lp:~niedbalski/charms/precise/rsyslog-forwarder-ha/markdown-modified
Merge into: lp:charms/rsyslog-forwarder-ha
Diff against target: 71 lines (+12/-20)
1 file modified
README.md (+12/-20)
To merge this branch: bzr merge lp:~niedbalski/charms/precise/rsyslog-forwarder-ha/markdown-modified
Reviewer Review Type Date Requested Status
charmers Pending
Review via email: mp+232567@code.launchpad.net

Description of the change

- Modified README.md to be compatible with CS markdown.

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
=== modified file 'README.md'
--- README.md 2014-08-27 22:16:57 +0000
+++ README.md 2014-08-28 13:50:32 +0000
@@ -1,56 +1,48 @@
1# General1# General
22
3This Charm provides support for adding a [rsyslog](http://www.rsyslog.org) forwarder listener to any service3This Charm provides support for adding a [rsyslog](http://www.rsyslog.org) forwarder listener to any service.
4in addition this charm allows to have multiple rsyslog aggregators servers offering currently 2 replication4In addition, this charm allows to have multiple rsyslog aggregators servers using two different replication
5modes ( fanout, failover ).5modes ( fanout, failover ).
66
7By default the 'fanout' replication mode is going to be used, which means that all the
8syslog messages will be forwarder to any aggregator server using UDP port 514.
9
10Failover mode will forward all the syslog messages to the primary rsyslog server and
11in case of failure will use the secondary rsyslog server.
12
13In you want to choose to failover mode, this will require that your current
14rsyslog server is binded to TCP port 514.
15
7# Usage method16# Usage method
817
9This is a subordinate charm, which means it requires to have a service to hook in. On this18This is a subordinate charm, which means it requires to have a service to hook in. On this
10example we are going to deploy mysql19example we are going to deploy mysql
1120
12```shell
13 juju deploy mysql21 juju deploy mysql
14```
1522
16Then you must deploy this charm23Then you must deploy this charm
1724
18```shell
19 juju deploy rsyslog-forwarder-ha25 juju deploy rsyslog-forwarder-ha
20```
2126
22Once your service is running, you can relate this charm:27Once your service is running, you can relate this charm:
2328
24```shell
25 juju add-relation rsyslog-forwarder-ha mysql29 juju add-relation rsyslog-forwarder-ha mysql
26```
2730
28Then you can deploy your rsyslog aggregators servers:31Then you can deploy your rsyslog aggregators servers:
2932
30```shell
31 juju deploy rsyslog primary33 juju deploy rsyslog primary
32 juju deploy rsyslog secondary34 juju deploy rsyslog secondary
33```
3435
35Once your rsyslog aggregators are ready, you can relate them with your forwarder.36Once your rsyslog aggregators are ready, you can relate them with your forwarder.
3637
37```shell
38 juju add-relation rsyslog-forwarder-ha primary38 juju add-relation rsyslog-forwarder-ha primary
39 juju add-relation rsyslog-forwarder-ha secondary39 juju add-relation rsyslog-forwarder-ha secondary
40```40
41
42By default the 'fanout' replication mode is going to be used, which means that all the
43syslog messages will be forwarder to any aggregator server using UDP port 514.
44
45In you want to choose to failover mode, this will require that your current
46rsyslog servers is binded to TCP port 514.
4741
48Once you have your rsyslog ports opened. You can change the replication-mode variable42Once you have your rsyslog ports opened. You can change the replication-mode variable
49on your rsyslog-forwarder-ha charm.43on your rsyslog-forwarder-ha charm.
5044
51```shell
52 juju set rsyslog-forwarder-ha replication-mode="failover"45 juju set rsyslog-forwarder-ha replication-mode="failover"
53```
5446
55# Contact Information47# Contact Information
5648

Subscribers

People subscribed via source and target branches

to all changes: