iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Ansible roles turn infrastructure automation into reusable, reviewable building blocks. A role bundles ordered tasks with the variables, handlers, templates, files, and metadata that those tasks need, all in a directory structure Ansible understands. Build a role around one capability, keep environment values in inventory, pin shared dependencies, and call the role from a predictable repository layout. The result is infrastructure behavior you can apply consistently across staging and production without copying large playbooks.
What an Ansible role is and why it matters
Ansible describes roles as a way to automatically load related variables, files, tasks, handlers, and other artifacts from a known file structure. That convention is the important part: once a role has the expected directories and entry files, Ansible can find its components without every playbook spelling out their paths.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsA role is best treated as a small software component with an interface. Its interface consists of documented input variables, supported platforms, defaults, dependencies, and side effects such as service restarts. The implementation is the task flow plus its templates, static files, handlers, and validation. A focused role might manage a web server, a common operating-system baseline, monitoring, firewall rules, or an application runtime.
Roles solve several practical problems:
- Reuse: the same configuration behavior can be applied to many host groups and environments.
- Separation: environment-specific addresses, ports, and credentials stay in inventory or variable files instead of being embedded in task code.
- Reviewability: operators can inspect one capability, its defaults, and its side effects without reading an entire site playbook.
- Composition: a play can combine several function-oriented roles, while metadata can enforce prerequisites that every invocation needs.
- Distribution: internal roles and shared Galaxy or collection content can be versioned and installed reproducibly.
Role anatomy: the directories Ansible recognizes
A role needs only the standard directories it actually uses. You do not have to retain empty directories from a generated skeleton, but each component belongs in its conventional location.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
| Path | Purpose | Typical contents |
|---|---|---|
tasks/main.yml |
Entry point for the role’s ordered task flow. | Package installation, configuration, service management, and includes for platform-specific work. |
handlers/main.yml |
Handlers notified by changed tasks. | Service reloads or restarts that should run only when configuration changed. |
templates/ |
Jinja templates rendered by the template module. |
Configuration files containing variables and conditional sections. |
files/ |
Static files copied to managed hosts. | Certificates, scripts, or other files that do not require templating. |
defaults/main.yml |
Low-precedence defaults that callers can override. | Safe listen ports, feature switches, paths, and other documented inputs. |
vars/main.yml |
Role variables with higher precedence than defaults. | Values that are part of the implementation and should not normally be overridden. |
meta/main.yml |
Dependencies and optional Galaxy metadata. | Prerequisite roles and metadata used when publishing or consuming the role. |
README.md |
Human-facing interface documentation. | Required variables, defaults, supported systems, examples, tags, and side effects. |
tests/ |
Role-specific test scaffolding. | Example inventory, test playbook, or checks used by your CI process. |
Keep the main task file readable. When lifecycle or platform differences make it long, split the flow with task includes so reviewers can see, for example, package installation, configuration, and service management separately. The role should still have one clear entry point at tasks/main.yml.
Create a role with a predictable skeleton
Use the Galaxy command-line tool to generate the conventional layout:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →ansible-galaxy role init webserverThe generated role includes README.md, defaults/, files/, handlers/, meta/, tasks/, templates/, tests/, and vars/. Remove directories that the finished role does not use, but keep every directory required by the implementation. Then build the role in this order:
- Define the capability: choose one coherent responsibility and state which operating systems or platforms it supports.
- Design the interface: place safe, user-overridable values in
defaults/main.yml; document required inputs and expected types in the README. - Write the flow: put the ordered configuration steps in
tasks/main.yml, using includes when platform or lifecycle branches deserve separate files. - Add artifacts: put static files in
files/and Jinja-rendered configuration intemplates/. - Handle changes: define reload or restart handlers in
handlers/main.ymland notify them only from tasks that report a change. - Declare prerequisites: add genuine, mandatory role dependencies to
meta/main.yml. - Document and test: update the README and run the complete role path on every platform and Ansible version your project claims to support.
Call a role from a play
A play can apply a role directly to its target hosts:
- hosts: webservers
roles:
- role: webserver
webserver_listen_port: 8080Variables supplied on the role entry let one implementation serve different environments. Keep this interface small: expose behavior callers genuinely need to change, provide safe defaults for the rest, and avoid requiring operators to understand internal task variables.
Use role entries for normal composition
Listing roles under roles: makes the play’s high-level order easy to read. It is appropriate when the role should be part of the play’s normal execution and does not need to be selected at a particular task location.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use include_role for dynamic selection
include_role inserts a role at a task location and is useful when a condition determines whether the role runs or when the role must be selected during execution. This makes the role’s placement and conditions visible alongside neighboring tasks.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Use import_role for static expansion
import_role favors static parsing and predictable expansion. Choose it when the role structure should be known when Ansible parses the playbook rather than selected dynamically during a run.
Running a role more than once
Ansible can run the same role more than once when its parameters differ. Metadata can explicitly permit duplicate execution with allow_duplicates: true. Without that setting, duplicate dependencies normally run once unless parameters, tags, or when conditions make the invocations distinct. Design repeated calls deliberately: two instances that manage the same file or service can overwrite one another or trigger surprising restarts.
Declare prerequisites and role dependencies
Dependencies belong in meta/main.yml when every invocation of a role requires them. For example:
---
dependencies:
- role: common
- role: firewall
vars:
firewall_allowed_ports: [80, 443]Ansible runs the listed dependencies before the role that declares them. It resolves nested dependencies recursively, so a prerequisite can bring in its own prerequisites. These are prerequisites, not an ownership hierarchy: the dependent role does not take over the other role’s code.
Choose dependencies versus explicit role calls
- Use a metadata dependency for a capability that must exist every time the role runs, such as a common baseline required by all web-server instances.
- Call an optional capability explicitly from the play when operators should control its tags, conditions, or order. Explicit calls keep optional behavior visible in the site composition.
- Review duplicate dependencies carefully. Parameters, tags, or conditions can affect whether Ansible treats invocations as distinct;
allow_duplicates: trueforces permitted repeated execution where that is intentional.
Install and pin shared roles
Keep external role selections in a repository-level requirements.yml file. Pinning a Galaxy version, a Git tag, or a commit hash prevents an unreviewed upstream change from altering production configuration.
---
roles:
- name: geerlingguy.apache
version: 3.2.0
- name: hardening
source: https://git.example.com/infra/ansible-role-hardening.git
scm: git
version: v1.4Install the declared content with:
ansible-galaxy install -r requirements.ymlThe requirements format supports roles selected by namespace, a Git URL, a semantic-version tag, or a commit hash. In production, select an immutable commit or an intentional release tag, record that choice in version control, and upgrade it through code review.
Control where roles are installed
Use --roles-path on the command line or the ANSIBLE_ROLES_PATH environment variable to choose the destination. This is useful when a project keeps downloaded dependencies outside the default location or when CI needs an isolated installation directory.
Recommended Free Tools
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Useful Galaxy installation controls
--no-depsskips dependency installation when dependencies are managed elsewhere.--forceoverwrites an existing role. Use it only for a deliberate, reviewed replacement, not as an upgrade strategy.--force-with-depsoverwrites the role and its dependencies.--serverselects an alternate Galaxy server.--roles-pathcontrols the installation destination.
Downloaded roles are software. Read their tasks, variables, templates, and metadata before using them; check supported platforms and side effects; and test the selected version in your own estate. A role that restarts a service, changes firewall rules, or writes credentials deserves the same review as internal automation.
Organize an infrastructure repository
A predictable repository separates environments from reusable capabilities:
ansible/
inventories/
production/
staging/
group_vars/
playbooks/
site.yml
roles/
common/
webtier/
monitoring/Inventories and variables
Put environment-specific host membership and values in the inventory tree, with shared group values in group_vars/ and host-specific exceptions in host variables. Keep production addresses, credentials, and environment names out of role code. The role should expose documented defaults and remain portable.
Playbooks as composition layers
Use a site playbook to assign roles to inventory groups and express environment composition. A playbook should answer which capabilities apply to which hosts; the role should answer how one capability is implemented.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Make role discovery explicit when needed
Ansible searches collections, a roles/ directory relative to the playbook, configured roles_path locations, and the playbook directory. If playbooks live under playbooks/ while roles remain at the repository root, configure the path in ansible.cfg:
[defaults]
roles_path = ./rolesUse an explicit path when moving files would otherwise make role resolution depend on the caller’s working directory. Keep the configuration under version control so local development and CI resolve the same content.
Design variables, templates, and handlers safely
Defaults versus role variables
Put values that callers should override in defaults/main.yml. Defaults have low precedence and are the right place for safe ports, paths, and feature switches. Values in vars/main.yml have higher precedence and generally represent implementation details that should not be casually replaced. Do not use high-precedence variables merely to make a role difficult to configure; document why a value is fixed when it truly must be.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Keep templates deterministic
Templates should render from the role’s documented inputs and inventory data. Keep static content in files/ instead of adding unnecessary templating. If a configuration change requires a service reload or restart, have the template task notify a handler and let the handler perform the operation.
Notify handlers only on change
Handlers are intended for state changes. A task that reports no change should not cause a restart, because unnecessary restarts increase deployment risk and make repeated runs disruptive. Keep handler names stable and document whether the action is a reload or a full restart.
Protect secrets
Do not commit plaintext credentials in role defaults, variables, templates, or example inventories. Use an approved secret store or an encrypted variable mechanism, and ensure rendered files have appropriate permissions. Treat secret-bearing templates and logs as sensitive outputs.
Validate inputs and support multiple platforms
If a role has a strict interface, validate its inputs early with argument specifications. Fail before package or configuration changes when a required value is missing or outside the supported range. Document the accepted types, required variables, defaults, and platform assumptions in the README.
Separate distribution-specific or lifecycle-specific work into included task files when that improves reviewability. A common pattern is a short entry file that selects the appropriate implementation, followed by shared configuration and service tasks. Keep the supported distribution and Ansible-version policy explicit; test every combination you claim to support rather than assuming that a role working on one host proves portability.
Test roles as complete execution paths
Role tests should exercise the whole path, not only an individual tagged task. A tag-focused run can hide ordering problems, missing variables, or a handler that is required by an earlier task. Use the generated tests/ area or your project’s CI framework to provide a test inventory and playbook, then run the role against each supported distribution and Ansible version.
- Check that the role converges successfully on a clean host.
- Run it a second time and verify that already-correct state produces no unnecessary changes.
- Change a template input and confirm that the appropriate handler runs.
- Exercise required and invalid inputs to confirm early validation.
- Verify that dependencies are installed and ordered before the dependent role.
- Check tags, conditional paths, and platform-specific includes as well as the default path.
- Inspect rendered files and permissions without exposing secret values in logs.
The exact CI matrix is an estate decision. Record the operating-system distributions and Ansible versions you support, and update that policy when the role or its dependencies change.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Choose between local, Galaxy, and collection roles
The right source depends less on convenience than on ownership, compatibility, and reviewability.
| Approach | Ownership and review | Version control | Questions to answer before adoption |
|---|---|---|---|
| Local role | Your team owns the repository, tests, and release process. | Commits and internal release conventions. | Is the interface documented? Which platforms and Ansible versions are tested? What side effects are expected? |
| Galaxy role | An external publisher owns the content; your team must review it before use. | Galaxy release, semantic-version tag, or commit selection in requirements.yml. |
Are dependencies transparent? Does the selected release support your estate? How often is it updated? |
| Collection role | Content is distributed as part of a collection with its own namespace and release process. | Collection version and associated dependency requirements. | Are module collection names and role interfaces compatible with project policy? What is the collection’s test and support policy? |
For any option, inspect variable names, supported operating systems, templates, dependencies, and service or firewall side effects. Pin the selected version and make upgrades deliberate.
Operational practices that keep roles maintainable
- Use fully qualified collection names for modules when project policy requires them, and document collection requirements beside role requirements.
- Use tags for focused operational runs, but always test the complete role path in CI so a tag-only invocation cannot conceal ordering errors.
- Keep optional capabilities as explicit play-level role calls when operators need independent control.
- Keep role names and variable names stable; changing an interface is a compatibility event that deserves a documented migration.
- Review role upgrades like application-code changes, including dependency changes and rendered configuration differences.
- Prefer idempotent tasks and handlers that react only to actual changes, so repeated site runs are safe and predictable.
Troubleshoot common role failures
Ansible cannot find the role
Check the directory name, the playbook location, and the configured search paths. If roles are at repository root while playbooks are under playbooks/, add roles_path = ./roles under [defaults] in ansible.cfg. For downloaded roles, verify that ansible-galaxy install used the same destination that your execution environment searches.
A dependency runs in an unexpected order
Inspect every meta/main.yml, including nested dependencies. Dependencies run before the declaring role, and nested prerequisites are resolved recursively. If a role is being skipped or duplicated, compare its parameters, tags, and when conditions and check whether allow_duplicates is set intentionally.
A variable is ignored
Confirm the variable name matches the role’s documented interface and determine where it is defined. A value in vars/main.yml has higher precedence than a value in defaults/main.yml; environment-specific values should normally live in inventory or group and host variables. Avoid fixing precedence surprises by adding more overrides until the role’s variable contract is clear.
A service restarts on every run
Find the task notifying the handler and check whether that task reports a change every time. Templates should change only when their rendered content changes, and handlers should be notified only by tasks that actually modify state.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe role works only when run with a tag
Run the full role path. Tag-only execution can bypass setup tasks, variable validation, or dependency work and produce a misleading success. Add a complete-path test to CI and use tags only for intentional operational subsets.
An external role changed unexpectedly
Check requirements.yml for an unpinned selection and inspect the installed version. Pin a semantic-version release, Git tag, or commit hash, record the installation result, and review future upgrades instead of relying on an unconstrained latest version.
Quick Recap
Production checklist
- The role has one clearly defined capability and a documented supported-platform policy.
tasks/main.ymlis the readable entry point; complex branches are split into appropriate includes.- Overrideable values are in
defaults/main.yml, while implementation constants invars/main.ymlare intentional. - Dependencies in
meta/main.ymlare mandatory prerequisites, not hidden optional features. - Templates, static files, and handlers are kept in their standard directories.
- Secrets are stored through an approved secret mechanism rather than plaintext role files.
- External roles and collections are pinned in requirements files and reviewed as code.
- The repository keeps inventories, group variables, playbooks, and roles in predictable locations.
roles_pathis configured when the repository layout is outside Ansible’s default search locations.- CI tests complete execution, repeatability, handlers, validation, dependencies, tags, and every supported platform and Ansible version.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
