You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Juniper api used mentions https://github.com/openconfig/public/blob/master/release/models/rpc/openconfig-rpc-api.yang, which went away in May 2016 (openconfig/public@e6a2f26), and the whole .../release/models/rpc subtree went away a year after that (June 2017, openconfig/public@9dcdf78).
I've tested jtimon against a switch running junos 18.3R1.9, and of course it works perfectly. (Some of my own code, using the new(er) OpenConfig api, does not work nearly as well, due (so far as I can tell) to bugs on the Juniper side.)
Would you happen to know when or if Juniper will be upgrading to the new API (or, I guess I should say, fixing it, since you can actually make those rpc calls), or where I might go to get more information on that?
Thank you for your time and this code. As mentioned above, my own code using the new api is broken in severe ways, but this definitely provides a roadmap forwards. Thanks again and I appreciate it!
The text was updated successfully, but these errors were encountered:
The Juniper api used mentions
https://github.com/openconfig/public/blob/master/release/models/rpc/openconfig-rpc-api.yang
, which went away in May 2016 (openconfig/public@e6a2f26), and the whole .../release/models/rpc subtree went away a year after that (June 2017, openconfig/public@9dcdf78).I've tested jtimon against a switch running junos 18.3R1.9, and of course it works perfectly. (Some of my own code, using the new(er) OpenConfig api, does not work nearly as well, due (so far as I can tell) to bugs on the Juniper side.)
Would you happen to know when or if Juniper will be upgrading to the new API (or, I guess I should say, fixing it, since you can actually make those rpc calls), or where I might go to get more information on that?
Thank you for your time and this code. As mentioned above, my own code using the new api is broken in severe ways, but this definitely provides a roadmap forwards. Thanks again and I appreciate it!
The text was updated successfully, but these errors were encountered: