File: mcollective.README.Debian

package info (click to toggle)
mcollective 2.6.0+dfsg-2.1
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 4,480 kB
  • ctags: 1,164
  • sloc: ruby: 9,588; sh: 652; xml: 468; python: 181; makefile: 161; perl: 127; php: 46
file content (54 lines) | stat: -rw-r--r-- 1,630 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
MCollective in Debian
---------------------

For an working MCollective support, you need one ActiveMQ Instance running in
your network.

In Debian you can simply install `activemq` package. You can find an working
configuration for activemq in the examples directory.

Please choose an new password for the MCollective and Admin user in the
activemq configuration.

This mcollective user and passwords needs to be configured in all your
MCollective servers. (client.cfg and server.cfg).

You need also to set an PSK in your MCollective configuration.

ActiveMQ Configuration step by step:
-----------------------------------

Create an new ActiveMQ instance:

 # mkdir /etc/activemq/instances-available/mcollective

Copy default configuration into ActiveMQ configuration directory:

 # cp /usr/share/doc/mcollective/examples/activemq.xml \
   /etc/activemq/instances-available/mcollective/

Edit configuration, setup new password and username.

In case you need logging:

 # cp /etc/activemq/instances-available/main/log4j.properties \
   /etc/activemq/instances-available/mcollective/

Register new ActiveMQ instance:

 # ln -s /etc/activemq/instances-available/mcollective \
   /etc/activemq/instances-enabled/mcollective

Start ActiveMQ:

 # invoke-rc.d activemq start


ActiveMQ Log configuration:
--------------------------

By default ActiveMQ does not log. To enabled logging you need to copy
the file /etc/activemq/instances-available/main/log4j.properties into
your MCollective instance configuration directory. Than restart your ActiveMQ.

 -- Jonas Genannt <jonas.genannt@capi2name.de>  Mon 25 Jul 2011 20:36:23 +0200