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

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

"Ansible for DevOps - 服务器与配置管理指南" 本书《Ansible for DevOps》由Jeff Geerling撰写，专注于服务器和配置管理，适用于人类操作。它旨在为DevOps从业者提供全面的Ansible知识，帮助他们利用轻量级工具进行持续迭代，以获取用户反馈，并根据反馈调整内容，直到找到合适的解决方案。这本书是在Leanpub平台上发布的，该平台支持作者进行精益出版，即在不断更新和完善中发布电子书。 Ansible是一款自动化工具，主要用于IT基础设施的配置管理和应用部署。它采用无代理架构，无需在目标机器上安装额外软件，通过SSH（Secure Shell）进行通信。其主要特点是简单易用、可扩展性强，能够简化复杂的IT运维任务。书中可能涵盖了以下关键知识点： 1. **Ansible基础知识**：包括Ansible的工作原理、安装与配置，以及如何创建第一个Playbook，这是Ansible中的核心配置文件。 2. **Inventory管理**：介绍如何组织和管理你的IT资源列表，以便于在不同的环境中应用配置。 3. **Playbooks**：详细讲解Playbook的语法和结构，如何编写有效的Playbook来执行自动化任务，如系统配置、软件安装、服务管理等。 4. **模块化设计**：Ansible拥有大量的内置模块，如file、package、service等，用于处理各种任务。书中会解释如何使用这些模块并自定义模块。 5. **角色（Roles）**：Ansible的角色允许你将相关配置和任务组织在一起，便于复用和维护。这部分内容会介绍如何创建和使用角色。 6. **变量和模板**：学习如何使用变量动态地改变配置，以及使用Jinja2模板语言来创建动态配置文件。 7. **Ansible Galaxy**：这是一个社区共享Ansible角色和集合的地方，书中可能会讲述如何利用Galaxy导入和分享资源。 8. **Ansible Tower**：对于企业级环境，可能还会涉及Ansible Tower的使用，它是Ansible的Web界面版本，提供了更高级的功能，如作业调度、权限控制和审计日志。 9. **持续集成与交付**：结合DevOps实践，探讨如何将Ansible整合到CI/CD（持续集成/持续部署）流程中。 10. **最佳实践和案例研究**：书中可能会分享实际项目中的经验，提出使用Ansible的最佳实践，以及解决常见问题的策略。通过阅读本书，读者可以掌握Ansible的基本操作，理解其在DevOps环境中的重要地位，以及如何有效地使用Ansible提升IT运维效率和一致性。这本书适合运维人员、系统管理员、DevOps工程师和任何有兴趣使用自动化工具优化工作流程的人士。

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/

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.

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

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

剩余315页未读，继续阅读

舟人不住

粉丝: 2
资源: 10

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

Ansible-For-DevOps.pdf

Configuration Management Code Block-开源

Ansible-for-DevOps-Server-and-configuration-man-316页

Ansible_Role:---这里所有的角色都已上传---

ansible-for-devops-2018-414页

ansible-for-devops-2016-391页

ansible_collection_falcon：-正在开发中–通过Ansible在Linux，Windows和OSX上安装和配置CrowdStrike的Falcon传感器

ansible-for-devops-in-AWS:在AWS的Ansible for Devops中复制所有项目以直观地查看最终产品是否有效

ansible_output_parser-0.0.5-py3-none-any.whl.zip

ansible_output_parser-0.0.3-py3-none-any.whl.zip

最新资源