On 12/06/14 16:38, Tyler Christiansen wrote:
What are you trying to accomplish? It may be easier to use the Juniper
I am trying to integrate our new EX switches into our existing,
extensive, automation and provisioning systems.
I've already got it working with Junoscript, but as noted had a few
problems (currently successfully being worked around) so took a look at
Netconf, and found namespace issues.
The fundamental question is: are namespaces used incorrectly all over
the place in Netconf?
Netconf Ruby gem or the Python junos-eznc module depending on your
background and goals.
I'd rather stab myself with a rusty fork than use Ruby.
I've looked at the PyEZ and ncclient code, and basically they seem to
take the approach of just throwing away all namespace information. This
seems icky to me, and make me wonder if Netconf is going to be another
SOAP - so many implementation errors that "interop" ends up being a mess
of special casing and workarounds.
In any event, our existing tooling uses Python & Twisted, so
synchronous/blocking libraries don't integrate well.
I'll look at the Ruby code to at least see what they do about
namespaces; I bet "ignore them". Makes me wonder why we even bother with
XML, sigh...
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
