精通Puppet：权威指南

5星 · 超过95%的资源需积分: 9 170 浏览量更新于2024-07-25 收藏 6.92MB PDF 举报

"Pro.Puppet 教程是针对系统管理员、实施者和系统集成者的权威指南，涵盖了Puppet配置管理工具的各个方面，旨在帮助读者最大化和定制Puppet在他们环境中的功能。本书由James Turnbull和Jeffrey McCune撰写，内容包括Puppet的入门、主机构建、环境管理、可扩展性、外部化配置、配置存储、控制台使用、工具集成、报告、Facter和Puppet的扩展以及Marionette Collective的介绍。" 在"Pro.Puppet 教程"中，作者深入浅出地介绍了Puppet这一强大的自动化配置管理工具。首先，"Getting Started with Puppet"章节将引导读者了解Puppet的基础知识，包括安装、配置和运行Puppet，以及如何定义和应用资源类型来管理IT基础设施。 "Building Hosts with Puppet"章节讲解了如何使用Puppet构建和管理服务器主机，包括定义主机的 Puppet 类，管理软件包、服务、文件和用户等系统资源。 "Working with Environments"章节探讨了如何利用Puppet的环境功能来管理不同开发、测试和生产环境的配置，确保代码在不同阶段的一致性和安全性。 "Puppet Scalability"章节讨论了Puppet在大规模环境下的扩展性问题，包括代理节点的管理、集中式报告和分布式数据存储等策略，以确保在大型IT环境中高效运行。 "Externalizing Puppet Configuration"章节介绍如何将Puppet配置外部化，使得配置管理更加灵活和可维护，例如使用Hiera进行数据分层。 "Exporting and Storing Configuration"章节讲解了如何导出和存储配置，确保配置的版本控制和备份，同时提高团队协作效率。 "Puppet Consoles: Puppet Dashboard and The Foreman"章节介绍了两个可视化的Puppet管理工具，它们提供了对Puppet部署的监控和报告，帮助管理员更好地理解系统的状态。 "Tools and Integration"章节涵盖了Puppet与其他工具和服务的集成，如CI/CD工具、监控系统和日志管理，增强整个IT生态系统的互操作性。 "Reporting with Puppet"章节详细阐述了Puppet的报告功能，如何收集和分析Puppet运行的日志，以便于故障排查和性能优化。 "Extending Facter and Puppet"章节介绍了Facter——Puppet的事实收集工具，以及如何扩展它以获取更多系统信息，并将其用于Puppet的配置决策。 "Marionette Collective"章节则探讨了Puppet的自动化框架Marionette，用于构建更复杂的自动化工作流程和管理逻辑。最后，附录"Working with Puppet"提供了一些额外的实践指导和高级技巧，帮助读者深入掌握Puppet的使用。 "Pro.Puppet 教程"是一本全面的Puppet学习资源，适合希望提升运维管理水平，通过自动化工具提高效率的IT专业人员。通过学习这本书，读者不仅可以掌握Puppet的核心功能，还能了解到如何在实际工作中有效地应用这些知识，实现高效的IT基础设施管理。

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页未读，继续阅读

ehongping

粉丝: 0

精通Puppet：权威指南

Pro.Puppet.pdf

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

Artifactory服务器配置教程及沙箱项目管理

AdvanTrol-Pro软件自动化部署教程：提升IT效率的关键技术一步到位

【Tesseral-Pro云计算整合术】：打造灵活资源管理的高级技巧

ALINT-PRO与持续集成的融合：实现DevOps流程的自动化检查

【VMware Workstation高手教程】：一步到位解决快捷方式创建难题

【大数据课设】p105出租车数据可视化分析-大数据-实训大作业.zip

TypeScript 入门教程

人脸识别_课堂考勤_OpenCV_服务端系统_1741777828.zip

最新资源