This Ansible Tower instance was actually upgraded from 3.7 to 3.8, and during the upgrade, the platform installer takes old inventory sources and converts them to a compatible inventory plugin configuration - therefore there will be a lot of entries in the section to maintain the same outcome for upgraded sources - groups created by default for example - as the old inventory scripts. This specific example is for an Amazon EC2 source in Ansible Tower 3.8:Īs you can see, the “Instance Filters” and “Regions” configuration options are no longer a part of the user interface in Ansible Tower 3.8, but the configuration can now be done in the “Source Variables” section of the inventory source definition. So as an example, the screenshot below shows the source configuration panel difference between an older version of Ansible Tower (3.7 in this case) and the new source configuration in Ansible Tower 3.8. The move to support native inventory plugins allows Red Hat Ansible Automation Platform customers to use all the configuration parameters available through the plugin, as well as supporting any future new plugin features automatically. For example: cloud region and a specific subset of variables you could pass to those inventory scripts surfaced as variables you could pass to the inventory source, which means that new configuration parameters that come with Ansible inventory plugins are not supported in order to maintain compatibility with the old inventory scripts. In previous versions, there were specific inventory plugin configurations based on the old inventory scripts where a specific set of parameters surfaced in Ansible Tower's user interface. This is now possible with an Ansible Tower inventory source that supports tags and provides the vmware_vm_inventory plugin.Īnsible Automation Platform 1.2 brings completely native Ansible inventory plugin support to Ansible Tower 3.8. Red Hat customers have regularly requested the ability to use vCenter Tags in Red Hat Ansible Tower. VMware vCenter Server tags are labels that can be applied to objects like the system’s environment and usage, therefore it is a very useful method of asset management - also making tags a perfect fit in the Ansible world to organize systems in an Ansible inventory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |