search

clicon / clixon-controller

Clixon network controller
Apache License 2.0
14 stars 5 forks source link

Exclusive candidate configuration #37

Closed krihal closed 8 months ago

krihal commented 1 year ago

Might be needed for both JunOS, EOS etc.

The controller should use configure private (or configure exclusive?) to make sure that no one else commits the candidate configuration.

olofhagsand commented 1 year ago

For junos: https://www.juniper.net/documentation/us/en/software/junos/junos-xml-protocol/topics/ref/tag/junos-xml-protocol-open-configuration.html

olofhagsand commented 8 months ago

Actually, this changed to "exclusive" access. The reason is: (1) private candidate is not a standardized concept (2) Even in the juniper proprietary solution, private cannot be combined with confirm-commit which is necessary for failures at commit (3) exclusive is standard using lock/unlock and can be combined with confirm-commit

olofhagsand commented 8 months ago

In branch https://github.com/clicon/clixon-controller/tree/exclusive-commit

krihal commented 8 months ago

Verified.