![]() ![]() However, you may wish to test this scenario locally to prepare for the eventual Red Hat Enterprise Linux 8 GA release. Testing Red Hat Enterprise Linux 8 Beta as an Ansible control nodeĪnsible Engine does not support using a Red Hat Enterprise Linux 8 Beta system as a control node in a production setting. In Ansible 2.8, Ansible will automatically discover the best ansible_python_interpreter definition, and you will not need to set the python interpreter like this. Once you’ve set the correct python interpreter, you can run Ansible to manage this Red Hat Enterprise Linux 8 Beta system: ansible RHEL8hosts -m yum -a “name=bash state=installed” Since Ansible will be automating systems-level tasks, this will be our target. This example directs Ansible to use the Red Hat Enterprise Linux 8 Platform Python, which is meant for systems-level tooling, rather than the standard python interpreter. ansible_python_interpreter=/usr/libexec/platform-python To set the python interpreter in your inventory with a host_var: You must do this on every Red Hat Enterprise Linux 8 node just as you would for any Python3 enabled host. ![]() You can define the python interpreter Ansible should use on your Red Hat Enterprise Linux 8 Beta nodes with an inventory host_var, a group_var, a play, or an ad-hoc command. Setting the Python interpreter on Red Hat Enterprise Linux 8 Beta managed nodes When Ansible 2.8 is released, we plan for Ansible to automatically discover the correct Python to use on Red Hat Enterprise Linux 8 Beta hosts. However, with Ansible 2.7 managing Red Hat Enterprise Linux 8 Beta, you must define which Python to use. Ansible allows you to manage a huge range of hosts and devices, from legacy systems to beta-release testing platforms, by working with both Python 2 and Python 3. Before you can manage Red Hat Enterprise Linux 8 Beta nodes with Ansible 2.7, though, you need to set the appropriate python interpreter. ![]() Red Hat is proud to announce that Ansible supports managing Red Hat Enterprise Linux 8 Beta hosts.
0 Comments
Leave a Reply. |