Updates for Ansible 2.9

Author: hpreston

netdevops/ansible_part_2/example1.yaml

@@ -11,13 +11,20 @@
 ---
 - name: Retrieve facts from Switches
   hosts: switches
-  connection: local
+  gather_facts: False
+
+  # Ansible added new connection options for networking devices
+  # to replace connection: local
+  # Now connection: network_cli or httpapi are recommended
+  #   Doc: https://docs.ansible.com/ansible/2.9/network/user_guide/platform_nxos.html 
+  connection: network_cli
 
   tasks: 
     - name: "Retrieving NX-OS Facts"
       nxos_facts: 
-        host: "{{inventory_hostname}}"
-        transport: nxapi 
+        # See docs for what subset options of facts are available
+        #   https://docs.ansible.com/ansible/2.9/modules/nxos_facts_module.html#nxos-facts-module 
+        gather_subset: all
       register: nxos_info
 
     - name: "Print NX-OS Facts"

netdevops/ansible_part_2/example2.yaml

@@ -11,24 +11,49 @@
 ---
 - name: Configure Loopback Networks on Each Switch
   hosts: switches
-  connection: local
+  gather_facts: False
+
+  # Ansible added new connection options for networking devices
+  # to replace connection: local
+  # Now connection: network_cli or httpapi are recommended
+  #   Doc: https://docs.ansible.com/ansible/2.9/network/user_guide/platform_nxos.html 
+  connection: network_cli
 
   tasks: 
     - name: Create Loopback Interface
-      with_items: "{{ local_loopbacks }}"
+      # Note: The "with_items" syntax has been replaced by "loop" 
+      #  - https://docs.ansible.com/ansible/2.9/user_guide/playbooks_loops.html#with-items
+      loop: "{{ local_loopbacks }}"
+      # with_items: "{{ l3_fabric.interfaces }}"
+      # Note: the nxos_interface module has been replaced with nxos_interfaces 
+      #  and will be deprecated/removed soon. However the new nxos_interfaces 
+      #  module has a bug in Ansible 2.9 when trying to create loopbacks. Keeping 
+      #  this example using nxos_interface for now. 
+      # Info: 
+      #  - https://docs.ansible.com/ansible/2.9/modules/nxos_interfaces_module.html
+      #  - https://docs.ansible.com/ansible/2.9/modules/nxos_interface_module.html
       nxos_interface: 
-        host: "{{ inventory_hostname }}"
         interface: "{{ item.name }}"
         mode: layer3
         description: "{{ item.desc }}"
-        admin_state: up
 
+
+
+    # Note: The module nxos_ip_interface was obsoleted by Ansible and replaced with 
+    #  nxos_l3_interfaces. This module provides the same purpose, but with different 
+    #  syntax. See details at: 
+    #  - https://docs.ansible.com/ansible/2.9/modules/nxos_l3_interfaces_module.html
     - name: Configure IPv4 Address on Interface
-      with_items: "{{ local_loopbacks }}"
-      nxos_ip_interface:
-        host: "{{ inventory_hostname }}"
-        state: present
-        interface: "{{ item.name }}"
-        version: v4
-        addr: "{{ item.ip_address }}"
-        mask: "{{ item.prefix }}"  
+      # Note: The "with_items" syntax has been replaced by "loop" 
+      #  - https://docs.ansible.com/ansible/2.9/user_guide/playbooks_loops.html#with-items
+      loop: "{{ local_loopbacks }}"
+      # Note: to stay consistent with the videos for the lesson, this playbook 
+      #  uses the loop construct for configuring interfaces. The current module 
+      #  does support multiple interfaces in one task execution, and that would 
+      #  be a more efficient configuration.
+      nxos_l3_interfaces:
+        state: merged
+        config: 
+          - name: "{{ item.name }}"
+            ipv4: 
+              - address: "{{ item.ip_address }}/{{ item.prefix }}"

netdevops/ansible_part_2/group_vars/switches.yaml

@@ -0,0 +1,12 @@
+# These variables are used with the connection: network_cli for Ansible
+# Info:   https://docs.ansible.com/ansible/2.9/network/user_guide/platform_nxos.html 
+#         https://docs.ansible.com/ansible/2.9/plugins/connection/network_cli.html 
+
+---
+# ansible_connection: network_cli 
+ansible_network_os: nxos 
+ansible_user: cisco 
+ansible_password: cisco 
+ansible_become: yes 
+ansible_become_method: enable 
+ansible_become_password: cisco