Automation mesh
Automation mesh provides a simple, flexible and reliable way to scale automation of large inventories across diverse network topologies, platforms and teams.
Free, on-demand webinar. Ansible Automation 2.3: Trusted, flexible automation at scale. Watch now
Automation mesh is a key component of Ansible Automation Platform that enables customers to automate at scale in a cloud-native way. It gives customers maximum flexibility in planning distributed, remote or otherwise complex automation deployments, along with visibility, control and reporting.
Automation mesh overview
SCALABILITY
With a flexible, bi-directional communication layer, automation mesh enhances an organization’s ability to truly operate at global scale.
RELIABILITY
With less sensitivity to latency and connection disruption with native peering capabilities, you can reach further with enhanced reliability than with any other automation platform on the market today.
SECURITY
With security features such as digital signing, TLS traffic encryption and additional access controls, you can rely on Ansible Automation Platform to expand the boundaries of what is possible for your entire enterprise IT estate.
E-book: Interactive guide to Ansible Automation Platform 2
Get up to speed quickly on Ansible Automation Platform 2. This free e-book provides an overview of key changes and new features, curated by your role on the automation team.
FAQs
Is automation mesh the same thing as isolated nodes?
No. It replaces and enhances that functionality. Effectively replacing the need for SSH jump hosts and providing an additional relaying facility, for greater distributional global reach.
How is load distributed across multiple execution nodes in an instance group? As an example, 2 execution nodes are located in the same remote environment. How is execution load handled?
A job gets sent to the instance with the most remaining capacity left in the first place. In the event of a tie-breaker situation, the first one in the instance list order wins.
Will it be possible to define execution in the host variables so a single playbook could be run over two different environments hitting more than one location for example on-premise and cloud at the same time?
You can define the Instance Groups to use at various levels including Inventory. By setting up your mesh so that it’ll route to the correct end locations, you can then assign the associated execution nodes to an Instance `Group.