IDUG EMEA 2024

I already showed howto work on Db2-Databases with Ansible and Python in previous IDUG sessions. This time around I'm going to guide you through the process on how to use Db2 as a configuration repository for Ansible. Runtime configuration for Ansible playbooks is usually done by the ansible inventory (usually requires a pull request) and, for runtime configuration, "extra-vars". This can be cumbersome in large environments and does not bear much flexibility. The result is usually an increase of AWX/Ansible-Tower templates for different configurations and targets. Furthermore, the templates (and surveys) get increasingly complex and uncomfortable to handle. Keeping runtime configuration data in a centralized database gives ample oportunity to create and maintain arbitrarily complex runtime configurations in one or multiple Databases with SQL so that the user does not need to know anything about Ansible at all, minimizing operational overhead.I will show how to implement this with the help of a few lines of python code. Live-elements will be pre-recorded if needed. Code will be available on GitHub.