Switch the global serial_no to the top object
Currently the serial_no that is incremented every time the configuration file is written is located on the 'cluster' object in the configuration structure. However, this is wrong as the cluster serial_no should be incremented only when the cluster state is changed (for whatever definition of “changed” we will use), not simply because the configuration file is written. This patch changes so that the ConfigWriter._BumpSerialNo affects the top-level ConfigData object. Reviewed-by: ultrotter
Please register or sign in to comment