Table of Contents:
eos_config_deploy_eapi, is a role that deploys the configuration to Arista EOS devices.
The eos_config_deploy_eapi role:
- Designed to replace device running-configuration with intended configuration.
- Backup configuration after successfully change.
Figure 1 below provides a visualization of the roles inputs, and outputs and tasks in order executed by the role.
Inputs:
- Device configuration file in EOS CLI syntax.
Outputs:
- Device running-configuration before configuration is replaced (snapshot).
- Device running-configuration after configuration is replaced (backup).
Tasks:
- Take a backup of the running configuration before configuration is replaced (pre) - (optional, default false).
- Destination:
{{ pre_running_config_backup_dir }}/{{ pre_running_config_backup_filename }}
- Destination:
- Replace configuration on device with intended EOS configuration. If changed, saves to startup-config, and notifies handler to backup configuration.
- Backup Configuration after the configuration is replaced (post) with handler.
- Destination:
{{ post_running_config_backup_dir }}/{{ post_running_config_backup_filename }}
.
- Destination:
# Peform config backup before config replace
eos_config_deploy_eapi_pre_running_config_backup: false
# Root directory where to build output structure
root_dir: '{{ inventory_dir }}'
# Backup directories path and filenames
post_running_config_backup_filename: "{{ inventory_hostname }}_post_running-config.conf"
post_running_config_backup_dir_name: 'config_backup'
post_running_config_backup_dir: '{{ root_dir }}/{{ post_running_config_backup_dir_name }}'
pre_running_config_backup_filename: "{{ inventory_hostname }}_pre_running-config.conf"
pre_running_config_backup_dir_name: 'config_backup'
pre_running_config_backup_dir: '{{ root_dir }}/{{ pre_running_config_backup_dir_name }}'
Requirements are located here: avd-requirements
Project is published under Apache 2.0 License