Skip to main content

Red Hat Virtualization

The importer for Red Hat Virtualization allows you to import your current virtualization infrastructure into Txture seamlessly.

RHV Data source

The data source establishes a connection to Red Hat Virtualization (RHEV) for extracting data.

For the connection this Data Source needs the URL (e.g. https://rhevm.customer.url/ovirt-engine/api, the "customer.url" must be replaced by the according url and the "/ovirt-engine/api" must not be removed) together with Username (can be found in the top right corner of the console - e.g. "user@internal-authz": the user required for the datasource in this case would be "user@internal") and Password.

Importable assets

As any other importer, the RHV importer allows certain assets to be imported from your RHV installation. These assets are listed in the following table and be arbitrarily mapped to your structure.

Asset-TypeDescription
VMVirtual machines. It is possible to choose "only running", if you do, only the virtual machines which are actually running (in this API the status is called "UP") at the given moment will be imported.
DISKDisks providing storage.
NETWORKNetworks. Red Hat Enterprise Virtualization provides networking functionality between virtual machines, virtualization hosts, and wider networks. For detailled information please have a look at the documentation of Red Hat.
CLUSTERClusters are collections of physical hosts that share the same storage domains and have the same type of CPU. For detailled information please have a look at the documentation of Red Hat.
HOSTHosts. Physical server on which virtual machines run.
DATA_CENTERData centers. A data center is the highest level virtual entity for all physical and logical resources within a managed virtual environment. For detailled information please have a look at the documentation of Red Hat.

Of course, the importer also allows to cover the connections between the above assets. Currently, the following links can be imported:

ShortcutDescription
DISK_TO_VMLinks between disks and virtual machines will be established: which disk is attached to which virtual machine?
CLUSTER_TO_VMLinks between clusters and virtual machines will be established: which cluster is connected to which virtual machine?
HOST_TO_VMLinks between hosts and virtual machines will be established: which host is connected to which virtual machine?
NETWORK_TO_CLUSTERLinks between networks and clusters will be established: which network is connected to which cluster?
CLUSTER_TO_HOSTLinks between clusters and hosts will be established: which cluster is connected to which host?
NETWORK_TO_HOSTLinks between networks and hosts will be established: which network is connected to which host?
CLUSTER_TO_DATACENTERLinks between clusters and data centers will be established: which cluster is connected to which data center?
NETWORK_TO_DATACENTERLinks between networks and data centers will be established: which network is connected to which data center?