On Thu, Oct 01, 2015 at 12:30:51AM +0300, Martin T wrote:
> So in order to sum this up, "commit check" makes sense at least in
> following cases:
>
> 1) confirm "commit confirmed" action. This does not waste a rollback.
> 2) test errors for configuration which will be saved and committed later
> 3) make intermediate syntax checks in case of large configurations in
> order to make sure that configuration applied to candidate
> configuration so far is fine
> 4) use "commit check" to trigger commit scripts
5) coordinate commits across multiple devices to be sure they will all
succeed at the same time when the final commits are given
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
