Device Programmability

This topic is to discuss the following lesson:

Hello Rene,

I have been watching videos about Device Programmability and Automation for last two months. It seems Netconf and Restconf more complicated compared to Netmiko or Ansible. Besides that I see a lot of companies asking for Restconf. I think we can do a lot of configurations easily by using Ansible. In presence of Ansible or other tools, why do companies still use Restconf and Netconf?

Could you please help me understand this?

Thanks

Hi Sinasi,

NETCONF/RESTCONF don’t have to exclude Ansible/Netmiko. In fact, Ansible is a great way to work with NETCONF/RESTCONF.

With network automation, the CLI doesn’t work very well. It was created for humans, not scripts. You can use Ansible with regular CLI commands but you can also use it with NETCONF or RESTCONF.

Even if you use NETCONF/RESTCONF, you still need tools to talk with a device somehow. You could use a python script or something like postman. That’s great for some quick examples but not the best way to work with it every day. You could use Ansible and talk with your routers using NETCONF/RESTCONF.

https://docs.ansible.com/ansible/latest/modules/netconf_config_module.html

https://docs.ansible.com/ansible/latest/modules/restconf_get_module.html

RESTCONF/NETCONF are a better way to talk with your router/switch, Ansible is the tool you use.

Does that help?

Rene