Ansible Inventory Generator

Introduction:

Before a playbook can change a server, router, switch, or virtual machine, Ansible needs a dependable inventory. The inventory is the control node's plain-text map of managed hosts: the names Ansible will target, the groups those names belong to, and the connection variables that tell Ansible how to reach them. A messy inventory can make a play run against the wrong group, hide duplicate aliases, or depend on a hostname that resolves only for one operator.

Static inventory files still have a place beside dynamic cloud discovery. They are easy to review in a change request, do not require provider credentials, and make a bounded rollout set visible before automation runs. INI inventory is compact enough for small batches, labs, jump-start network inventories, and temporary change windows, as long as the operator remembers that a clean text file is not the same thing as a tested connection.

Inventory alias

The unique host name Ansible uses inside the inventory and play output.

Connection address

The host name or IP address used for the actual connection when it differs from the alias, commonly represented by ansible_host.

Primary group

The main target group that receives every accepted host row.

Group variables

Shared values placed under a :vars section, such as login user, connection type, or platform settings.

Grouping is the main reason to write inventory instead of pasting a list of addresses into a command. A host can belong to a primary group such as edge_routers while also appearing in groups for site, platform, role, or environment. A parent children group can gather several smaller groups into a broader target, so a playbook can say what it intends to change without duplicating host rows.

Variables need careful placement. Host variables belong on a host line when the value is unique, such as a nonstandard SSH port. Group variables belong in a :vars section when the value applies to every member of the primary group. Secrets are a poor fit for static inventory text because copied output, review tables, and screenshots can expose them. Use vaulted variables or another protected workflow for passwords, tokens, and private keys.

A generated inventory is ready for review, not ready for blind execution. It can reduce text mistakes before a change, but only the installed Ansible version on the control node can prove how the file parses, and only a limited connectivity check can prove that DNS, SSH, WinRM, network CLI access, Python paths, collections, and credentials are correct.

How to Use This Tool:

Build the inventory from the target group outward, then use the review output before copying or downloading the INI draft.

1. Set Inventory group to the primary target you expect to use in playbooks or ad hoc commands, such as edge_routers, prod_linux, or web. Empty group names and names with whitespace, brackets, colon, or # create blocking errors.
2. Enter Host rows as alias,ansible_host,groups,host_vars, paste rows, drop a CSV or TXT file, or use Browse CSV. Blank lines, comment lines beginning with #, and a recognizable header row are ignored.
3. Use the third cell for extra groups. Spaces, pipes, and semicolons split multiple group names, so dc1|ios and dc1 ios both create additional group membership.
4. Put host-specific values after the third comma as key=value tokens. Put shared values in Group variables, one key=value entry per line.
5. Set Default ansible_user when the same login user applies to the primary group. If Group variables already includes ansible_user, the review warns that the group variable takes priority over the default user field.
6. Open Advanced for Parent children group, alias sorting, verification comments, or an intentional empty :vars section. Use Normalize rows after import when accepted rows need a consistent CSV shape.
7. Read Inventory Review before using INI Inventory. Red errors leave the INI output empty; yellow warnings still allow output but need operator review. Parse the draft with ansible-inventory -i inventory.ini --list before running playbooks.

Interpreting Results:

The summary reports status, accepted hosts, the primary group, and remaining warnings. An accepted host count means the rows could be parsed into an inventory draft. It does not prove that the host names resolve, that the login user can authenticate, or that the selected connection plugin works.

Red errors are stop signs. The generated INI text stays empty so a partial inventory is not mistaken for a usable file. Yellow warnings describe choices that may be valid but deserve attention, such as a short alias without a separate ansible_host or a group name that may trigger Ansible naming warnings.

A clean review can still hide environmental problems. Treat the generated text as a draft that has passed local syntax and naming checks, then validate it with Ansible and a limited connectivity command before any change work.

Technical Details:

INI inventory is section based. A [group] section lists hosts, a [group:vars] section assigns values to every member of that group, and a [parent:children] section lists child groups rather than host lines. The inventory alias becomes Ansible's host identity, while variables such as ansible_host, ansible_port, ansible_user, and ansible_connection affect how Ansible connects.

INI variables have an important type caveat. Inline host variables can be interpreted as Python literal values, while variables in a :vars section are treated as strings. For typed values, nested data, or sensitive material, separate host_vars and group_vars files are usually easier to audit than a dense static INI file.

Transformation Core:

The generator maps each accepted row into one primary host entry, optional extra group membership, optional host variables, and optional shared group variables.

A row such as edge-rtr-01,10.44.1.11,dc1|ios,site=dc1 role=edge rack=A1 becomes one host under the primary group, two extra group memberships, and three host variables. With a parent group of network, the parent children section includes the primary group plus dc1 and ios.

[edge_routers]
edge-rtr-01 ansible_host=10.44.1.11 site=dc1 role=edge rack=A1

[dc1]
edge-rtr-01

[ios]
edge-rtr-01

[network:children]
edge_routers
dc1
ios

Rule Core:

Variable Semantics:

Variable precedence extends beyond one generated file. Parent groups, child groups, host variables, separate variable files, playbook variables, and command-line variables can all affect the final values Ansible sees. Parse the inventory and inspect final host variables before relying on the draft for operational changes.

Privacy Notes:

Pasted host rows and CSV or TXT imports are read in the browser, and imported files over 1 MiB are rejected. The generated INI, ledger, review rows, JSON snapshot, copied text, downloaded files, and screenshots can still expose hostnames, IP addresses, ports, users, platform names, and variables. Keep secrets out of static inventory text and use Ansible Vault or another protected variable workflow for sensitive values.

Advanced Tips:

• Leave Include verification comments enabled when handing the draft to another operator because it keeps the parse command near the generated text.
• Use Host order by alias only when review readability matters more than preserving the original source-line order.
• Turn on Keep empty :vars section only when you intentionally want a placeholder for later editing.
• Use Normalize rows after importing from a spreadsheet so quoted values and accepted group lists are easier to compare.
• Move growing platform settings into separate group_vars files once the INI draft stops being short and readable.

Worked Examples:

FAQ:

Glossary:

Control node

The machine where Ansible runs, parses inventory, and starts connections to managed hosts.

Inventory alias

The host identity Ansible uses inside inventory and play output.

ansible_host

The resolvable host name or IP address used when it differs from the inventory alias.

Primary group

The main generated group section that receives every accepted host row.

Extra group

An additional group assigned from a host row for site, role, platform, or environment targeting.

Parent children group

A metagroup section that lists child group names instead of individual hosts.

Host variables

Inline variables placed on one host line because the value applies only to that host.

Group variables

Shared variables placed under a [group:vars] section for members of the primary group.

References:

• How to build your inventory, Ansible Community Documentation.
• Build Your Inventory, Ansible Community Documentation.
• Protecting sensitive data with Ansible vault, Ansible Community Documentation.
• How to connect to an SSH server on a different port, Simplified Guide.
• How to set per-host SSH identity files in config, Simplified Guide.