Most of them areoutdated, but provide historical design context.
They arenotuser documentation and should not be treated as such.
Documentation is available here.
Hosted Engine related changes in the UI
Several changes were made to the Webadmin UI to make it easier to see hosted engine related entities.
- New icons showing:
- which VM is the hosted engine
- which storage domain contains disks used by the hosted engine
- which hosts are configured to run the hosted engine VM
- The buttons for enabling and disabling hosted engine global maintenance mode were moved to the context menu of a host
- Only one of the buttons is enabled, depending on the actual state.
- Hosts can be filtered by hosted engine deployment.
- Name: Andrej Krejcir (akrejcir)
- Email: email@example.com
Added icons make it easier to see hosted engine related entities in the webadmin. These icons were added to the webadmin UI:
Icon showing which VM is actually the hosted engine, regardless of its name.
Icon showing which storage domain contains the disks used by the hosted engine.
Icons showing which hosts are configured to run the hosted engine VM.
Global maintenance buttons
The buttons for enabling and disabling hosted engine global maintenance mode were moved to the host context menu in the host tab, because it was easier to implement their state.
All hosts with hosted engine deployment can be filtered using the flag:
Host: he_deployed = true.
Benefit to oVirt
It is now easily visible which entities are related to the hosted engine and they can be filtered out from the rest if needed.
Adding the icon for VM was simple, as the VM entity already has a field indicating if it is the hosted engine. Similarly for the hosts, the host entity has fields indicating if the hosted engine can run on it and the mode of the maintenance.
The storage domain did not have such field, so it was added. A new view was added to the DB which contains the ids of storage domains with disks used by the hosted engine.
Documentation / External references