Ansible メモ

Ansible concepts

Control node

Any machine with Ansible installed. You can run Ansible commands and playbooks by invoking the ansible or ansible-playbook command from any control node. You can use any computer that has a Python installation as a control node - laptops, shared desktops, and servers can all run Ansible. However, you cannot use a Windows machine as a control node. You can have multiple control nodes.

Ansible がインストールされた、Windows 以外のマシン

Managed nodes

The network devices (and/or servers) you manage with Ansible. Managed nodes are also sometimes called “hosts”. Ansible is not installed on managed nodes.

ネットワークに接続された、Ansible で管理するマシン。
hosts とも表現される

Inventory

A list of managed nodes. An inventory file is also sometimes called a “hostfile”. Your inventory can specify information like IP address for each managed node. An inventory can also organize managed nodes, creating and nesting groups for easier scaling. To learn more about inventory, see the Working with Inventory section.

Managed nodes のリストで、IP アドレスなどの情報を持つ。
Managed nodes のグループ分けや階層分けもする。
hostfile とも表現される

Collections

Collections are a distribution format for Ansible content that can include playbooks, roles, modules, and plugins. You can install and use collections through Ansible Galaxy. To learn more about collections, see Using collections.

ansible-galaxy でインストール・利用することが可能な、playbooks, roles, modules, plungins を含んだ Ansible ファイルの配布形式

Modules

The units of code Ansible executes. Each module has a particular use, from administering users on a specific type of database to managing VLAN interfaces on a specific type of network device. You can invoke a single module with a task, or invoke several different modules in a playbook. Starting in Ansible 2.10, modules are grouped in collections. For an idea of how many collections Ansible includes, take a look at the Collection Index.

Ansible が実行するコードの一まとまりの単位。
各 Module にはそれぞれ特定の目的がある。
Ansible 2.10 から、Modules は Collections としてまとめられている

Tasks

The units of action in Ansible. You can execute a single task once with an ad hoc command.

Ansible アクションの一まとまりの単位。
単一の Task を1回だけアドホックに実行するすることもできる

Playbooks

Ordered lists of tasks, saved so you can run those tasks in that order repeatedly. Playbooks can include variables as well as tasks. Playbooks are written in YAML and are easy to read, write, share and understand. To learn more about playbooks, see Intro to playbooks.

タスクの順序付けされたリストで、これのおかげで順序どおりに複数のタスクを何回でも実行することができる。
タスクと一緒に、変数を保存することもできる。
YAML で書かれている