# Best place to assign roles to managed nodes

**URL:** <https://forum.ansible.com/t/best-place-to-assign-roles-to-managed-nodes/4991>\
**Category:** Get Help\
**Tags:** rhel, vmware\
**Created:** [April 17, 2024, 8:12am UTC](https://forum.ansible.com/t/best-place-to-assign-roles-to-managed-nodes/4991 "2024-04-17T08:12:58Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [April 17, 2024, 6:30pm UTC](https://forum.ansible.com/t/best-place-to-assign-roles-to-managed-nodes/4991/3 "2024-04-17T18:30:24Z")

</div>

I sense a disconnect, or perhaps an overload is a better way to say it, around the word “role”. There may not be a 1:1 – or even a clear – relation between the roles your individual hosts play in your infrastructure and the Ansible roles you need or want to run against those hosts. This is a very hand-wavy answer, but a lot depends on what you actually have in your Satellite/Foreman and CMDB that you could draw on to inform other processes. Plus, you [mentioned](http://forum.ansible.com/t/introduce-yourself/15/153) you’re migrating from Saltstack; I imagine that your Saltstack way of organizing things is going to influence the approach you take in Ansible. And that’s okay!

Trust your instincts. You have a better feel for your environment than we do, and there are lots of legitimate ways to do things. Build it in a way you’re comfortable maintaining it. And if you have second thoughts later on, embrace change and refactor early and often.

---

_[View the full topic](https://forum.ansible.com/t/best-place-to-assign-roles-to-managed-nodes/4991)._
