Ansible
Configuration and changes as code.
Ansible works without agents over SSH and APIs and ships with modules for many network and server platforms. Playbooks remain readable for network engineers without a development background. We use it for configuration changes, for standardisation and as the execution layer behind pipelines.
Limits: Ansible does not manage state the way Terraform does. In large environments, you need to keep an eye on run times and idempotent roles.
- network and server changes recur
- you operate devices from different vendors
- a team is getting started with automation
- cloud resources are to be managed across their lifecycle; in that case, use Terraform
- complex logic is needed that is better placed in Python or a workflow tool
In practice
CI/CD and network automation in air-gapped environments
Control deployments and network changes through pipelines without internet access: traceable and within the classified-information requirements.
Read use caseHybrid target architecture for data centre, edge and cloud
Connect your own data centre, edge sites and cloud according to consistent rules: secure, operable and described as code.
Read use caseRelated entries
- Adopt 13Terraform Infrastructure as code for cloud and data centre.
- Trial 08Network configuration from the source of truth Generate device configurations from the data in the source of truth.
- Adopt 11GitLab CI/CD Pipelines for deployments and network changes.
- Hold 20Chef Configuration management in Ruby; not our choice for new initiatives.
History Adopt (New)
Which tools suit your operations?
In an initial call we review your tool landscape and show where a change pays off and where it does not.