Ansible for DevOps: 英文完整版电子书，带书签

Ansible

需积分: 50 39 浏览量更新于2024-07-20 收藏 3.3MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Ansible for DevOps 是一本关于自动化运维的英文书籍，由Jeff Geerling撰写，旨在为人类提供服务器和配置管理的解决方案。这本书在2015年10月4日出版， ISBN号为978-0-9863934-0-2。该版本是通过Leanpub平台发布的，该平台支持作者使用轻量级工具进行多次迭代以获取读者反馈，并根据反馈调整内容。" Ansible是一种强大的自动化工具，尤其在DevOps领域中广泛使用，它简化了基础设施的配置和管理任务。本书《Ansible for DevOps》深入浅出地介绍了如何利用Ansible进行服务器和配置管理。通过阅读这本书，读者可以学习到： 1. Ansible基础知识：了解Ansible的工作原理，包括它的主机清单、模块、任务、角色和playbook等核心概念。 2. 安装和配置Ansible：学习如何在本地或远程环境中设置Ansible控制节点，以及如何配置Ansible与目标主机的通信方式，如使用SSH密钥对认证。 3. 配置管理：学习如何使用Ansible的配置管理功能来部署和更新服务器上的软件，包括操作系统、服务、应用和其他配置项。 4. 自动化工作流：探索如何构建自动化工作流，将多个Ansible任务串联起来，实现从代码仓库拉取、构建、测试到部署的全自动化流程。 5. 角色和playbooks：掌握如何编写和复用Ansible角色，以及如何组织和执行playbooks，实现高效和可维护的配置管理。 6. 动态 inventories：学习如何使用动态inventory源，如EC2、OpenStack等云环境，以便更好地管理大规模分布式系统。 7. 模块和插件：了解Ansible的内置模块，以及如何创建自定义模块和插件，以扩展Ansible的功能。 8. 协作和版本控制：理解如何将Ansible集成到团队协作环境中，如使用Git进行版本控制，确保代码的整洁和一致性。 9. 安全实践：学习Ansible的安全最佳实践，包括最小权限原则、加密敏感数据和限制网络访问等。 10. 监控和日志：了解如何通过Ansible集成监控工具（如Nagios、Prometheus）和日志收集系统（如Logstash、Elasticsearch），以确保系统的稳定性和可追溯性。 11. 持续集成与持续部署(CI/CD)：探讨如何将Ansible与Jenkins、Travis CI等CI/CD工具结合，实现快速、可靠的软件发布流程。本书适合有一定Linux和系统管理经验的DevOps工程师、系统管理员、运维人员以及希望提升自动化能力的开发人员。通过书中丰富的实例和实战指导，读者可以逐步掌握Ansible的使用技巧，提高工作效率，实现高效的运维自动化。

资源详情

资源推荐

Preface iv

Tip asides will give tips for deepening your understanding or optimizing your use of

Ansible.

When displaying commands run in a terminal session, if the commands are run under your

normal/non-root user account, the commands will be prefixed by the dollar sign ($). If the commands

are run as the root user, they will be prefixed with the pound sign (#).

Please help improve this book!

New revisions of this book are published on a regular basis. If you think a particular section needs

improvement or find something missing, please contact me via Twitter (@geerlingguy²), Google+³,

a comment on this book’s Feedback page on LeanPub⁴, or whatever method is convenient for you.

All known issues with Ansible for DevOps will be aggregated on the book’s online Errata⁵ page, as

well as in the book’s Changelog (for the benefit of those who purchase the book on a platform that

allows frequent releases between editions).

About the Author

Jeff Geerling⁶ is a developer who has worked in programming and devops for companies with

anywhere between one to thousands of servers. He also manages many virtual servers for services

offered by Midwestern Mac, LLC⁷ and has been using Ansible to manage infrastructure since early

2013.

²https://twitter.com/geerlingguy

³https://plus.google.com/+JeffGeerling

⁴https://leanpub.com/ansible-for-devops/feedback

⁵http://www.ansiblefordevops.com/errata

⁶http://jeffgeerling.com/

⁷http://www.midwesternmac.com/

http://freepdf-books.com

Introduction

In the beginning, there were sysadmins

Since the beginning of networked computing, deploying and managing servers reliably and

efficiently has been a challenge. Historically, system administrators have typically been walled off

from the developers and users who interact with the systems they administer, and so they have had

to manage servers by hand, installing software, changing configurations, and administering services

on individual servers.

As data centers grew, and hosted applications became more complex, administrators realized they

couldn’t scale their manual systems management as fast as the applications they were enabling.

That’s why server provisioning and configuration management tools came to flourish.

Server virtualization brought large-scale infrastructure management to the fore, and the number of

servers managed by one admin (or by a small team of admins), has grown by an order of magnitude.

Instead of deploying, patching, and destroying every server by hand, admins now are expected to

bring up new servers, either automatically or with minimal intervention. Large-scale IT deployments

now may involve hundreds or thousands of servers; in many of the largest environments, server

provisioning, configuration, and decommissioning are all entirely automated.

Modern infrastructure management

As the systems that run applications become an ever more complex and integral part of the

software they run, application developers themselves have begun to integrate their work more fully

with operations personnel. In many companies, development and operations work is almost fully

integrated. Indeed, this integration is a requirement for modern test-driven application design.

As a software developer by trade, and a sysadmin by necessity, I have seen the power in uniting

development and operations—more commonly referred to now as DevOps. When developers begin

to think of infrastructure as part of their application, stability and performance become normative.

When sysadmins (most of whom have intermediate to advanced knowledge of the applications and

languages being used on servers they manage) work tightly with developers, development velocity

is improved, and more time is spent doing ‘fun’ activities like performance tuning, experimentation,

and getting things done, and less time putting out fires.

http://freepdf-books.com

Introduction vi

DevOps is a loaded word; some people argue that using the word to identify both the

movement of development and operations working more closely to automate infrastruc-

ture-related processes, and the personnel who skew slightly more towards the system

administration side of the equation, dilutes the word’s meaning. I think the word has come

to be a rallying cry for the employees who are dragging their startups, small businesses,

and enterprises into a new era of infrastructure growth and stability. I’m not too concerned

that the term has become more of a catch-all for modern infrastructure management. My

advice: spend less time arguing over the definition of the word, and more time making it

mean something to you.

Ansible and Ansible, Inc.

Ansible was released in 2012 by Michael DeHaan (@laserllama⁸ on Twitter), a developer who

has been working with configuration management and infrastructure orchestration in one form

or another for many years. Through his work with Puppet Labs and RedHat (where he worked

on Cobbler⁹, a configuration management tool and Func¹⁰, a tool for communicating commands

to remote servers), and some other projects¹¹, he experienced the trials and tribulations of many

different organizations and individual sysadmins on their quest to simplify and automate their

infrastructure management operations.

Additionally, Michael found many shops were using separate tools¹² for configuration management

(Puppet, Chef, cfengine), server deployment (Capistrano, Fabric), and ad-hoc task execution (Func,

plain SSH), and wanted to see if there was a better way. Ansible wraps up all three of these features

into one tool, and does it in a way that’s actually simpler and more consistent than any of the other

task-specific tools!

Ansible aims to be:

1. Clear - Ansible uses a simple syntax (YAML) and is easy for anyone (developers, sysadmins,

managers) to understand. APIs are simple and sensible.

2. Fast - Fast to learn, fast to set up—especially considering you don’t need to install extra agents

or daemons on all your servers!

3. Complete - Ansible does three things in one, and does them very well. Ansible’s ‘batteries

included’ approach means you have everything you need in one complete package.

4. Efficient - No extra software on your servers means more resources for your applications.

Also, since Ansible modules work via JSON, Ansible is extensible with modules written in a

programming language you already know.

⁸https://twitter.com/laserllama

⁹http://www.cobblerd.org/

¹⁰https://fedorahosted.org/func/

¹¹http://www.ansible.com/blog/2013/12/08/the-origins-of-ansible

¹²http://highscalability.com/blog/2012/4/18/ansible-a-simple-model-driven-configuration-management-and-c.html

http://freepdf-books.com

Introduction vii

5. Secure - Ansible uses SSH, and requires no extra open ports or potentially-vulnerable daemons

on your servers.

Ansible also has a lighter side that gives the project a little personality. As an example, Ansible’s

major releases are named after Van Halen songs (e.g. 1.4 was named after 1980’s “Could This Be

Magic”, and 1.5 after 1986’s “Love Walks In”). Additionally, Ansible will use cowsay, if installed,

to wrap output in an ASCII cow’s speech bubble (this behavior can be disabled in Ansible’s

configuration).

Ansible, Inc.¹³ was founded by Saïd Ziouani (@SaidZiouani¹⁴ on Twitter) and Michael DeHaan,

and oversees core Ansible development and provides services (such as Automation Jump Start¹⁵)

and extra tooling (such as Ansible Tower¹⁶) to organizations using Ansible. Hundreds of individual

developers have contributed patches to Ansible, and Ansible is the most starred infrastructure

management tool on GitHub (with over 10,000 stars as of this writing). Ansible, Inc. has proven

itself to be a good steward and promoter of Ansible so far, and I see no indication of this changing

in the future.

Ansible Examples

There are many Ansible examples (playbooks, roles, infrastructure, configuration, etc.) throughout

this book. Most of the examples are in the Ansible for DevOps GitHub repository¹⁷, so you can

browse the code in its final state while you’re reading the book. Some of the line numbering may

not match the book exactly (especially if you’re reading an older version of the book!), but I will try

my best to keep everything synchronized over time.

Other resources

We’ll explore all aspects of using Ansible to provision and manage your infrastructure in this book,

but there’s no substitute for the wealth of documentation and community interaction that make

Ansible great. Check out the links below to find out more about Ansible and discover the community:

• Ansible Documentation¹⁸ - Covers all Ansible options in depth. There are few open source

projects with documentation as clear and thorough.

• Ansible Glossary¹⁹ - If there’s ever a term in this book you don’t seem to fully understand,

check the glossary.

¹³http://www.ansible.com/

¹⁴https://twitter.com/SaidZiouani

¹⁵http://www.ansible.com/services

¹⁶http://www.ansible.com/tower

¹⁷https://github.com/geerlingguy/ansible-for-devops

¹⁸http://docs.ansible.com/

¹⁹http://docs.ansible.com/glossary.html

http://freepdf-books.com

剩余315页未读，继续阅读

itmonkey2001

粉丝: 0
资源: 11

Ansible for DevOps: 英文完整版电子书，带书签

Ansible-Tower-3.0

Ansible 2 Cloud Automation Cookbook

linux-AnsibleRoleAWX开源版本AnsibleTower

PFC3D初学者指南：Ansible for DevOps英文版配合示例解析

Ansible for DevOps - 2018 Edition

Ansible for DevOps：服务器与配置管理指南

《Ansible for DevOps》2018-01-04版：服务器与配置管理

Vagrant和Ansible结合实践：完全自动化的开发环境

DevOps文化与实践

DevOps与持续集成

DevOps理念与实践

通过Ansible实现多主机并行部署

implementing devops 2with ansible

有什么devops书籍推荐吗

ansible自学资料

ansible jinja2 for

docker ansible

ansible wait_for 多端口

kolla-ansible 对应 ansible版本

最新资源