Unsolved
3 Posts
0
588
November 9th, 2020 06:00
Best practice to organize external module utils
Hi all, we're currently in the process of rolling out several automations across an account. Since this is my first time working with a lot of external modules (brocade, IBM, EMC etc.) I'm not quite sure how to organize the folder structures. For exmaple the official Brocade module requires several files to be copied over to "module_utils" additionally to the standard module path. Is it best practice to just take those utility files (mostly scripts) and paste them over there? It seems like quite some hassle to update and troubleshoot future releases of the ansible modules for example. We transferred the entire ansible directory over to /usr/share/ on the host and most of the modules live in /usr/share/ansible/plugins/modules How are you guys dealing with this or are you more or less pushing it all into the "ansible/plugins/module_utils" directory?
FoolInTheRain
123 Posts
0
November 9th, 2020 08:00
Hi Jopaszek2,
You are correct, at this time, each of the Dell EMC Ansible platforms that are currently supported have a Product Guide with specific directories that you need to move files into as part of the installation.
I am told that engineering is "...looking into creating collections for all the modules for all the platforms", which I believe will help address what you are looking for.
lhernand3z
8 Posts
0
November 10th, 2020 15:00
I've also heard that Ansible collections is the way to go for best practices. I think Ansible started with collections after 2.8 but not 100% sure.
According to our Ansible resource, Isilon and VMAX modules do provide collection structure but not the VPLEX. I would imagine that other vendors are going to follow the collection thread, I did hear from RedHat that it's the best way to manage their core modules