Skip to content
This repository has been archived by the owner on Nov 25, 2021. It is now read-only.

User's guide

Tomas Jelinek edited this page Mar 29, 2017 · 6 revisions
Table of Contents

Setup
Remote Consoles
Augmented Reality
Dashboard
Explanation of Dashboard

Setup

After successfully installing the application, you need to set the connection details up:

  • 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 polled1: the maximum number of events polled in each main sync or on main events tab

  • Max events stored1: the maximum number of events stored on a device

  • 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.

[1]: max polled = max stored before moVirt 1.8

Remote Consoles

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

Augmented Reality

You can use your smartphone/tablet camera to help managing your servers. Follow these steps to access augmented reality:

  1. 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).
  1. Print and stick codes to physical servers.
  2. Open Scan Codes option in moVirt and you are ready.

Dashboard

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.

Physical Resources

Physical CPU

Z% Available od Y%
  • Z = average cpu usage of all hosts
  • Y = always 100%
X% (Allocated W%)
  • X = overcommit; (up vm cores1) / (all physical cores3)
  • W = (all vm cores2) / (all physical cores3)
V% Used
  • 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

Physical Memory

Z Available od Y GiB
  • Z = available memory of all hosts
  • Y = total memory of all hosts
X% (Allocated W%)
  • X = overcommit; (all up vm total memory1) / (all physical memory3)
  • W = (all vm total memory2) / (all physical memory3)
V GiB Used
  • 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

Physical Storage

Z Available od Y GiB
  • Z = available space in all active Domains1
  • Y = total space in all active Domains1
X GiB Used
  • X = Y - Z

[1]: applies to Data Storage Domains with status ACTIVE

Running Vms

VMs CPU

Z% Available od Y%
  • Z = average cpu usage of all running vms1
  • Y = always 100%
X% Used
  • X = Y - Z

[1]: Virtual Machines with status UP

VMs Memory

Z Available od Y GiB
  • Z = available memory of all running vms1
  • Y = total memory of all running vms1
X GiB Used
  • X = Y - Z

[1]: Virtual Machines with status UP

VMs Storage

Z Available od Y GiB
  • Z = available space of all Disks1
  • Y = total space space of all Disks1
X GiB Used
  • X = Y - Z

[1]: Does not include snapshots