精通Puppet：自动化配置管理与扩展

4星 · 超过85%的资源需积分: 9 104 浏览量更新于2024-07-24 收藏 6.92MB PDF 举报

"Pro Puppet 是一本深入介绍 Puppet 配置管理系统的专业书籍，由 James Turnbull 和 Jeffrey McCune 撰写，旨在帮助读者最大化利用 Puppet 的功能并根据自身环境进行定制。书中涵盖了 Puppet 的基本概念、资源管理、环境设置、扩展性、外部化配置、配置存储、监控工具集成、报告以及 Puppet 的扩展功能等方面，适合希望提升 Puppet 使用技巧和理解的 IT 专业人士。 Puppet 是一个跨平台的集中配置管理系统，适用于 Linux、Unix、Windows 系统，它使用 Puppet 自有的描述语言来管理配置文件、用户账户、定时任务（cron）、软件包和系统服务等资源。Puppet 的核心设计是简化资源管理，处理资源间的依赖关系，以实现自动化运维。书中详细介绍了如何开始使用 Puppet，从安装和配置基础环境开始，逐步引导读者构建 Puppet 管理的主机。在 Chapter 2 中，读者将学习如何用 Puppet 创建和管理不同的主机。Chapter 3 讨论了 Puppet 的环境管理，这对于在多环境或不同阶段的项目中保持一致性至关重要。Chapter 4 专注于 Puppet 的可扩展性，讲解如何应对大规模部署的挑战。 Chapter 5 介绍如何将 Puppet 的配置外部化，提高灵活性和可维护性。在 Chapter 6 中，作者探讨了配置数据的导出和存储，这对于版本控制和历史记录追踪非常有用。Chapter 7 提到了 Puppet Dashboard 和 The Foreman 这样的监控控制台，帮助管理员可视化和管理 Puppet 实施。 Chapter 8 介绍了 Puppet 的工具和集成，包括与其他系统管理工具的配合使用。Chapter 9 关注 Puppet 的报告功能，通过报告可以更好地理解和优化 Puppet 的运行效果。Chapter 10 和 11 分别讲解了扩展 Puppet 的事实收集工具 Facter 和实现分布式管理的 Marionette Collective。此外，书中的附录 A 提供了更多关于 Puppet 实践的指导，而索引则方便读者快速查找特定主题。这本书全面覆盖了 Puppet 的各个方面，是系统管理员和运维人员深入了解 Puppet 并提升运维效率的宝贵参考资料。" 通过阅读本书，读者不仅可以掌握 Puppet 的基础操作，还能深入理解 Puppet 的高级特性，从而在实际工作中更高效地应用 Puppet 实现自动化运维。

CHAPTER 1  GETTING STARTED WITH PUPPET

Further instructions are available on the Puppet wiki at

http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Solaris.

Installing from Source

You can also install Puppet and Facter from source tarballs. We don’t recommend this approach

because it makes upgrading, uninstalling and generally managing Puppet across a lot of hosts difficult.

To do this you’ll need to ensure some prerequisites are installed, for example Ruby and its libraries,

using the appropriate packages for your host or via source again. First, download the Facter tarball from

the Puppet Labs site.

$ cd /tmp

$ wget http://puppetlabs.com/downloads/facter/facter-1.5.7.tar.gz

Unpack the tarball and run the install.rb script to install Facter.

$ tar -zxf facter-1.5.7.tar.gz

$ cd facter-1.5.7

# ./install.rb

This will install Facter into the default path for Ruby libraries on your host, for example

/usr/lib/ruby/ on many Linux distributions.

Next, we need to download and install Puppet using the same process:

$ cd /tmp

$ wget http://puppetlabs.com/downloads/puppet/puppet-2.6.1.tar.gz

$ tar -zxf puppet-2.6.1.tar.gz

$ cd puppet-2.6.1

# ./install.rb

Like the Facter steps, this will install Puppet into the default path for Ruby libraries on your host.

 Note You can find the latest Puppet and Facter releases at

http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet.

Installing on Microsoft Windows

Since version 2.6.0, Puppet has supported running on Microsoft Windows. For the 2.6.0 release Puppet

only manages a limited subset of configuration, primarily managing files, but other configuration types

should be available in later releases.

Installing Puppet on Microsoft Windows can be achieved a couple of different ways, but the first

step of both methods is to install Ruby. The easiest way to do this is with the Ruby One-Click Installer

available at http://rubyinstaller.rubyforge.org/wiki/wiki.pl?RubyInstaller. You can also download

binaries at http://www.ruby-lang.org/en/downloads/ if you wish.

We’re going to use the One-Click installer. Download the latest version, which at the time of writing

is at http://rubyforge.org/frs/download.php/47082/ruby186-27_rc2.exe. Run the downloaded

executable and install Ruby. During the installation, select the Use RubyGems tick box.

CHAPTER 1  GETTING STARTED WITH PUPPET

Once Ruby is installed, start the RubyGems Package Manager from the start menu:

Programs -> Ruby-186-27 -> RubyGems -> RubyGems Package Manager

From the command window that opens, you can then install the Facter and Puppet gems.

C:\gem install puppet facter

Installing on other Platforms

We’ve just explained how to install Puppet on some popular platforms. Puppet can also be installed on a

wide variety of other platforms. Puppet is also available in varying versions on:

• MacOS X via MacPorts and from

https://sites.google.com/a/explanatorygap.net/puppet/

• Solaris via Blastwave

• SLES/OpenSuSE via http://software.opensuse.org/

• Gentoo via Portage

• Mandrake and Mandriva via the Mandriva contrib repository

• FreeBSD via ports tree

• NetBSD via pkgsrc

• OpenBSD via ports tree

• ArchLinux via ArchLinux AUR

 Note You can find a full list of additional operating systems and specific instructions at

http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet.

Puppet’s tarball also contains some packaging artifacts in the conf directory, for example an RPM

spec file and OS X build scripts, that can allow you to create your own packages for compatible operating

systems. Now you’ve installed Puppet on your chosen platform, we can start configuring it.

Configuring Puppet

Let’s start by configuring a Puppet master that will act as our configuration server. We’ll look at Puppet’s

configuration files, how to configure networking and firewall access and how to start the Puppet master.

Remember that we’re going to be looking at Puppet in its client-server mode. Here, the Puppet master

contains our configuration data, and Puppet agents connect via SSL and pull down the required

configuration.

On most platforms, Puppet’s configuration will be located under the /etc/puppet directory.

Puppet’s principal configuration file is called puppet.conf and is stored at /etc/puppet/puppet.conf. It is

CHAPTER 1  GETTING STARTED WITH PUPPET

likely that this file has already been created when you installed Puppet, but if it hasn’t, then you can

create a simple file using the following command:

# puppetmasterd --genconfig > puppet.conf

 Note We’re assuming your operating system uses the /etc/ directory to store its configuration files, as most

Unix/Linux operating systems and distributions do. If you’re on a platform that doesn’t, for example Microsoft

Windows, substitute the location of your

puppet.conf configuration file.

The puppet.conf configuration file is constructed much like an INI-style configuration file and

divided into sections. Each section configures a particular element of Puppet. For example, the [agent]

section configures the Puppet agent, and the [master] section configures the Puppet master binary.

There is also a global configuration section called [main]. All components of Puppet will set options

specified in the [main] section.

 Note On releases before 2.6.0, each section was named for the Puppet binary command rather than the

function, for example the [master] section was called [puppetmasterd] and the [agent] section was

[puppetd]. If you have this older style configuration, then Puppet 2.6.0 and later versions will prompt you to

update your configuration file when you start Puppet.

At this stage, we’re only going to add one entry, certname, to the puppet.conf file. The certname

option specifies the name of the Puppet master. We’ll add the certname value to the [master] section (if

the section doesn’t already exist in your file, then create it).

[master]

certname=puppet.example.com

Replace puppet.example.com with the fully qualified domain name of your host.

 Note We’ll look at other options in the puppet.conf file in later chapters.

Adding the certname option and specifying our fully qualified domain name does two things: it

makes troubleshooting certificate issues easier, and it addresses a bug with the Ruby SSL code present

on many Linux-based hosts. This bug requires that we manually specify the name used by your Puppet

master’s SSL certificates. You can read more about the precise bug at

http://projects.puppetlabs.com/projects/puppet/wiki/Ruby_Ssl_2007_006.

CHAPTER 1  GETTING STARTED WITH PUPPET

Firewall Configuration

The Puppet master runs on TCP port 8140. This port needs to be open on your master’s firewall (and any

intervening firewalls and network devices), and your client must be able to route and connect to the

master. To do this, you need to have an appropriate firewall rule on your master, such as the following

rule for the Netfilter firewall:

-A INPUT -p tcp -m state --state NEW --dport 8140 -j ACCEPT

The preceding line allows access from everywhere to TCP port 8140. If possible, you should lock this

down to only networks that require access to your Puppet master. For example:

-A INPUT -p tcp -m state --state NEW -s 192.168.0.0/24 --dport 8140 -j ACCEPT

Here we’ve restricted access to port 8140 to the 192.168.0.0/24 subnet.

 Note You can create similar rules for other operating systems’ firewalls such as pf or the Windows Firewall.

Starting the Puppet Master

The Puppet master can be started via an init script on most Linux distributions. On Red Hat, we would

run the init script with the service command, like so:

# service puppetmaster start

On Debian or Ubuntu, we run it using the invoke-rc.d command:

# invoke-rc.d puppetmaster start

Other platforms should use their appropriate service management tools.

 Note Output from the daemon can be seen in /var/log/messages on Red Hat-based hosts and

/var/log/daemon.log on Debian and Ubuntu hosts. Puppet will log via the daemon facility to Syslog by default on

most operating systems. You will find output from the daemons in the appropriate location and files for your

operating system.

Starting the daemon will initiate your Puppet environment, create a local Certificate Authority,

certificates and keys for the master, and open the appropriate network socket to await client

connections. You can see Puppet’s SSL information and certificates in the /etc/puppet/ssl directory.

# ls –l /etc/puppet/ssl

drwxrwx--- 5 puppet puppet 4096 2009-11-16 22:36 ca

剩余331页未读，继续阅读

lanj3

粉丝: 0
资源: 3

精通Puppet：自动化配置管理与扩展

Pro Puppet(Apress,2ed,2013)

Pro.Puppet.pdf

Pro Puppet 2nd - 第四章 - 扩展

Pro Puppet 2nd：开源系统配置管理指南

Pro Puppet 2nd Edition: Open Source Automation for Cluster Deployments

Puppet 5 Beginner's Guide(3rd) Go from newbie to pro with Puppet 5 无水印原版pdf

omnibus-puppet:创建综合 Puppet 安装程序

收集的Puppet资料 高清

puppet-artifactory:安装和反向代理工件的模块

Pro Puppeta

最新资源

收集的Puppet资料高清