[FR] Update the parser to use FRRouting JSON as data-source instead of screen-scraping about hyperglass-agent HOT 2 CLOSED

Hello,

My plan is to do this ASAP, but I have not yet built any UI components to handled structured data output, so doing this now would just print a big JSON blob to the screen, which would be less readable than the CLI output. I’ve put off writing said UI components until I can at least get structured data out of Cisco IOS, IOS-XR, and JunOS as those are the most widely used platforms.

I’m finally almost ready to release v1.0.0-beta.1 of hyperglass, so this shouldn’t be too far behind.

from hyperglass-agent.

Hi there,

Really sorry for not responding to this sooner.

Starting in hyperglass v1.0.0-beta.76, I've started deprecating hyperglass-agent. Moving forward, FRR & BIRD can be interacted with in the same manner as any other device, i.e. via SSH. See here for details/caveats). Everything will still work as-is for now, but I'd encourage you to try moving to frr_ssh/bird_ssh as the nos (and of course, let me know of any problems via a new hyperglass issue).

I'm going to go ahead and close this issue out.

Thanks,
Matt

from hyperglass-agent.