Previously, our method involved persisting the entirety of the running configuration into /etc/sonic/config_db.json by running config save in a task. This approach led to undesired configurations being retained, especially noticeable after a switch reboot. A key example of such undesired configurations arises from metal-core.
To refine this, we have now transitioned to a selective persistence strategy. Instead of saving the entire running configuration, only crucial segments are extracted and stored. Specifically, these segments relate to the breakout and port configuration. This approach ensures a cleaner and more focused /etc/sonic/config_db.json, mitigating the presence of unintended configurations.
Previously, our method involved persisting the entirety of the running configuration into
/etc/sonic/config_db.jsonby runningconfig savein a task. This approach led to undesired configurations being retained, especially noticeable after a switch reboot. A key example of such undesired configurations arises frommetal-core.To refine this, we have now transitioned to a selective persistence strategy. Instead of saving the entire running configuration, only crucial segments are extracted and stored. Specifically, these segments relate to the breakout and port configuration. This approach ensures a cleaner and more focused
/etc/sonic/config_db.json, mitigating the presence of unintended configurations.