An operator may create a backup and save it as a "last known good" state, knowing that he/she can easily return to that state should an upgrade fail. Backup may be useful, for example, when performing high-risk operations on a pod such as upgrading software. Backup and Restore are concerned with storing state at a specific time and returning the system to that state on demand. ![]() Fault Tolerance ensures that a component remains operational in the case of failure. Any backup solution for XOS must encompass not only the traditional database aspects, but also address contributions that are unique to XOS.įault Tolerance and Backup are two different goals. XOS acts as a coordinator for these services and enforces rules (such as versioning and dependency enforcement) on service behavior. Services augment XOS, with not only schema but also custom logic. ![]() ![]() For example, while XOS maintains a database schema and stores data within that schema, XOS is also designed to be extensible in ways that a traditional database may not be. XOS shares many similarities with a traditional database system, but XOS also provides unique capabilities and challenges that a traditional database system may not have. ![]() This page documents the requirements, design, and implementation of the XOS backup / restore feature. Even the user accounts that secure access to the XOS API are part of the data model. This typically includes configuration of services such as ONOS and VOLTHA as well as operational data such as subscriber state. XOS holds authoritative state for many components in a deployment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |