-
Notifications
You must be signed in to change notification settings - Fork 33
User's guide
Setup
Remote Consoles
Augmented Reality
Dashboard
Explanation of Dashboard
After successfully installing the application, you need to set the connection details up:
- API URL: http://host:port/ovirt-engine/api
- Username: name@domain - e.g. admin@internal
- Password: your password
- Certificate Management: download trusted certificate from the engine or supply your own
You can also set optional settings:
- Poll Events: leave checked if you want events in the main sync
- Connection Notifications: shows notification first time the connection is lost
- Periodic Sync: periodic sync when the device is online
- Sync Interval: interval in minutes
- Max events locally: the maximum number of events stored locally
- Events Search Query: poll events for the search query. E.g. severity > warning, see API 3.0 Documentation for syntax.
- Max VMs polled: maximum number of VMs polled.
- VMs Search Query: poll VMs for the search query. E.g. name = "production", see API 3.0 Documentation for syntax.
Follow these steps to connect to remote console:
#####VNC
- Install bVNC from Google Play
- Start up VM and refresh it in moVirt
- Click Vnc Console button in VM's menu
#####SPICE
- Install aSPICE from Google Play
- Start up VM and refresh it in moVirt
- Click Spice Console button in VM's menu
You can use your smartphone/tablet camera to help managing your servers. Follow these steps to access augmented reality:
- Generate Data Matrix codes for each host you running (this step will be simplified in future).
- Open
http://host:port/ovirt-engine/api/hosts
in your browser and find host ID.
- Make data matrix codes with any online generator containing these IDs as a text (one code for each ID).
- Print and stick codes to physical servers.
- Open Scan Codes option in moVirt and you are ready.
Consists of
-
Physical Overview1
- Overview1: shows state of all entities
- Most Utilized Hosts1: hosts sorted by cpu usage
- Physical Resources: shows utilization of all hosts and storage domains
-
Virtual Overview1
- Overview1: shows state of all entities
- Most Utilized Vms1: vms sorted by cpu usage
- Running Vms: shows utilization of running vms and all disks
[1]: only for tablets
Notes
- moVirt uses recently fetched data to compute the dashboard compared to the oVirt's webadmin which uses average over the last 5 minutes.
- Dashboard is affected by the settings, i.e. by the queries and by the number of vms/events downloaded
##Explanation of Dashboard
Both tablet and phone version include physical resources and running vms utilization.
They will be described bellow.
- Z = average cpu usage of all hosts
- Y = always 100%
- X = overcommit; (up vm cores1) / (all physical cores3)
- W = (all vm cores2) / (all physical cores3)
- V = Y - Z
[1]: Allocated cores of running Virtual Machines (with status UP)
[2]: Maximum number of cores that can be allocated to all Virtual Machines
[3]: Physical cores of all Hosts
- Z = available memory of all hosts
- Y = total memory of all hosts
- X = overcommit; (all up vm total memory1) / (all physical memory3)
- W = (all vm total memory2) / (all physical memory3)
- V = Y - Z
[1]: Total memory of running Virtual Machines (with status UP)
[2]: Total memory of all Virtual Machines
[3]: Total memory of all Hosts
- Z = available space in all active Domains1
- Y = total space in all active Domains1
- X = Y - Z
[1]: applies to Data Storage Domains with status ACTIVE
- Z = average cpu usage of all running vms1
- Y = always 100%
- X = Y - Z
[1]: Virtual Machines with status UP
- Z = available memory of all running vms1
- Y = total memory of all running vms1
- X = Y - Z
[1]: Virtual Machines with status UP
- Z = available space of all Disks1
- Y = total space space of all Disks1
- X = Y - Z
[1]: Does not include snapshots