AsterNOS Datastores
此内容尚不支持你的语言。
Running
Section titled “Running”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.
Startup
Section titled “Startup”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.
Operational
Section titled “Operational”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)
Relationships Between Datastores
Section titled “Relationships Between Datastores”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/>.