Glossary
Terms commonly used throughout the documentation.
- ansible group
- See group.
- Ansible inventory project
- See inventory project.
- group
- A group, also known as an Ansible group, is a collection of servers or hosts defined in the inventory file within an inventory project. It allows referencing multiple associated hosts for automation or defining variables in bulk. Once defined, you can use patterns to select the hosts or groups for Ansible to run against.
See details.
- group-based environments
- Group-based environments refer to an Ansible inventory strategy within an
inventory project, where hosts are organized into groups representing
different environments (e.g.,
dev
,test
,staging
,prod
). This allows for environment-specific variables and configurations to be managed efficiently usinggroup_vars
. See details.
- inventory
- See inventory file.
- inventory file
- An inventory file, also simply referred to as inventory, is a file used in Ansible to define the managed nodes (hosts) that you automate, along with variables associated with those hosts. You can also specify “groups” of hosts, see group. The inventory file is part of an inventory project.
See details.
- inventory project
- An inventory project, also known as an Ansible inventory project, is a structured collection of files used in Ansible for managing hosts and configurations. It typically includes inventory files, playbooks, host configurations, group variables, and vault files. This type of project is sometimes referred to as a playbook project or configuration project.
See details.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified September 4, 2025: guideline gitlab-runner control node PHX-162 (5381212)