Closed raddessi closed 5 years ago
First, with yangify
, you can pick an match as you want, the idea of the Root{Parser, Translator}
is that you can combine things as you wish. For instance:
class MyPickAndMixParser(RootParser):
arp = CustomArpModelParser
interfaces = OpenconfigIOSInterfacesParser
vlans = IETFIOSVlanParser
Re rosetta
, a few comments:
ntc-models
and ARP is actually one of the first things we want to add.My recommendation at this point would be to wait a bit so we have the time to opensource the ntc-models and integrate them into rosetta and then we can take this discussion from there
Nice, I didn't realize you could mix and match in yangify that way.
For now I'll wait and see what you guys put out with ntc-models, it looks like you all have been moving pretty quickly on these projects so far. Thanks
Ahh, thank you :) I joined the ntc slack as well
Seems like this is a good opportunity to improve the docs a little?
Is there anything left to do here? Otherwise I will proceed to close it.
No, I think you can close this one out. Thank you again for all the feedback and work! Have a good week
Hi,
I want to be able to set some minimal arp configuration on interfaces (expiry-time in ietf-arp) but there doesn't appear to be any model for that in openconfig yet, at least from what I've looked at. If I want to use yangify and ntc-rosetta to build switch config does it make more sense to try to use the ietf and openconfig models at the same time or try to build our own augmentations on to openconfig to support just what we need?
The relevant ietf-arp config I would use is something like:
But that would have to get merged with the openconfig-interfaces:interfaces config for ip addresses/mtu/desc/channel group etc.
Thank you :)