Version information
This version is compatible with:
- Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 3.8.0 < 5.0.0
- , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-puppet_agent', '0.2.0'
Learn more about managing modules with a PuppetfileDocumentation
#puppet_agent
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with puppet_agent
- Usage - Configuration options and additional functionality
- Reference
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Overview
A module for upgrading Puppet 3.8 agents to puppet-agent in Puppet Collection 1 (i.e., Puppet 4).
Module Description
The puppet_agent module installs the Puppet Collection 1 repo (on systems that support repositories); migrates configuration required by Puppet to new locations used by puppet-agent; and installs the puppet-agent package, removing the previous Puppet installation. This module expects Puppet to be installed from packages.
Setup
What puppet_agent affects
- Puppet, Facter, Hiera, and MCollective.
- Puppet's SSL directory and puppet.conf.
- MCollective's server.cfg.
- Removes deprecated settings from puppet.conf.
- Updates puppet.conf and server.cfg for behavioral changes in puppet-agent (future parser is the now the default, and MCollective has a new varlog location).
Setup Requirements
You must be running Puppet 3.8 with stringify_facts
set to 'false'. Agents should already be pointed at a master running Puppet Server 2.1 or greater, and thus successfully applying catalogs compiled with the Puppet 4 language.
Beginning with puppet_agent
Install the puppet_agent module with puppet module install puppetlabs-puppet_agent
.
Usage
Add the class to agents you want to upgrade:
include ::puppet_agent
##Reference
###Public classes
###Private classes
puppet_agent::config
: Configures the services.puppet_agent::install
: Installs packages.puppet_agent::prepare
: Prepares the agent for upgrade.puppet_agent::service
: Ensures the services are running.
###Parameters
####Class: puppet_agent
#####arch
The architecture version you wish to install. Defaults to $::architecture
. This parameter is ignored in Windows Server 2003.
#####package_name
The package to upgrade to, i.e., puppet-agent
. Currently, the default and only accepted value is puppet-agent
.
#####service_name
An array of services to start, normally puppet
and mcollective
. If the array is empty, no services are started.
#####source
Alternate source from which you wish to download the latest version of Puppet.
Limitations
This module supports:
- RHEL 5, 6, 7
- Centos 5, 6, 7
- Debian 6, 7
- Ubuntu 12.04, 14.04
- Windows Server 2003 or later
###Known issues
- In masterless environments, modules installed manually on individual agents cannot be found after upgrading to Puppet 4.x. You should reinstall these modules on the agents with
puppet module install
.
In addition, there are several known issues with Windows:
- To upgrade the agent by executing
puppet agent -t
interactively in a console, you must close the console and wait for the upgrade to finish before attempting to use thepuppet
command again. - MSI installation failures do not produce any error. If the install fails, puppet_agent continues to be applied to the agent.
If this happens, you'll need to examine the MSI log file to determine the failure's cause. You can find the location of the log file in the debug output from either a puppet apply or an agent run; the log file name follows the pattern
puppet-<timestamp>-installer.log
.- On Windows Server 2003, only x86 is supported, and the
arch
parameter is ignored. If you try to force an upgrade to x64, Puppet installs the x86 version with no error message.
- On Windows Server 2003, only x86 is supported, and the
##Development
Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.
We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
To contribute to the puppet_agent module, see Contributing.md. You can also read the complete module contribution guide on the Puppet Labs wiki.
Change Log
All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.
[0.2.0] - 2015-07-21
Summary
Added support for most systems with both Puppet 3.8 and Puppet-Agent packages released by Puppet Labs.
Features
- Support for Debian 6/7, Ubuntu 12.04/14.04, SLES 12, and Windows 2003 through 2012R2.
Bugfixes
- Fix puppet_agent module doesn't touch puppet.conf settings outside an INI section (PUP-4886)
- Made internal classes private, using stdlib's assert_private helper
- Migrate SSL cert directories individually to account for individual settings (PUP-4690)
- Migrated mcollective configuration should prefer the new plugin location (PUP-4658)
- Fixed updating mcollective configuration files with multiple libdir or plugin.yaml definitions (PUP-4746)
[0.1.0] - 2015-06-02
Added
- Initial release of puppetlabs-puppet_agent, supporting Redhat and Centos 5/6/7.
Dependencies
- puppetlabs-stdlib (>= 4.6.0 < 5.0.0)
- puppetlabs-inifile (>= 1.2.0 < 2.0.0)
- puppetlabs-apt (>= 2.0.1 < 3.0.0)
Copyright 2015 Puppet Labs Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.