Traditional, manual approaches to network configuration and updates are too slow and error-prone to effectively support the needs of today’s rapidly shifting application and data transfer requirements. Programmable, software-based automation technologies can help your team better support your organization’s digital initiatives.
With network automation, network operations (NetOps) teams can quickly respond to dynamic, ever-changing workload requirements for flexible capacity, application security, load balancing, and multicloud integrations. They can also implement self-service and on-demand network activities.
As a result, NetOps teams can become as agile and flexible as applications and infrastructure teams to support modern business demands.
Introducing Red Hat Ansible Automation
With Red Hat® Ansible® Automation, Red Hat brings the community Ansible project to the enterprise, adding the features and functionality needed for team-based automation at scale. Two automation offerings let you choose the capabilities best for your team. Red Hat Ansible Engine gives you support for the Ansible project, so you can automate with confidence. Red Hat Ansible Tower provides an additional management interface, so you can control how automation is deployed, and gain auditable knowledge about automation sources and outcomes.
Redhat Ansible Engine
A support offering for the Ansible project that includes the Ansible execution engine and hundreds of modules for automating all aspects of IT environments and processes.
Redhat Ansible Tower
A product and support offering that helps teams manage deployments by adding control, knowledge, and delegation to Ansible-powered environments.
When Should You Use Red Hat Ansible Tower
We recommend you use Red Hat Ansible Tower when you need:
- Centralized control for multiple people to use the same playbooks.
- Application programming interface (API) control of playbooks.
- Integration with remote authentication tools.
- Compliance checking and enhanced logging.
- More than just network automation.
Playbooks are Ansible’s configuration, deployment, and orchestration language. They consist of sets of human-readable instructions called plays that define automation across an inventory of hosts. Each play includes one or more tasks that target one, many, or all hosts in the inventory. Each task calls an Ansible module that performs a specific function like collecting useful information, backing up network files, managing network configurations, or validating connectivity
Playbooks can be shared and reused by multiple teams to create repeatable automation.
An inventory is a collection of hosts that may be acted on using Ansible commands and playbooks. Inventory files organize hosts into groups and can serve as a source of trust for your network. Using an inventory file, a single playbook can maintain hundreds of network devices with a single command. This chapter explains how to build an inventory file.
A role bundles Ansible automation content to make it reusable. Instead of creating long playbooks with hundreds of tasks, you can use roles to organize and break tasks apart into smaller, more discrete units of work. A role includes all of the tasks, variables and handlers needed to complete the unit of work.
Source : https://www.ansible.com/hubfs/pdfs/RHAA-network-automation-technical-e-book.pdf