Most of them areoutdated, but provide historical design context.
They arenotuser documentation and should not be treated as such.
Documentation is available here.
StoragePool Metadata Removal
Until oVirt 3.5 the Storage Pool (Data Center) information was maintained in the engine database and stored in different ways in the Master Domain. In the larger scope of removing the SPM (Storage Pool Manager) and the Master Domain Role, the goal of this feature is to decommission the Storage Pool Metadata (and its dependency on the Master Domain).
- Name: Federico Simoncelli
- Email: email@example.com
- Released in oVirt 3.5
connectStoragePoolwill receive a new argument enumerating the storage domains that are part of the pool and their status (
refreshStoragePoolis now useless (as there’s no metadata on the storage anymore), on Data Center 3.5
connectStoragePoolwill be used also for refreshing.
- Since it’s not possible to periodically refresh the Storage Domains map from the storage anymore it’s now mandatory that all the hosts will receive these information with the
connectStoragePoolcommand (especially on the activation/deactivation of the domains). The engine will include a new logic to synchronize the hosts sending
connectStoragePoolwhen required (analyzing the
- The new Storage Domain statuses “Preparing For Maintenance”, “Activating” and “Detaching” will be introduced in order to mark those domains that are in transition.
- full compatibility with the old
reconstructMasterwill be maintained for Data Center 3.4 (and lower).
Benefit to oVirt
- This feature will enable the SPM and Master Domain removal.
- Robustness as some complex flows will be dropped (
reconstructMaster) and consistency (the metadata is kept in the engine database).