Replies: 1 comment 2 replies
-
The main problem I see is that NAPALM is going to require all the core platforms to return the same data structure for So then we would have a bit of an issue with what to do about the other platforms (Junos, Arista, IOS-XR, NX-OS) and does what we are doing for IOS/IOS-XE make sense for these other platforms or not (as far as adding a new key for the You could probably do this with ntc-ansible and ntc_show_command module and just execute a This in NAPALM:
Calls this in Netmiko:
Which basically just parses the Let me know if that workaround will work for you (without needing to create an Ansible module). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For IOS, NAPALM requires the following in the running-config in order to merge or replace a config:
Of course the path directive might be different, e.g. bootflash: depending on the specific device. I want to template out the right config ahead of time to enable config replace.
I see I can get the value with
device._discover_file_system()
. But (AFAICT) no getters return this value so I can't use ansible to discover it without a custom module. I could write a custom module, but wondering if others might also find it useful if this value were returned as an key inget_facts()
, or another getter? Something like this:Beta Was this translation helpful? Give feedback.
All reactions