EOS Platform Options
Arista EOS supports multiple connections. This page offers details on how each connection works in Ansible 2.5 and how to use it.
Connections Available
CLI | eAPI | |
---|---|---|
Protocol | SSH | HTTP(S) |
Indirect Access | via a bastion (jump host) | via a web proxy |
Returned Data Format | stdout[0]. | stdout[0].messages[0]. |
Using CLI in Ansible 2.5
Example CLI group_vars/eos.yml
ansible_connection: network_cli ansible_network_os: eos ansible_user: myuser ansible_ssh_pass: !vault... ansible_become: yes ansible_become_method: enable ansible_become_pass: !vault... ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q bastion01"'
- If you are using SSH keys (including an ssh-agent) you can remove the
ansible_ssh_pass
configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the
ansible_ssh_common_args
configuration. - If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the
ProxyCommand
directive. To prevent secrets from leaking out (for example inps
output), SSH does not support providing passwords via environment variables.
Example CLI Task
- name: Backup current switch config (eos) eos_config: backup: yes register: backup_eos_location when: ansible_network_os == 'eos'
Using eAPI in Ansible 2.5
Enabling eAPI
Before you can use eAPI to connect to a switch, you must enable eAPI. To enable eAPI on a new switch via Ansible, use the eos_eapi
module via the CLI connection. Set up group_vars/eos.yml just like in the CLI example above, then run a playbook task like this:
- name: Enable eAPI eos_eapi: enable_http: yes enable_https: yes become: true become_method: enable when: ansible_network_os == 'eos'
You can find more options for enabling HTTP/HTTPS and local http in the eos_eapi module documentation.
Once eAPI is enabled, change your group_vars/eos.yml
to use the eAPI connection.
Example eAPI group_vars/eos.yml
ansible_connection: local ansible_network_os: eos ansible_user: myuser ansible_ssh_pass: !vault... eapi: host: "{{ inventory_hostname }}" transport: eapi authorize: yes auth_pass: !vault... proxy_env: http_proxy: http://proxy.example.com:8080
- If you are accessing your host directly (not through a web proxy) you can remove the
proxy_env
configuration. - If you are accessing your host through a web proxy using
https
, changehttp_proxy
tohttps_proxy
.
Example eAPI Task
- name: Backup current switch config (eos) eos_config: backup: yes provider: "{{ eapi }}" register: backup_eos_location environment: "{{ proxy_env }}" when: ansible_network_os == 'eos'
In this example two variables defined in group_vars
get passed to the module of the task:
- the
eapi
variable gets passed to theprovider
option of the module - the
proxy_env
variable gets passed to theenvironment
option of the module
Warning
Never store passwords in plain text. We recommend using SSH keys to authenticate SSH connections. Ansible supports ssh-agent to manage your SSH keys. If you must use passwords to authenticate SSH connections, we recommend encrypting them with Ansible Vault.
© 2012–2018 Michael DeHaan
© 2018–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.5/network/user_guide/platform_eos.html