You need to practice somes to familiar with Ansible first. Then set some 
small targets using ansible to manage. So far I know switch, router devices 
don't have python inside which must have to manage by ansible.

I suggest you use model : Ansible control --> Jump server --> cisco 
devices. (I use this model to do backup task all devices in my environment 
labs)
Ansible control: ansible installed, use playbook variable to manage 
quantity/type of devices, use templates to send scripts to Jump server to 
execute.
Jum server: Python installed, expect installed. Only use for executing 
scripts to manage devices (upgrade, backup, etc..)

### playbook.yml sample
---
- hosts: jumpserver
  become: yes
  become_method: su
  gather_facts: no
  ignore_errors: yes
  roles:
    - upgrade_cisco_router
    - backup_router

####upgrade_cisco_router roles sample:
## roles/tasks/main.yml
---
- name: Prepare upgrade scripts
  template: src=upgrade_cisco_router.exp.j2 
dest=/root/upgrade_cisco_router_{{ item }}.exp mode=0774
  with_items:
    - {{ cisco_router }}
- name: Start upgrade 
  raw: /root/upgrade_cisco_router_{{ item }}.exp 
  with_items:
    - {{ cisco_router }}
## roles/vars/main.yml
---
cisco_router: ["10.10.10.5", "10.10.10.6"]

## roles/templates/upgrade_cisco_router.exp.j2
<contain script to upgrade cisco router>


On Thursday, May 16, 2019 at 1:57:40 PM UTC+7, rajthecomputerguy wrote:
>
> Hi Team,
>
> Which is one is followed as best practice in Ansible?
>
> Using jump server to connect devices ? or having direct access to devices.
>
> thanks
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/f11db751-f984-45f9-ba50-2a37ab933b76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to