Developer

Hello everyone,

I'm currently experimenting with Ansible and virtual switches in EVE-NG, and I've noticed something interesting. It appears that the AOS-CX API offers far more calls than there are corresponding Ansible modules, at least for core features like interfaces and VLANs. Does this mean that if I want to configure a switch completely, I must rely on the aoscx_config module? This approach feels less automated than I expected. Could I be looking at the wrong Ansible collection?
Here's the repository link for reference: https://github.com/aruba/aoscx-ansible-collection

Any insights or guidance would be greatly appreciated!

Lars

Hi @LarsNijhuis! Yes that is our AOS-CX Ansible Collection - you can also find our content on Ansible Galaxy here:

https://galaxy.ansible.com/ui/namespaces/arubanetworks/

You are correct and while we are working towards 1:1 parity with what's available through the CX API and what's available through our CX Ansible Collection - the aocx_config module allows for full configuration capabilities using SSH/CLI commands.

Hello everyone,

I'm currently experimenting with Ansible and virtual switches in EVE-NG, and I've noticed something interesting. It appears that the AOS-CX API offers far more calls than there are corresponding Ansible modules, at least for core features like interfaces and VLANs. Does this mean that if I want to configure a switch completely, I must rely on the aoscx_config module? This approach feels less automated than I expected. Could I be looking at the wrong Ansible collection?
Here's the repository link for reference: https://github.com/aruba/aoscx-ansible-collection

Any insights or guidance would be greatly appreciated!

Lars

@Tiffany.Chiapuzio-Wong, thank you for the information and confirmation. Could you please provide an estimated timeframe for new updates? The collection has been around for quite some time now.

@alagoutte, modules such as user control, NTP, Hostname (and other system settings), AAA, and SNMP come to mind for me atm.  Furthermore, it would be great to see future updates include options for EVPN and similar features.

Additionally, it is necessary to disable gather_facts and instead use a separate module. Could you please explain the rationale behind this requirement?

Hi @LarsNijhuis! Yes that is our AOS-CX Ansible Collection - you can also find our content on Ansible Galaxy here:

https://galaxy.ansible.com/ui/namespaces/arubanetworks/

You are correct and while we are working towards 1:1 parity with what's available through the CX API and what's available through our CX Ansible Collection - the aocx_config module allows for full configuration capabilities using SSH/CLI commands.

Hello everyone,

I'm currently experimenting with Ansible and virtual switches in EVE-NG, and I've noticed something interesting. It appears that the AOS-CX API offers far more calls than there are corresponding Ansible modules, at least for core features like interfaces and VLANs. Does this mean that if I want to configure a switch completely, I must rely on the aoscx_config module? This approach feels less automated than I expected. Could I be looking at the wrong Ansible collection?
Here's the repository link for reference: https://github.com/aruba/aoscx-ansible-collection

Any insights or guidance would be greatly appreciated!

Lars

Hello everyone,

I'm currently experimenting with Ansible and virtual switches in EVE-NG, and I've noticed something interesting. It appears that the AOS-CX API offers far more calls than there are corresponding Ansible modules, at least for core features like interfaces and VLANs. Does this mean that if I want to configure a switch completely, I must rely on the aoscx_config module? This approach feels less automated than I expected. Could I be looking at the wrong Ansible collection?
Here's the repository link for reference: https://github.com/aruba/aoscx-ansible-collection

Any insights or guidance would be greatly appreciated!

Lars