... | ... | @@ -78,10 +78,16 @@ All these operations should be performed in isolation to guarantee atomicity. If |
|
|
|
|
|
A new component, Configuration Manager (CM), will provide the mechanics for ensuring the configuration updates atomicity by locking the configuration until a timeout or until it is committed. CM will also make available the identity of the user currently performing the updates.
|
|
|
|
|
|
### Configuration File Case
|
|
|
|
|
|
![CMConfigSet.svg](uploads/b4759d7c31c0ebdd13c15bfb8ee79841/CMConfigSet.svg)
|
|
|
|
|
|
### Hooks Case
|
|
|
|
|
|
![CMSubnet4Update.svg](uploads/70bbfc3d0e9b21621dee15830b855af3/CMSubnet4Update.svg)
|
|
|
|
|
|
### Config Backend Case
|
|
|
|
|
|
![CMRemoteSubnet4Set.svg](uploads/5a5059d30158b698e4b83475ff5f1ac4/CMRemoteSubnet4Set.svg)
|
|
|
|
|
|
## Configuration Versioning
|
... | ... | |