# Grouping modules by purpose

**URL:** <https://forum.ansible.com/t/grouping-modules-by-purpose/21215>\
**Category:** Ansible Project\
**Created:** [April 20, 2016, 4:55am UTC](https://forum.ansible.com/t/grouping-modules-by-purpose/21215 "2016-04-20T04:55:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Azer\_Huseyin](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@Azer\_Huseyin](https://forum.ansible.com/u/Azer_Huseyin)\
**Post date:** [April 20, 2016, 4:55am UTC](https://forum.ansible.com/t/grouping-modules-by-purpose/21215/1 "2016-04-20T04:55:47Z")

</div>

Hi ,

I am investigating ansible to automate our system configuration/management tasks currently performed using mostly shell scripts. We mostly definitely will have to write custom modules, but I noticed that ansible doesn’t have module hierarchy. Is there a way to group related modules under “umbrella” name in OOP style ?

Using core file module as example, instead of single “file” module with “state” parameter, having modules “file.copy”, “file.link”, “file.rename” etc.

Thanks!

BR/Azer

---

<div class="post-metadata">

**Author:** ![Maksims\_Juvcenko](https://avatars.discourse-cdn.com/v4/letter/m/edb3f5/32.png) [@Maksims\_Juvcenko](https://forum.ansible.com/u/Maksims_Juvcenko)\
**Post date:** [May 28, 2016, 12:00pm UTC](https://forum.ansible.com/t/grouping-modules-by-purpose/21215/2 "2016-05-28T12:00:18Z")

</div>

Hi,

I wanted to ask same question.  
Seems that Ansible needs support of some sort of task grouping or name-spacing. Version 2.1 already has over 500 tasks in the single namespace, which affects readability of existing scripts/playbooks - short task names are obscure and long names do not follow common pattern. In my opinion it can become a huge usability problem when number of tasks will grow over 1k (which I believe can happen this year). Having some structure like in documentation [http://docs.ansible.com/ansible/modules\_by\_category.html](http://docs.ansible.com/ansible/modules_by_category.html) would already be a big help.