Skip to content

Release Notes for AVD 6.x.x

Versioning

The AVD project follows Semantic Versioning. For the best user experience, we recommend working with the latest stable release. If you are upgrading from version 5.x, please see the 6.0.0 release notes.

For additional information, please see versioning.

Release 6.0.0

Changes to requirements

  • Python requirements:
    • PyAVD no longer requires the cvprac, treelib and jsonschema libraries.
    • PyAVD now requires the anta Python library as a core dependency.
    • PyAVD now requires the pyavd-utils Python library. It will be installed automatically when upgrading pyavd.
    • PyAVD now requires the cryptography Python library to be version 43.0.0 or higher. It will be installed automatically when upgrading pyavd.
    • PyAVD now requires the python-socks[asyncio] Python library to be version 2.7.2 or higher. It will be installed automatically when upgrading pyavd.

    • PyAVD now supports ansible-core from 2.16.0 to 2.20.x. The latest version can be installed with pip install "ansible-core<2.21" --upgrade.

      Note

      ansible-core version 2.19 and later contains many changes to how templating is done. You may see errors around undefined variables, and these must be resolved before running AVD. Previously such errors were silently ignored.

  • Ansible collection requirements:
    • arista.avd Ansible collection no longer requires the arista.cvp and ansible.utils collections.

Removal of Ansible components

The following Ansible components have been removed from the arista.avd Ansible collection in version 6.0.0.

Component type Name Replacement
Action plugin/Module arista.avd.configlet_build_config The internal arista.avd.configlet_build_config module is no longer used by AVD. The plugin is released as open source, so it can be copied and reused according to the license and copyright.
Action plugin/Module arista.avd.inventory_to_container The internal arista.avd.inventory_to_container module is no longer used by AVD. The plugin is released as open source, so it can be copied and reused according to the license and copyright.
Role arista.avd.dhcp_provisioner The role is not compatible with modern DHCP servers and should not be used for production. The arista.avd.dhcp_provisioner role is released as open source, so it can be copied and reused according to the license and copyright.
Role arista.avd.eos_config_deploy_cvp Migrate to arista.avd.cv_deploy. See the detailed porting guide for instructions.
Role arista.avd.cvp_configlet_upload Migrate to arista.avd.cv_deploy. See the detailed porting guide for instructions.
Role arista.avd.eos_validate_state Migrate to arista.avd.anta_runner. See the how-to guide for instructions.

Schema naming changes

In AVD 6.0.0, the data model schemas have been renamed to better reflect their purpose and improve clarity in documentation and error messages:

Previous Schema Name New Schema Name Ansible Role using the schema PyAVD function using the schema
eos_designs AVD Design arista.avd.eos_designs (unchanged) validate_inputs
eos_cli_config_gen EOS Config arista.avd.eos_cli_config_gen (unchanged) validate_structured_config

Note

No changes to playbooks or inventory are required. You may see the new schema names in:

  • Documentation references
  • Schema validation error messages
  • Warning messages
  • Release note and porting guide

The new naming convention provides clearer distinction between:

  • AVD Design (eos_designs role): High-level fabric design and topology abstraction.
  • EOS Config (eos_cli_config_gen role): Low-level EOS configuration.

Example entry

// Description

In AVD 5.x ....

As of AVD 6.0.0 ....

// Adjust anchor when relevant See the porting guide for details.

Breaking or behavioral changes in eos_designs

Breaking changes may require modifications to the inventory or playbook. See the Porting guide for AVD 6.x.x for details.

Detailed changes and link to porting guide
Removal of deprecated eos_designs data models

Fixed IP extended community list and route map for EVPN-SOO

In AVD 6.0.0, when vtep_loopback is set to Loopback0, the IP extended community list and route map for EVPN SOO is corrected to use the Loopback0 IP address.

Breaking or behavioral changes in eos_cli_config_gen

Breaking changes may require modifications to the inventory or playbook. See the Porting guide for AVD 6.x.x for details.

Detailed changes and link to porting guide
Removal of deprecated eos_cli_config_gen data models