Hi everyone,
I'm studiying ansible 2.4 behaviour and the impact of multi inventory
possibilities to evaluate the impact on our project.
I tried many things to try to understand how it will work, but I think it
could be clearest with some users stories, and how ansible 2.4 will works.
So this is an exemple of what I found
Imagine that you want deploy a big data cluster with some Mapr, Vertica and
Elastic Stack.
With ansible 2.3 you will have a big hosts.ini inventory with lots of
sections for all the mapr parts, the Vertica ones and the elastic ones.
Very hard to maintain, you have to use limit on your playbook or use tags
to reduce the impact.
With ansible 2.4, you can have this structure
inventories/
- big_data_cluster/
- hosts.ini
- mapr.ini
- vertica.ini
- es.ini
so now, you can target your ansible-playbook with one of the inventories to
reduce the impact, or target all those inventories by specifying the parent
folder :)
It seems a cleanest way to manage the inventories.
So if you have some othe users stories to share guys, it could be nice.
Thx a lot
Cheers,
Winael
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/7015ca25-8f7f-4bdd-8ad4-3e8efb8c6247%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
