X-Git-Url: https://review.fuel-infra.org/gitweb?a=blobdiff_plain;f=website%2Freference%2Fbasic%2Fgettingstarted_debian.md;fp=website%2Freference%2Fbasic%2Fgettingstarted_debian.md;h=3539663a0a2a32d8c56cda6a36a4b66777381b53;hb=8fd0f35facc21b89b378ecfb253e06a66af1e422;hp=ecab62566bc3ebb27b4c5705285ace5e3e92afbe;hpb=327162e6e319ff38447992668e0753363b870b6e;p=packages%2Fprecise%2Fmcollective.git diff --git a/website/reference/basic/gettingstarted_debian.md b/website/reference/basic/gettingstarted_debian.md index ecab625..3539663 100644 --- a/website/reference/basic/gettingstarted_debian.md +++ b/website/reference/basic/gettingstarted_debian.md @@ -19,16 +19,16 @@ title: Getting Started [ControllingTheDaemon]: /mcollective/reference/basic/daemon.html [SSLSecurityPlugin]: /mcollective/reference/plugins/security_ssl.html [AESSecurityPlugin]: /mcollective/reference/plugins/security_aes.html -[ConnectorStomp]: /mcollective/reference/plugins/connector_stomp.html +[ConnectorActiveMQ]: /mcollective/reference/plugins/connector_activemq.html +[ConnectorRabbitMQ]: /mcollective/reference/plugins/connector_rabbitmq.html [MessageFlowCast]: /mcollective/screencasts.html#message_flow [Plugins]: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki [MCDownloads]: http://www.puppetlabs.com/downloads/mcollective/ [RubyGems]: http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=rubygems +[server_config]: /mcollective/configure/server.html Getting started using Debian based distribution like Debian squeeze and Ubuntu is easy as DEBs are available for most the required components. This guide walks you through the process. -If you just want to experiment with the system please try our [EC2 based demo][EC2Demo]. You should be familiar with the architecture and terminology of Marionette Collective, please review the [basic architecture, terminology and message flow][MessageFlowCast] screencast first. - ## Requirements We try to keep the requirements on external Gems to a minimum, you only need: @@ -46,15 +46,16 @@ We strongly recommend you set up a local Apt repository that will host all the p * Ruby - included with your distribution * [RubyGems] * Stomp Ruby Gem - * [MCollective][MCDownloads] - mcollective-1.x.x-1_all.deb, mcollective-common-1.x.x-1_all.deb, mcollective-client-1.x.x-1_all.deb + * [MCollective][MCDownloads] - mcollective-2.2.x-1_all.deb, mcollective-common-2.2.x-1_all.deb, mcollective-client-2.2.x-1_all.deb The rest of this guide will assume you set up a Apt repository. Puppet Labs hosts a Apt repository with all these dependencies at _apt.puppetlabs.com_. ## ActiveMQ + ActiveMQ is currently the most used and tested middleware for use with MCollective. You need at least one ActiveMQ server on your network, all the nodes you wish to manage will connect to the central ActiveMQ server. -Later on your can [cluster the ActiveMQ servers for availability and scale][ActiveMQClustering]. +Later on you can [cluster the ActiveMQ servers for availability and scale][ActiveMQClustering]. ### Install @@ -68,82 +69,17 @@ ActiveMQ installation instructions can be found [here][ActiveMQ Getting Started] ### Configuring -Initially you'll just keep it simple with a single ActiveMQ broker and a basic user setup, further security information for ActiveMQ -can be found [here][SecurityWithActiveMQ] - -Place the following in your ActiveMQ configuration path as *activemq.xml*. You can download this file from [GitHub][ActiveMQSingleBrokerSample] - -Other examples are also available from [GitHub][ActiveMQSamples] - -{% highlight xml %} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -{% endhighlight %} +[The ActiveMQ config reference][activemq_config] describes all of the ActiveMQ settings that MCollective cares about. For best use, skim the sections you care about while comparing it to an example activemq.xml file. + +[activemq_config]: /mcollective/deploy/middleware/activemq.html -This creates a user *mcollective* with the password *marionette* and give it access to read/write/admin */topic/mcollective.`*`*. You should change this passsword. +We recommend that new users: + +* Start with the [single-broker example config][ActiveMQSingleBrokerSample]. +* Change the [user account passwords](/mcollective/deploy/middleware/activemq.html#authentication-users-and-groups). +* [Set up TLS](/mcollective/deploy/middleware/activemq.html#tls-credentials) and [use a TLS Stomp transport connector](/mcollective/deploy/middleware/activemq.html#transport-connectors). + +Other example config files are also available from [GitHub][ActiveMQSamples]. ### Starting @@ -156,13 +92,13 @@ Start the ActiveMQ service: You should see it running in the process list: {% highlight console %} - # ps -auxw|grep java + # ps auxw|grep java activemq 3012 0.1 14.5 1155112 152180 ? Sl Dec28 2:02 java -Dactivemq.home=/usr/share/activemq -Dactivemq.base=/usr/share/activemq -Dcom.sun.management.jmxremote -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Xmx512m -Djava.library.path=/usr/lib:/usr/lib64 -classpath /usr/share/java/tanukiwrapper.jar:/usr/share/activemq/bin/run.jar -Dwrapper.key=eg4_VvENzCmvtAKg -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=3000 -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.apache.activemq.console.Main start {% endhighlight %} -You should also see it listening on port 61613 in your network stack +You should also see it listening on port 61613 or 61614 in your network stack, depending on whether you turned on TLS. -You should open port 61613 for all your nodes to connect to. +You should open port 61613 or 61614 for all your nodes to connect to. ## Marionette Collective @@ -185,7 +121,7 @@ A machine can be both at once, in which case you need to install all 3 packages. You'll need to tweak some configs in */etc/mcollective/client.cfg*, a full reference of config settings can be found [here][ConfigurationReference]: -We're assuming you called the machine running ActiveMQ *stomp.example.net* please change as appropriate +We're assuming you called the machine running ActiveMQ *stomp.example.net*; please change as appropriate. Also note that the port should be 61614 if you turned on TLS. {% highlight ini %} # main config @@ -194,18 +130,19 @@ We're assuming you called the machine running ActiveMQ *stomp.example.net* pleas loglevel = error # connector plugin config - connector = stomp - plugin.stomp.host = stomp.example.net - plugin.stomp.port = 61613 - plugin.stomp.user = mcollective - plugin.stomp.password = marionette + connector = activemq + plugin.activemq.pool.size = 1 + plugin.activemq.pool.1.host = stomp.example.net + plugin.activemq.pool.1.port = 61613 + plugin.activemq.pool.1.user = mcollective + plugin.activemq.pool.1.password = marionette # security plugin config securityprovider = psk plugin.psk = abcdefghj {% endhighlight %} -You should also create _/etc/mcollective/server.cfg_ here's a sample, , a full reference of config settings can be found here [ConfigurationReference]: +You should also create _/etc/mcollective/server.cfg_ here's a sample, a full reference of config settings can be found on the [Server Configuration Reference][server_config]: {% highlight ini %} # main config @@ -215,11 +152,13 @@ You should also create _/etc/mcollective/server.cfg_ here's a sample, , a full r loglevel = info # connector plugin config - connector = stomp - plugin.stomp.host = stomp.example.net - plugin.stomp.port = 61613 - plugin.stomp.user = mcollective - plugin.stomp.password = marionette + connector = activemq + plugin.activemq.pool.size = 1 + plugin.activemq.pool.1.host = stomp.example.net + plugin.activemq.pool.1.port = 61613 + plugin.activemq.pool.1.user = mcollective + plugin.activemq.pool.1.password = marionette + # facts factsource = yaml @@ -309,4 +248,3 @@ From here you should look at the rest of the wiki pages some key pages are: * [ControllingTheDaemon] - Controlling a running daemon * [AESSecurityPlugin] - Using AES+RSA for secure message encryption and authentication of clients * [SSLSecurityPlugin] - Using SSL for secure message signing and authentication of clients - * [ConnectorStomp] - Full details on the Stomp adapter including failover pools