Committing configuration changes in a multi-node environment from the NISH client should be an atomic operation. This means that at the end of a commit operation for a specified set of nodes, every node should successfully commit the configuration or all the nodes should return to their configuration state before the commit.
The multi-node commit process driven from the NISH client uses standard SR OS MD-CLI features to achieve the atomic commit. There are three phases to the multi-node commit operation:
validation (validate command)
conditional commit (commit confirmed command)
final commit (commit confirmed accept command)
At every stage, each node is processed in turn, to ensure that every node is in the expected state before the next stage.
Figure 1 shows an overview of the multi-node commit process.
