@gp_ifconfig @dbarrosop @kirkbyers @adainese If everything has a uniform interface, like NETCONF, then it is trivial to build a generic CLI rendered from the YANG models. Juniper took this approach early on, thanks @philatjuniper. Others did not which is why it's a tad messy now *looking at you, XR*
@gp_ifconfig @dbarrosop @kirkbyers @adainese @philatjuniper this can be cisco style or junos style or some other style. The operations and behavior of the CLI is orthogonal to the data (config and operational state) that it operates on. Imagine configuring XR via NETCONF through JUNOS style CLI or vice versa.
@gp_ifconfig @dbarrosop @kirkbyers @adainese @philatjuniper By junos style I mean you use a command/verb followed by config/noun. Like "set protocols bgp bla". "set" is the command. The rest is the noun you act on. In IOS style you don't have "set" command, it's implicit.
@gp_ifconfig @dbarrosop @kirkbyers @adainese @philatjuniper So editing XR config with junos style CLI wouldn't change the config path of something. XR BGP is under "router bgp" and not "protocols bgp" so you would do like "set router bgp 123 router-id 1.2.3.4" to edit XR config with junos style CLI. Model standardization is separate!
