From 8300fe3517a2d8b130a5b866c483b43fd5d5f9b0 Mon Sep 17 00:00:00 2001
From: jdh8383 <4565726+jdh8383@users.noreply.github.com>
Date: Thu, 7 Mar 2019 10:51:05 +0800
Subject: [PATCH] Update and rename sources/tech/20180202 Tips for success when
getting started with Ansible.md to translated/tech/20180202 Tips for success
when getting started with Ansible.md
---
...ccess when getting started with Ansible.md | 75 -------------------
...ccess when getting started with Ansible.md | 71 ++++++++++++++++++
2 files changed, 71 insertions(+), 75 deletions(-)
delete mode 100644 sources/tech/20180202 Tips for success when getting started with Ansible.md
create mode 100644 translated/tech/20180202 Tips for success when getting started with Ansible.md
diff --git a/sources/tech/20180202 Tips for success when getting started with Ansible.md b/sources/tech/20180202 Tips for success when getting started with Ansible.md
deleted file mode 100644
index 2b70c04e4d..0000000000
--- a/sources/tech/20180202 Tips for success when getting started with Ansible.md
+++ /dev/null
@@ -1,75 +0,0 @@
-jdh8383 is translating.
-
-Tips for success when getting started with Ansible
-======
-
-
-
-Ansible is an open source automation tool used to configure servers, install software, and perform a wide variety of IT tasks from one central location. It is a one-to-many agentless mechanism where all instructions are run from a control machine that communicates with remote clients over SSH, although other protocols are also supported.
-
-While targeted for system administrators with privileged access who routinely perform tasks such as installing and configuring applications, Ansible can also be used by non-privileged users. For example, a database administrator using the `mysql` login ID could use Ansible to create databases, add users, and define access-level controls.
-
-Let's go over a very simple example where a system administrator provisions 100 servers each day and must run a series of Bash commands on each one before handing it off to users.
-
-
-
-This is a simple example, but should illustrate how easily commands can be specified in yaml files and executed on remote servers. In a heterogeneous environment, conditional statements can be added so that certain commands are only executed in certain servers (e.g., "only execute `yum` commands in systems that are not Ubuntu or Debian").
-
-One important feature in Ansible is that a playbook describes a desired state in a computer system, so a playbook can be run multiple times against a server without impacting its state. If a certain task has already been implemented (e.g., "user `sysman` already exists"), then Ansible simply ignores it and moves on.
-
-### Definitions
-
- * **Tasks:**``A task is the smallest unit of work. It can be an action like "Install a database," "Install a web server," "Create a firewall rule," or "Copy this configuration file to that server."
- * **Plays:**``A play is made up of tasks. For example, the play: "Prepare a database to be used by a web server" is made up of tasks: 1) Install the database package; 2) Set a password for the database administrator; 3) Create a database; and 4) Set access to the database.
- * **Playbook:**``A playbook is made up of plays. A playbook could be: "Prepare my website with a database backend," and the plays would be 1) Set up the database server; and 2) Set up the web server.
- * **Roles:**``Roles are used to save and organize playbooks and allow sharing and reuse of playbooks. Following the previous examples, if you need to fully configure a web server, you can use a role that others have written and shared to do just that. Since roles are highly configurable (if written correctly), they can be easily reused to suit any given deployment requirements.
- * **Ansible Galaxy:**``Ansible [Galaxy][1] is an online repository where roles are uploaded so they can be shared with others. It is integrated with GitHub, so roles can be organized into Git repositories and then shared via Ansible Galaxy.
-
-
-
-These definitions and their relationships are depicted here:
-
-
-
-Please note this is just one way to organize the tasks that need to be executed. We could have split up the installation of the database and the web server into separate playbooks and into different roles. Most roles in Ansible Galaxy install and configure individual applications. You can see examples for installing [mysql][2] and installing [httpd][3].
-
-### Tips for writing playbooks
-
-The best source for learning Ansible is the official [documentation][4] site. And, as usual, online search is your friend. I recommend starting with simple tasks, like installing applications or creating users. Once you are ready, follow these guidelines:
-
- * When testing, use a small subset of servers so that your plays execute faster. If they are successful in one server, they will be successful in others.
- * Always do a dry run to make sure all commands are working (run with `--check-mode` flag).
- * Test as often as you need to without fear of breaking things. Tasks describe a desired state, so if a desired state is already achieved, it will simply be ignored.
- * Be sure all host names defined in `/etc/ansible/hosts` are resolvable.
- * Because communication to remote hosts is done using SSH, keys have to be accepted by the control machine, so either 1) exchange keys with remote hosts prior to starting; or 2) be ready to type in "Yes" to accept SSH key exchange requests for each remote host you want to manage.
- * Although you can combine tasks for different Linux distributions in one playbook, it's cleaner to write a separate playbook for each distro.
-
-
-
-### In the final analysis
-
-Ansible is a great choice for implementing automation in your data center:
-
- * It's agentless, so it is simpler to install than other automation tools.
- * Instructions are in YAML (though JSON is also supported) so it's easier than writing shell scripts.
- * It's open source software, so contribute back to it and make it even better!
-
-
-
-How have you used Ansible to automate your data center? Share your experience in the comments.
-
---------------------------------------------------------------------------------
-
-via: https://opensource.com/article/18/2/tips-success-when-getting-started-ansible
-
-作者：[Jose Delarosa][a]
-译者：[译者ID](https://github.com/译者ID)
-校对：[校对者ID](https://github.com/校对者ID)
-
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
-
-[a]:https://opensource.com/users/jdelaros1
-[1]:https://galaxy.ansible.com/
-[2]:https://galaxy.ansible.com/bennojoy/mysql/
-[3]:https://galaxy.ansible.com/xcezx/httpd/
-[4]:http://docs.ansible.com/
diff --git a/translated/tech/20180202 Tips for success when getting started with Ansible.md b/translated/tech/20180202 Tips for success when getting started with Ansible.md
new file mode 100644
index 0000000000..395a46a5e1
--- /dev/null
+++ b/translated/tech/20180202 Tips for success when getting started with Ansible.md
@@ -0,0 +1,71 @@
+Ansible 初学者成功指南
+======
+
+
+
+Ansible 是一个开源自动化工具，可以从中央控制节点统一配置服务器、安装软件或执行各种 IT 任务。它采用一对多、无客户端的机制，从控制节点上通过 SSH 发送指令给远端的客户机来完成任务（当然除了 SSH 外也可以用别的协议）。
+
+Ansible 的主要使用群体是系统管理员，他们经常会周期性地执行一些安装、配置应用的工作。尽管如此，一些非特权用户也可以使用 Ansible，例如数据库管理员就可以通过 Ansible 用 `mysql` 这个用户来创建数据库、添加数据库用户、定义访问权限等。
+
+让我们来看一个简单的使用场景，一位系统管理员每天要配置 100 台服务器，并且必须在每台机器上执行一系列 Bash 命令，然后交付给用户。
+
+
+
+这是个简单的例子，但应该能够证明：在 yaml 文件里写好命令然后在远程服务器上运行，是一件非常轻松的事。而且如果运行环境不同，就可以加入判断条件，指明某些命令只能在特定的服务器上运行（如：只在那些不是 Ubuntu 或 Debian 的系统上运行 `yum` 命令）。
+
+Ansible 的一个重要特性是用 playbook 来描述一个计算机系统的最终状态，所以一个 playbook 可以在服务器上反复执行而不影响其最终状态（译者注：即是幂等的）。如果某个任务已经被实施过了（如，“用户 `sysman` 已经存在”），那么 Ansible 就会忽略它继续执行后续的任务。
+
+### 定义
+
+ * **任务：** task 是工作的最小单位，它可以是个动作，比如“安装一个数据库服务”、“安装一个 web 服务器”、“创建一条防火墙规则”或者“把这个配置文件拷贝到那个服务器上去”。
+ * **战术动作：** play 由 task 组成，例如，一个 play 的内容是要：“设置一个数据库，给 web 服务用”，这就包含了如下任务：1）安装数据库包；2）设置数据库管理员密码；3）创建数据库实例；4）为该实例分配权限。
+ * **战术手册：**（译者注：playbook 原指美式橄榄球队的[战术手册][5]） playbook 由 play 组成，一个 playbook 可能像这样：“设置我的网站，包含后端数据库”，其中的 play 包括：1）设置数据库服务器；2）设置 web 服务器。
+ * **角色：** Role 用来保存和组织 playbook，以便分享和再次使用它们。还拿上个例子来说，如果你需要一个全新的 web 服务器，就可以用别人已经写好并分享出来的 role 来设置。因为 role 是高度可配置的（如果编写正确的话），可以根据部署需求轻松地复用它们。
+ * **Ansible 星系:** [Ansible Galaxy][1] 是一个在线仓库，里面保存的是由社区成员上传的 role，方便彼此分享。它与 GitHub 紧密集成，因此这些 role 可以先在 Git 仓库里组织好，然后通过 Ansible Galaxy 分享出来。
+
+
+这些定义以及它们之间的关系可以用下图来描述：
+
+
+
+请注意上面的例子只是组织任务的方式之一，我们当然也可以把安装数据库和安装 web 服务器的 playbook 拆开，放到不同的 role 里。Ansible Galaxy 上最常见的 role 是独立安装配置每个应用服务，你可以参考这些安装 [mysql][2] 和 [httpd][3] 的例子。
+
+### 编写 playbook 的小贴士
+
+学习 Ansible 最好的资源是其[官方文档][4]。另外，像学习其他东西一样，搜索引擎是你的好朋友。我推荐你从一些简单的任务开始，比如安装应用或创建用户。下面是一些有用的指南：
+
+ * 在测试的时候少选几台服务器，这样你的 play 可以执行的更快一些。如果它们在一台机器上执行成功，在其他机器上也没问题。
+ * 总是在真正运行前做一次测试以确保所有的命令都能正确执行（要运行测试，加上 `--check-mode` 参数 ）。
+ * 尽可能多做测试，别担心搞砸。任务里描述的是所需的状态，如果系统已经达到预期状态，任务会被简单地忽略掉。
+ * 确保在 `/etc/ansible/hosts` 里定义的主机名都可以被正确解析。
+ * 因为是用 SSH 与远程主机通信，主控节点必须要接受密钥，所以你面临如下选择：1）要么在正式使用之前就做好与远程主机的密钥交换工作；2）要么在开始管理某台新的远程主机时做好准备输入“Yes”，因为你要接受对方的 SSH 密钥交换请求（译者注：还有另一个不那么安全的选择，修改主控节点的 ssh 配置文件，将 `StrictHostKeyChecking` 设置成“no”）。
+ * 尽管你可以在同一个 playbook 内把不同 Linux 发行版的任务整合到一起，但为每个发行版单独编写 playbook 会更明晰一些。
+
+
+### 总结一下
+
+Ansible 是你在数据中心里实施运维自动化的好选择，因为它：
+
+ * 无需客户端，所以比其他自动化工具更易安装。
+ * 将指令保存在 YAML 文件中（虽然也支持 JSON），比写 shell 脚本更简单。
+ * 开源，因此你也可以做出自己的贡献，让它更加强大！
+
+
+你是怎样使用 Ansible 让数据中心更加自动化的呢？请在评论中分享您的经验。
+
+--------------------------------------------------------------------------------
+
+via: https://opensource.com/article/18/2/tips-success-when-getting-started-ansible
+
+作者：[Jose Delarosa][a]
+译者：[jdh8383](https://github.com/jdh8383)
+校对：[校对者ID](https://github.com/校对者ID)
+
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
+
+[a]:https://opensource.com/users/jdelaros1
+[1]:https://galaxy.ansible.com/
+[2]:https://galaxy.ansible.com/bennojoy/mysql/
+[3]:https://galaxy.ansible.com/xcezx/httpd/
+[4]:http://docs.ansible.com/
+[5]:https://usafootball.com/football-playbook/