Ansible Tower Module

Using the OneFuse Ansible Tower module, it’s easy to create API-based, Ansible-powered services to drive solutions from upstream automation tools or scripts.

OneFuse provides the control and standardization for resources for both public and private cloud (on-prem) environments.

OneFuse eliminates the security risk of requiring direct access to an Ansible Tower, enabling least-privilege access for specific use cases via policy-based services, versus exposing the full Tower API and otherwise over-allocating permissions. Each policy defines the automation use case, organization, inventory and specific job templates – with the added flexibility of having the requester influence all use cases dynamically via templated fields.

Ansible Tower Deployments

Ansible Tower Module with vRA Cloud Assembly

Ansible Tower Module with Terraform

OneFuse Makes vRA Better

Learn more

Highlights

Provides lifecycle support

Run specific Job Templates during provisioning and deprovisioning as part of the policy-based service

Dynamic Assignments

Influence assignments dynamically via templated fields

Centralized Visibility

View the active deployment inventory representing the outputs and relevant data of each policy execution

Features and Capabilities

Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API
Provides control and standardization for resources on both public and private cloud (on-prem) environments
OneFuse enables least-privilege access wherein each policy serves as an API-based service, restricted to the specific use cases defined in the policy, without exposing the full Tower API or over-allocating permissions to users or upstream automation tools.
Each policy defines the automation use case, organization, inventory, specific provisioning and deprovisioning job templates, and overrides
Added flexibility of having the requester influence all use cases dynamically via templated fields
Ability to override Inventory and Inventory Groups, default based on Job Template
Prompt on Launch Overrides
- Ability to verify Prompt on Launch for Limit is defined on each Job Template prior to execution
- Ability to override credential selection using Machine Credentials defined in Ansible Tower
- Ability to supply extra vars, as a JSON formatted string which can include variables given by the user, including answers to survey questions
Multiple Ansible Tower Policies (each specifying an Ansible Tower Endpoint) can safely co-exist, allowing for isolated testing and promotion without disruption
Centralized visibility into inventory of Ansible Tower deployments, log data