Open nodens opened 4 years ago
@nodens Thanks for the report. Rather than forking into a completely new module the recommendation would be to update the existing module to initially support both libraries and then deprecate support for the one that is no longer maintained. Do you know if yanify is a drop in replacement for napalm-yang? Would you be interested and able to add support for this?
Last I looked in to this they were still in the early stages of rewriting napalm-yang in to yangify, is it ready for use now? I think they plan on having rosetta be the device driver layer that then uses yangify
on its own.
The #yangify
channel on the NTC slack is a great place for communication with them if anyone wants more info.
Napalm-yang and yangify do differ quite a bit, rosetta may work as a drop-in but I'm really not sure - someone would need to dig more than I have time for right now.
Description Napalm-yang has been abandoned upstream a couple years ago. Advice is to use yangify instead.
I'm not sure it would make sense to build a new napalm driver based on yangify, or fork napaml-yang, but since I'm considering administering netconf/yang based devices (namely 6wind's soft routers), I thought it would be worth filling an issue.