{"id":35513,"date":"2019-10-31T22:04:46","date_gmt":"2019-10-31T19:04:46","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ansible-obnovleniya-v-klyuchevyh-resheniyah-dlya-avtomatizatsii-vashego-mira\/"},"modified":"2019-10-31T22:04:46","modified_gmt":"2019-10-31T19:04:46","slug":"ansible-obnovleniya-v-klyuchevyh-resheniyah-dlya-avtomatizatsii-vashego-mira","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/ansible-obnovleniya-v-klyuchevyh-resheniyah-dlya-avtomatizatsii-vashego-mira","title":{"rendered":"Ansible: updates in key solutions for automating your world","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The Ansible community continuously delights with new content\u2014plugins and modules\u2014creating a lot of new work for those involved in maintaining Ansible, as new code needs to be rapidly integrated into repositories. Meeting deadlines isn't always possible, and the launch of some fully ready-to-release products is postponed until the next official version of Ansible Engine. Until recently, the end user had only one way to obtain new Ansible content\u2014along with a new version of Ansible Engine.<\/p>\n

\"Ansible:
\n
\nTo alleviate this inconvenience, the Ansible community has begun working on more flexible options for creating and obtaining content.
\n<\/a><\/noindex><\/p>\n

Red Hat Ansible Engine 2.8: on the way to new methods of handling Ansible content<\/h3>\n

\nIn response to user requests, changes regarding content handling appeared in Ansible Engine 2.8, not included in the official release.<\/b>. These changes will enable a new method of delivering content to users that will not depend on those supporting Ansible in managing both Ansible content and the platform's own code.<\/p>\n

It is planned that in future releases, content Creators will be able to deliver it in the form of special packages, called Collections, which can be installed in the appropriate execution place on the Ansible control node or the managed node. The creator of the collection will specify execution details directly in the package using roles and playbooks. Thanks to the aforementioned changes in Ansible Engine, collections will become one of the tools that allow decoupling content release from the release of official versions of Ansible Engine.<\/b>.<\/p>\n

The new Become construct<\/h4>\n

\nThe Become construct has been around for a while, but starting from version 2.8, the word BECOME is used by default in Ansible Engine to prompt for a password when elevating privileges (sudo privileges on *nix systems or enable mode on network devices). In other words, BECOME is now the standard privilege escalation tool that manages interactions with the target system on its own.<\/p>\n

Here is an example of its usage:<\/p>\n

ansible-playbook --become --ask-become-pass site.yml\nBECOME password:\n<\/code><\/pre>\n
\nAdditionally, Ansible Engine 2.8 introduced the BECOME plugin, which works like doas on Linux and runas on Windows, allowing actions to be executed as a specified user. For privilege escalation on network devices, the become plugin enable is used.<\/p>\n
Searching for the Python interpreter<\/h4>\n
\nYou may have encountered an error like this:<\/p>\n
\/usr\/bin\/python: bad interpreter: No such file or directory\n<\/code><\/pre>\n
\nThe issue is that in previous versions of Ansible Engine, it was assumed that the main (default) Python interpreter was located in the folder \/usr\/bin\/python. Starting with version 2.8, Ansible searches for the interpreter on each target system, first matching against the table of paths and executable names of the main Python interpreter in various distributions, and then using ordered lists of fallback interpreters; see more in the Porting Guide to Ansible 2.8<\/a><\/noindex>.<\/p>\n
Retry files are no longer created by default<\/h4>\n
\nHave you spent a long time searching your disk for .retry files? If you've been using Ansible for a while, there are likely many of them, and they just take up valuable space. Starting from version 2.8, Ansible Engine no longer creates these files by default (this can be reverted by editing the default ansible.cfg file).<\/p>\n
Updated Play Recap<\/h4>\n
\nExcerpt from Porting Guides to Ansible 2.8<\/a><\/noindex>:<\/p>\n
Play Recap now counts tasks with statuses ignored and rescued, as well as ok, changed, unreachable, failed, and skipped, thanks to two new statistics counters in the default callback plugin. Failed tasks that have the flag ignore_errors: yes are counted as ignored. Failed tasks that subsequently executed the rescue section are counted as rescued. Note that unlike previous versions of Ansible, rescued tasks are no longer counted as failed.<\/p><\/blockquote>\n
\nAnd in the Play Recap table at the end of playbook execution, additional columns for skipped, rescued, and ignored have been added for hosts:<\/p>\n
\"Ansible:<\/p>\n
Clouds and Containers<\/h4>\n
\nVersion 2.8 features improvements and additions in cloud and container modules for working with Amazon Web Services, Microsoft Azure, Google Cloud, Digital Ocean, podman<\/a><\/noindex> and kubevirt<\/a><\/noindex>. It is also worth noting that TOML files can now be used as an inventory source.<\/p>\n
Paramiko<\/h4>\n
\nAre you using Red Hat Ansible Network Automation? Ansible Engine 2.8 no longer includes paramiko and does not depend on it. By default, Ansible Engine uses ssh. If you need paramiko, it can be installed with the command pip install paramiko.<\/p>\n
If you need support for using paramiko within the Red Hat subscription, refer to the knowledge base article. Paramiko package missing after new Ansible Engine installations.<\/a><\/noindex>.<\/p>\n
Thus, the latest version of Red Hat Ansible Engine has been enhanced with a significant list of improvements and changes, which can be reviewed in detail. here<\/a><\/noindex>.<\/b><\/p>\n
Red Hat Ansible Tower 3.5: More Automation.<\/h3>\n
\nSince the end of May, the new version of Red Hat Ansible Tower 3.5 has been available, offering several significant improvements for automation, which we will discuss if you haven't checked them out yet.<\/p>\n
So, first the key points:<\/p>\n