This is where the module documentation is essential. The items under the dnf item are specific to the dnf module.
How to install winrar software how to#
Like with a command in a Linux terminal, knowing how to invoke an Ansible module is half the battle. In this example, I used dnf because I wrote the playbook on Fedora Linux. You must adjust the module name you use to match the distribution you're using. Open site.yml in your favorite text editor, and add this: The file that serves as the Ansible playbook can be named anything you like, but it's traditional to name it site.yml: $ touch ~ /install_packages /site.yml For now, just create a directory called install_packages or similar: $ mkdir ~ /install_packages Ansible can run with just a configuration file written in YAML, but if you want to expand your playbook later, you can control Ansible by how you lay out your directories and files. This isn't strictly necessary, but it's a good idea to establish the habit. The first step is to create a directory representing your playbook. This gets you started with something you can test and verify as you go, and you can expand your work for your other computers later. If you're writing on Elementary OS, use the apt module, and so on. For instance, if you're going to write your Ansible instructions (a "playbook," as it's called in Ansible) on a laptop running Fedora, start with the dnf module.
To begin, choose the package manager on your local computer. For package management, the Packaging modules section contains a module for nearly any system with a package manager. With a little searching, you're very likely to find a module for whatever you need. The index is listed primarily by category. When you're using Ansible, you refer to the Ansible module index. How do you find the one you need for a given task? In Linux, you might look in your Applications menu or in /usr/bin to discover new applications to run. The number of Ansible modules can be overwhelming. Of course, installing and maintaining applications on a Linux machine is a basic task for Ansible, and it means you can list what you want across all computers under your care. I used to use a text list of packages to keep my systems more or less synchronized: I'd list the packages installed on my laptop and then cross-reference that with my desktop, or between one server and another server, making up for any difference manually. They provide solutions to specific problems, and one common task when maintaining computers is keeping all the ones you use updated and consistent. Ansible modules are, in a way, what commands are to a Linux computer. As is often the case with extensible frameworks, Ansible has limited use on its own, with its real power dwelling in its many modules.
0 kommentar(er)
