Developer

A change has been made in the way interfaces will be configured using Ansible with AOS-CX. Originally, in the AOS-CX Collection, to configure interfaces users had the choice of 2 modules aoscx_l2_interface and aoscx_l3_interface  to configure interface specific details. In order to be more consistent with other vendors implementation we've restructured our modules to include a new module aoscx_interface , in this module you'll be able to specify interface attributes that are applicable regardless if routing is enabled or not. For L2/L3 specific configurations you'll continue to use aoscx_l2_interface and aoscx_l3_interface.

 

Examples of how to use these modules are available on our AOS-CX Ansible Workflows Github here:

https://github.com/aruba/aoscx-ansible-workflows

 

Also included in this release is the support for QOS related configurations, please feel free to provide any feedback to our Github issues here:

https://github.com/aruba/aoscx-ansible-collection/issues

 

This will be the final release where the AOS-CX Ansible Role will be supported. Moving forward all new features and bug fixes will be focused on the AOS-CX Ansible Collection.

 

Happy Automating!

------------------------------
Tiffany Chiapuzio-Wong
------------------------------

Our previous implementation will continue to function but will not be supported for future modules. That means you should and eventually have to update your Ansible Inventory variables to specify the ansible_network_os=arubanetworks.aoscx.aoscx and additional variables as well as install the pyaoscx Python package using Python3 pip, all playbooks will remain the same: pip3 install pyaoscx The AOS-CX Ansible Collection will automatically determine if you have pyaoscx installed and will use that method when the ansible_network_os is set to aoscx. If it's set to httpapi it will continue to use the previous implementation method.

------------------------------
piyanjas kosanda
------------------------------