Let’s try to understand the databases provided inside Oracle Linux Virtualization Manager. There are two PostGreSQL databases in play. The first one named engine is created as part of the engine configuration process. And if you choose to install the ovirt_engine DWH package, a second database called ovirt_engine_history is created.
The engine database is where the persistent information about the Oracle Linux Virtualization Manager environment is stored. This includes details about its configuration, current state, and performance metrics. It continuously collects historical configuration information and statistical metrics updating them every minute.
On the other hand, the orvit_engine_history database serves as a management history database. It stores historical configuration information and statistical metrics for data centers, clusters, and hosts. This data can be accessed by any application that needs historical insights into your virtualization environment.
Now, here is an interesting feature that is both history and engine databases can be run on a remote host. This helps reduce the load on the engine host enhancing performance and scalability. But remember, it’s essential note to remember that running these databases on remote host is currently in technology preview feature, meaning it’s still under development and may have limitations.
Recent Comments