AsterNOS Datastores

\<font color="#1d50a2">running\</font> asternos support running datastore, which stores the effective running configurations delivered through netconf the data in this database can be modified, and the modifications take effect immediately this is the only mandatory standard database \<font color="#1d50a2">startup\</font> asternos support startup datastore, which stores the configuration that will take effect after next startup the data in this database cannot be modified you can only replace the database by performing the \<save config> or \<copy config> this database is supported by distinct startup \<font color="#1d50a2">operational\</font> this is the default datastore for all read operations it contains system state as well as configs from sources other than user configuration (e g system default and learned config from clusters) \<font color="#1d50a2">relationships between datastores\</font> when the system is starting, it automatically copies the data from \<startup/> to \<running/> then the system uses the data in \<running/> as the current effective configuration, and do a full sync to operational datastore when user modifies the configuration via \<edit config> to \<running/>, the system will do a increase sync to operational datastore all backend processes read the data from \<operational/> database, such as swss/ hostcfgd/ featured process when user performs \<copy config> or \<save config> to \<startup/>, the system only updates the data in \<startup/> database, and does not change the data in \<running/> or \<operational/> warning the operational db is set to read only, the user can't do write operations on it