Inventory and Playbooks - Aruba Bots Ansible Series 02

[@davidibrahim7809]

Very informative stuff. Thanks. I noticed the inventory and playbooks use rest interface to communicate with the hosts as well as to push the commands. How about using SSH for connecting and the traditional CLI-style to configure the devices. Is it possible? Do we have Aruba modules that support this? I assume that if I change ansible_connection from "local" to "network_cli", I should be able to enforce the ansible control machine to use SSH to connect to remote hosts. However, after successful connection, how would I define the plays in my playbook to execute the tasks that I intend to push to those remote hosts? I am just curious.

[@mcirigliano7697]

Thank you! Very informative. How do you have both switches connected to your system running the commands? How many switches can you have at once? It seems you can configure 10 at a time if you really wanted, no?

[@AirheadsBroadcasting]

With Ansible you can manage any number of devices in your inventory! Ansible simply needs to be able to reach the IP address you want to use to manage the device! You are correct! You can configure more than 10 at a time! For performance tuning visit Ansible's site for more information : www.ansible.com/blog/ansible-performance-tuning

[@jeromemeinzen]

Thank you, very informative. Could you let me know the Aruba reset manager password command to use on Ansible please?

[@fossdom5568]

Question - After you issue the playbook command on ansible to write the config changes ,and after its done writing the changes on the switch , does it save (write mem) the config automatically? Like how we do manually ??? On the switch

[@iliakupriianov754]

Thanks, very helpful! May be if you were to change from cutting videos to 3-5 seconds chunks to more continuous flow information would be easier to digest? You still can cut out any moments unrelated to aruba-ansible-modules, but while creating a certain file could you keep it end-to-end solid?

[@AirheadsBroadcasting]

Thank you for that feedback! We'll work on implementing a more solid flow in the next video of this series!