跳转到内容
Ask AI

AsterNOS Datastores

此内容尚不支持你的语言。

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.

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 or .

This database is supported by Distinct Startup.

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)

When the system is starting, it automatically copies the data from to .

Then the system uses the data in as the current effective configuration, and do a full-sync to operational datastore.

When user modifies the configuration via to , the system will do a increase-sync to operational datastore.

All backend processes read the data from database, such as swss/ hostcfgd/ featured process.

When user performs or to , the system only updates the data in database, and does not change the data in or .