Book description Orchestrate change across server clusters in near realtime with MCollective, the framework that works in concert with Puppet, Chef, and other configuration management tools. Show and hide more. Table of contents Product information. Getting Started 1.
Introduction What Is MCollective? Why Parallel Execution? Web Clients Puppet Enterprise mcomaster 5. Complex Installations Configures MCollective servers, clients, and middleware brokers; handles networks of brokers, subcollectives, and TLS security options. Module Stats 17, downloads 1, latest version 3.
Version information 1. This module has been deprecated by its author since Jan 14th Start using this module Show options. Installation method r10k or Code Manager. Add this module to your Puppetfile: mod 'jorhett-mcollective', '1. Add this module to your Bolt project: bolt module add jorhett-mcollective. Manually install this module globally with Puppet module tool: puppet module install jorhett-mcollective --version 1.
Tags: mcollective , activemq , deprecated. Description This module can configure MCollective middleware brokers, servers, and clients. The module can also create authorization policies from Hiera input. Simple Setup The easiest setup is to put the passwords in Hiera and then simply include the modules in site or nodes manifest. Hiera : common.
For RedHat-derived systems, this can be as easy as this:. Customize to suit your local networks. Check Appendix A for platform-specific instructions. The mcollectived application server runs on nodes that will process requests from clients.
You should pick several target nodes that you desire to make requests of and install the server as described in the following section. The following is the MCollective server configuration file, which should be installed on every host you want to control.
Note that you have to replace two of the passwords in this file and also the libdir directory. Note that libdir will vary between operating systems. For this stage of the learning process, either test on a single operating system or adjust it by hand as necessary for each different OS. To start the service, run the following command:. At this time, you should see the server bound to the ActiveMQ server on the port listed in both the server.
You only need to install the client software on systems from which you will be sending requests. This may be your management hosts, a bastion host, or could be your laptop or desktop systems in the office.
The following is the client configuration file, which should be installed only on hosts from which you will submit requests. Note that you have to replace two of the passwords in this file and also the libdir directory if the operating systems differ. With the pre-shared key security model, anyone who can read the client. I recommend that you limit the people who can read the client file to the people who you trust to execute commands on every system:. The Puppet module provided in this book does this step for you.
You only need to execute the commands just shown during our initial learning installation. Later on, if you are using the provided Puppet module, this will be handled for you. If there are no suitable packages for your operating system, you can install MCollective from source. The installer will place the files in the standard Ruby locations for your platform, or to directories which you give it as options.
You will need to set up init scripts for your operating system on your own. Do not attempt to install from RubyGems. The version in RubyGems was not created by Puppet Labs and is quite a bit older than, and incompatible with, recent versions of MCollective. It also does not install the connector or security plugins. There are a few startup scripts in the MCollective source tree to use as starting points:.
Start with these examples to tailor an appropriate startup script for the MCollective server daemon. You may want to create a package for your platform to avoid installing from source on every node.
To create a package for your operating system, invoke the installer with an option to build a chroot tree for you:.
Once you have done this, copy the init script you created into the package root, adjust the configuration files if necessary, and then build the package according to your operating system standards.
After you have set up a middleware host, at least one server and one client, you can run a test to confirm that your configuration settings are correct. At this point, the installation used for this chapter looks like the diagram shown in Figure Note that host geode has both the server and client software installed.
It will receive requests through the middleware the same as every other server. The ping test is a low-level query that confirms that the server node is communicating through the middleware:.
If you get back a list of each server connected to your middleware and its response time, then congratulations!
You have successfully created a working MCollective framework. Ensure that the three passwords we created are used correctly, and replace them if you need to do so for testing purposes:.
Should be used as the value for plugin. The second most likely problem is a firewall blocking access between the server and the middleware, or the client and the middleware. Test the server connectivity by going to the middleware system and confirm that you see connections to port from each of the servers:.
These settings will not match. In the MCollective configuration files for the server and client, it should indicate activemq , like so:. When doing searches on the Internet, you may find references to a stomp connector. This connector was deprecated in MCollective 2. Always use the native activemq and rabbitmq connectors. Skip to main content. Learning MCollective by Jo Rhett. Start your free trial. Chapter 2. Installation In this part of the book, we will walk you through building a fully functional MCollective environment on several of your hosts.
Requirements Before you install MCollective, you will need to check that you have all of the required elements, as listed in the next two sections.
Operating System The operating system requirements are as follows: Working time synchronization Many problems are due to systems having a different idea of what time it is. Ruby 1. Middleware Broker And these are the middleware broker requirements: MB of memory minimum One of the following messaging middleware options: ActiveMQ 5. Where to Install In the remainder of this book, we discuss MCollective as if you are installing it in your production environment.
Dirty Little Secret I have a dirty little secret to share with you.
0コメント