1. Methods Available for Use with ManageIQ

Methods can be used from within ManageIQ to create custom actions and workflows for the objects managed for your ManageIQ Infrastructure.
This document describes the methods available for use in ManageIQ.
This document is organized by the object hierarchy in the Automate Model.

Users of ManageIQ can construct custom automation methods in Ruby to extend the product.
ManageIQ ships with a core set of Ruby gems used by the ManageIQ Rails Application.
The Ruby gems in this set are subject to change, and have changed since the previous version. If you are calling gems using Automate that are no longer in the ManageIQ appliance, you can install them by using the gem install command.

While gems can be imported into automation methods using require, it is recommended that the authors of the automation methods clearly document the use of gems either in the core set or a custom set.
It is the responsibility of the author of such custom automation to own the life cycle of any gem being referenced in those methods.

1.1. $evm.root

When an Automate method is launched, it has one global variable: $evm.
The $evm variable allows the method to communicate back to ManageIQ.
The $evm.root is the root object in the workspace, it provides access to the data currently loaded in the ManageIQ model.
It use the objects data to solve more complex problems by integrating with ManageIQ methods.

The following is an excerpt from the InspectMe method that can be found in the ManageIQ\System\Request namespace.
The dumpRoot method accesses the $evm.root object, and sends all of its attributes to the ManageIQ Automate log for review.
In the dumpServer Method, the inspect method is run based on the value of the miq_server obtained from the $evm.root object.

1.2. Method Hierarchy

The Automate Model inline methods have a hierarchy.
The sublevels in the hierarchy have access to the methods for itself and the levels above it.
For example, Red Hat Hosts have access to the Red Hat Host methods, Host Methods, and Base Methods.

The following nested list displays the hierarchy.

Top Level: Base

Authentication (authentication)

Private Keys (auth_private_key)

Key Pair for Clouds (auth_key_pair_cloud)

Amazon (auth_key_pair_amazon)

OpenStack (auth_key_pair_openstack)

Availability Zones (availability_zone)

Amazon (availability_zone_amazon)

OpenStack (availability_zone_openstack)

Classification (classification)

Cloud Networks (cloud_network)

Cloud Resource Quotas (cloud_resource_quota)

OpenStack (openstack_resource_quota)

Cloud Subnets (cloud_subnet)

Cloud Tenants (cloud_tenant)

Customization Templates (customization_template)

Cloud Init (customization_template_cloud_init)

Kickstart (customization_template_kickstart)

Sysprep (customization_template_sysprep)

Cluster (ems_cluster)

Event (ems_event)

Folder (ems_folder)

Providers (ext_management_system)

Cloud (ems_cloud)

Amazon (ems_amazon)

Openstack (ems_openstack)

Infrastructue (ems_infra)

Microsoft System Center VMM (ems_microsoft)

Red Hat Enterprise Virtualization (ems_redhat)

VMware vCenter (ems_vmware)

Filesystems (filesystem)

Firewall Rules (filewall_rule)

Flavors

Amazon (flavor_amazon)

OpenStack (flavor_openstack)

Floating IPs (floating_ip)

Amazon (floating_ip_amazon)

OpenStack (floating_ip_openstack)

Guest Applications (guest_application)

Guest Devices (guest_device)

Hardware (hardware)

Hosts (host)

Red Hat Enterprise Virtualization (host_redhat)

VMware (host_vmware)

VMware ESX (host_vmware_esx)

ISO Images (iso_image)

Jobs (job)

LANs (lan)

Groups (miq_group)

Policies (miq_policy)

Proxies (miq_proxy)

Requests (miq_request)

Automation (automation_request)

Host Provisioning (miq_host_provision_request)

VM Provisioning (miq_provision_request)

VM Templates (miq_provision_request_template)

Service Reconfiguration (service_reconfigure_request)

Service Template Provisioning (service_template_provision_request)

VM Migration (vm_migrate_request)

VM Reconfiguration (vm_reconfigure_request)

Request Task (miq_request_task)

Automation (automation_task)

Host Provisioning (miq_host_provision)

VM Provisioning (miq_provision)

Cloud (miq_provision_cloud)

Amazon (miq_provision_amazon)

OpenStack (miq_provision_openstack)

Red Hat Enterprise Virtualization (miq_provision_redhat)

Via ISO (miq_provision_redhat_via_iso)

Via PXE (miq_provision_redhat_via_pxe)

VMware (miq_provision_vmware)

Via NetApp RCU (miq_provision_vmware_via_net_app_rcu)

Via PXE (miq_provision_vmware_via_pxe)

Service Reconfiguration (service_reconfigure_task)

Service Template Provisioning (service_template_provision_task)

VM Migratation (vm_migrate_task)

VM Reconfiguration (vm_reconfigure_task)

Servers (miq_server)

Networks (network)

Operating Systems (operating_system)

PXE Images (pxe_image)

iPXE (pxe_image_ipxe)

PXELINUX (pxe_image_pxelinux)

PXE Servers (pxe_server)

Resource Pools (resource_pool)

Security Groups (security_group)

Amazon (security_group_amazon)

OpenStack (security_group_openstack)

Services (service)

Service Resources (service_resource)

Service Templates (service_template)

Snapshots (snapshot)

Storages (storage)

Switches (switch)

Users (user)

VMs or Templates (vm_or_template)

Templates (miq_template)

Cloud (template_cloud)

Amazon (template_amazon)

OpenStack (template_openstack)

Infrastructure (template_infra)

Microsoft (template_microsoft)

Red Hat Enterprise Virtualization (template_redhat)

VMware (template_vmware)

VMs (vm)

Clouds (vm_cloud)

Amazon (vm_amazon)

OpenStack (vm_openstack)

Infrastructure (vm_infra)

Microsoft (vm_microsoft)

Red Hat Enterprise Virtualization (vm_redhat)

Vmware (vm_vmware)

Windows Images (windows_images)

1.3. Base Methods

These methods may be used with all objects available in the Automate Model.

Method

Usage

inspect

Returns a string containing a list of attributes of the object. See the InspectMe method in Samples class

inspect_all

Returns all information for an object

virtual_column_names

Returns the objects virtual columns names

virtual_columns_inspect

Returns the objects virtual columns and values

reload

Returns to original object to prevent the internal object from being returned

tags(category = nil)-- this means that category is an optional parameter, with a default of nil

Returns the tags.

tag_assign(tag)

Assigns tag to the object, except for the miq_provision object, which uses add_tag(category, tag_name)

tag_unassign(tag)

Unassigns tag to the object, except for the miq_provision object, which uses clear_tag(category, tag_name)

The InspectMeSample Method uses many of the Methods shown in this document.
The method returns attributes of the ManageIQ Server and then returns attributes for the host, cluster, and virtual machine from the provider of invocation.
In many environments it is linked to a button.

Searches event log records to determine if an event has occurred x number of times within a defined time frame. Returns true if the number of matching records found are greater or equal to the specified freq_threshold, otherwise it returns false

Options values:

:message_filter_type - Must be one of "STARTS WITH", "ENDS WITH", "INCLUDES", "REGULAR EXPRESSION"

1.24. Request (miq_request)

Request objects are submitted to ManageIQ Server for processing.
After the request phase, the request becomes a task object.
The table below shows the relationship between a request object and a task object.

Request Object

Task Object

automation_request

automation_task

miq_host_provision_request

miq_host_provision

miq_provision_request

miq_provision

vm_reconfigure_request

vm_reconfigure_task

service_template_provision_request

service_template_provision_task

vm_migrate_request

vm_migrate_task

If you set something on the request object, it will be inherited by the task instance that does the work.
This may be useful if you are provisioning multiple virtual machines at a time and need to modify the same setting for all.
Otherwise, the item can be modified on the individual task.

Method

Use

add_tag(category, tag_name)

Add a tag to a provision instance by specifying the category and tag name

Example: miq_provision.add_tag(:location, "CHI")

approve(approver,reason for approval)

Approves the miq_request.

Example: $evm.root["miq_request"].approve("admin", "Auto-Approved")

approvers

Returns request approvers.

authorized?

Returns true if authorized, false if not.

clear_tag(category=nil, tag_name=nil)

Without any parameters, the clear_tag method will clear all tags from the provision request. Providing a category will clear all tags selected in that category. Clear a specific category/tag by providing it.

Example: miq_provision.clear_tag(:location, "CHI")

deny

Denies the miq_request

Example:

# Deny the request

$evm.log('info',"Request denied because of Quota")

$evm.root["miq_request"].deny("admin", "Quota Exceeded")

get_classification(category)

Works the same as get_tag(category) but the returned data is a hash with :name and :description

Returns a value from the options hash based on the name of the key name passed in. Internally many of the values are stored as an array of items. (For example, a target host would be stored as the index to the host object in the db and the display name.) Calling this method will return the first item if it is an array. For non-array values the item is returned unmodified.

Example: miq_provision_request.get_option(:number_of_cpus)

get_tag(category)

Returns the tags selected for the specified tag category.

Example: request.get_tag(:department)

Returns: ["accounting", "engineering"]

get_tags

Get all selected tags stored in a hash by category. If more than one tag is selected in a category, the hash will contain an array of tag names. Otherwise it will contain the tag name as a string.

Example: request.get_tags

Returns: {:cc⇒"001", :department⇒["accounting", "engineering"]}

miq_request

(Legacy support) Internal Note: The miq_request instance use to be a separate instance from the specific request instance (like miq_provision_request). When the classes were refactored into 1 this method was added to allow existing code and automate methods to continue to run unchanged.)

miq_request_tasks

Returns the requests tasks

options

Returns a hash containing all the options set for the current provision object

pending

Puts the object in a pending state for approval

Example:

# Raise automation event: request_pending

$evm.root["miq_request"].pending

reason

Returns reason for approval or denial of request

requester

Returns the requester

resource

Returns the resource for the request

set_message(value)

Sets the message for the request

set_option(key, value)

Sets the specified key/value pair for the object

1.24.1. Automation Request (automation_request)

Method

Use

automation_tasks

Returns objects automate tasks

1.24.2. Host Provision Request (miq_host_provision_request)

Method

Use

miq_host_provisions

Returns the miq_host_provisions objects

ci_type

Returns the cloud infrastructure type: host

1.24.3. VM Provision Request (miq_provision_request)

Method

Use

check_quota(quota_type, options={})

Returns the quota information for the specified type

ci_type

Returns the cloud infrastructure type: vm

eligible_clusters

Returns an array of available Cluster objects filtered by previously selected resources

eligible_customization_templates

Returns an array of available Customization Templates filtered by previously selected resources

eligible_folders

Returns an array of available Folder objects filtered by previously selected resources

eligible_hosts

Returns an array of available Host objects filtered by previously selected resources

eligible_iso_images

Returns an array of available ISO image objects filtered by previously selected resources

eligible_pxe_images

Returns an array of available PXE Image objects filtered by previously selected resources

eligible_pxe_servers

Returns an array of available PXE Server objects filtered by previously selected resources

eligible_resource_pools

Returns an array of available Resource Pool objects filtered by previously selected resources

eligible_resources(rsc_type)

Returns eligible resources given the type specified

eligible_storages

Returns an array of available Storage (Datastore) objects filtered by previously selected resources

eligible_windows_images

Returns an array of available Windows Image objects filtered by previously selected resources

get_folder_paths

Returns a hash where the key is an index and the value is the fully-qualified path name of the folder. (Sample: {7 ⇒ Dev/Dept1/QA, 8 ⇒ Test/Dept2/QA}) This format is useful when a fully-qualified path is required to match the folder name. For example, if you had multiple QA folders under different departments in the sample above. To find the proper QA folder you need to evaluate the entire folder path.

get_retirement_days

Returns the number of dates until retirement

miq_provision

Returns the task.

miq_request

Returns the miq_provision_requests miq_request object

set_cluster(rsc)

Set the cluster to use based on object returned from eligible_clusters

set_customization_template(rsc)

Set the customization_template to use based on object returned from eligible_customization_templates

set_folder(folder_path)

Set the folder to use based on object returned from eligible_folders. In addition, set_folder accepts the following folder types:

Folder Paths - separated by forward slashes. (Must include Data-center name.) Example: Prod/Discovered virtual machine where Prod is the Data-center name and Discovered virtual machine is the folder name.

Set the iso_image to use based on object returned from eligible_iso_images

set_pxe_image(rsc)

Set the pxe_image to use based on object returned from eligible_pxe_images

set_pxe_server(rsc)

Set the pxe_server to use based on object returned from eligible_pxe_servers

set_resource_pool(rsc)

Set the resource_pool to use based on object returned from eligible_resource_pools

set_resource(rsc)

Sets the resource for the request. (Helper method, should not be called directly)

set_retirement_days

Set the number of days until retirement.

set_storage(rsc)

Set the Datastore (storage object) to use based on object returned from eligible_storages

set_vm_notes(note)

Sets text for the VM notes (aka annotation) field

set_windows_image(rsc)

Set the windows_image to use based on object returned from eligible_windows_images

source_type

Returns the provision source type. (values are 'vm' or 'template')

src_vm_id

Returns ID of the template being cloned

target_type

Returns the provision target type. (values are 'vm' or 'template')

vm_template

Returns the requests template

1.25. Request Task (miq_request_task)

Method

Use

add_tag(category, tag_name)

Add a tag to a provision instance by specifying the category and tag name.

Example: miq_provision.add_tag(:location, "CHI")

clear_tag(category=nil, tag_name=nil)

Without any parameters, the clear_tag method will clear all tags from the provision request. Providing a category will clear all tags selected in that category. Clear a specific category/tag by providing it.

Example: miq_provision.clear_tag(:location, "CHI")

destination

Returns the destination object. (The resultant object from running the task. In the case of provisioning, this would be the newly created VM.)

execute

Executes or processes the request.

finished(msg)

Sets the task to finished with the supplied message.

get_classification(category)

Works the same as get_tag(category) but the returned data is a hash with :name and :description.

This method is the same as get_option, except that it returns the last array value.

get_option(key)

Returns a value from the options hash based on the name of the key name passed in. Internally many of the values are stored as an array of items. (For example, a target host would be stored as the index to the host object in the db and the display name.) Calling this method will return the first item if it is an array. For non-array values the item is returned unmodified.

Example: miq_provision_request.get_option(:number_of_cpus)

get_tag(category)

Returns the tags selected for the specified tag category.

Example: request.get_tag(:department)

Returns: ["accounting", "engineering"]

get_tags

Get all selected tags stored in a hash by category. If more than one tag is selected in a category, the hash will contain an array of tag names. Otherwise it will contain the tag name as a string.

Example: request.get_tag

Returns: {:cc⇒"001", :department⇒["accounting", "engineering"]}

message=(msg)

Sets the message for the request task.

miq_request

Returns the miq_request for the task.

miq_request_task

Returns the parent miq_request task.

miq_request.user_message=(msg)

Allows automate method to override the default request status message.
As a result, you can set custom messages for the progression of the state machine and its success or failure.
This message will appear as the last message for the service request.

miq_request_tasks

Returns the children miq_request tasks.

options

Returns a hash containing all the options set for the current object.

set_option(key, value)

Updates a key/value pair in the options hash for the provision object. Often the value is required to be an array.

source

Returns the source object. (The source, or input, object that the task runs against. In the case of provisioning, this would be the VM or template selected to be provisioned.)

1.25.1. Automation Task (automation_task)

Method

Use

automation_request

Returns associated automation_request object

status

Returns status of the task

1.25.2. Host Provision Task (miq_host_provision)

Method

Use

host

Returns objects host

miq_host_provision_request

Returns the request that created the task

status

Returns status of host provision

1.25.3. VM Provision Task (miq_provision)

Method

Use

check_quota(quota_type, options={})

Returns the quota information for the specified type

eligible_clusters

Returns an array of available Cluster objects filtered by previously selected resources

eligible_customization_templates

Returns an array of available Customization Templates

eligible_folders

Returns an array of available Folder objects filtered by previously selected resources

eligible_hosts

Returns an array of available Host objects filtered by previously selected resources

eligible_iso_images

Returns an array of available ISO Image objects filtered by previously selected resources

eligible_pxe_images

Returns an array of available PXE Image objects filtered by previously selected resources

eligible_pxe_servers

Returns an array of available PXE Servers filtered by previously selected resources

eligible_resource_pools

Returns an array of available Resource Pool objects filtered by previously selected resources

eligible_resources(rsc_type)

Returns the eligible resources for the resource type specified

eligible_storages

Returns an array of available Storage (Datastore) objects filtered by previously selected resources

eligible_windows_images

Returns an array of available Windows Image objects filtered by previously selected resources

get_domain_details

Returns domain information

get_domain_name

Returns domain name

get_folder_paths

Returns a hash where the key is an index and the value is the fully-qualified path name of the folder. (Sample: {7 ⇒ Dev/Dept1/QA, 8 ⇒ Test/Dept2/QA}) This format is useful when a fully-qualified path is required to match the folder name. For example, if you had multiple QA folders under different departments in the sample above. To find the proper QA folder you need to evaluate the entire folder path.

get_network_details

Returns network information

get_network_scope

Returns network scope

miq_provision_request

Returns the provision request object

set_cluster(rsc)

Set the cluster to use based on object returned from eligible_clusters

set_customization_spec(name=nil, override=false)

Sets the name of the custom spec to use as defined by its name in Virtual Center

set_customization_template(rsc)

Set the customization_template to use based on object returned from eligible_customization_templates

set_dvs(portgroup, switch = portgroup)

Set the name of the Distributed Virtual Switch (portgroup). An options <switch> name can also be passed

Example: miq_provision.set_dvs('default')

set_folder(folder_path)

Set the folder to use based on object returned from eligible_folders. In addition, set_folder accepts the following folder types:

Folder Paths - separated by forward slashes. (Must include Data-center name.) Example: Prod/Discovered virtual machine where Prod is the Data-center name and Discovered virtual machine is the folder name.

Booting OpenStack Instances from Volume

You can boot instances created in Red Hat Enterprise Linux OpenStack Platform from a specified volume from an existing selection of block volumes.
You can enable automate to pass the required parameters to OpenStack to use volumes as booting devices on an instance.

Example 2. Usage in Automate Model:

Include the following settings in the prov.set_option for provisioning instances created in OpenStack.

1.39. Virtual Machines and Templates (vm_or_template)

The following methods can be used on a virtual machine or template object.

Method

Use

changed_vm_value?

Checks the 2 most recent drift state captures , and answers whether the specified value changed between them

collect_running_processes

Collects the running processes of the object

create_snapshot(name, desc = nil)

Create a snapshot of the object. The name parameter is not used for Red Hat Virtualization virtual machines when creating a snapshot.

custom_get(key)

Get the value of specified ManageIQ Server key from the object

custom_keys

List all ManageIQ Server custom keys for the object

custom_set(key, value)

Set a custom ManageIQ Server key value

datacenter

Returns objects Datacenter

direct_service

Show the direct service relationship of the virtual machine

directories

Returns number of directories on the object

ems_blue_folder (this will be reworked to be more VMware-specific)

Returns objects blue folder from VMware. These are the folders showing in VM and Templates view in VMware

ems_cluster

Returns objects cluster

ems_custom_get(key)

Gets specified key of custom Management System Attribute

ems_custom_keys

List the custom keys defined by the Management System for the object

ems_custom_set(attribute, value)

Sets specified key and value of custom Management System Attribute

ems_folder

Returns objects folder on Management System

ems_ref_string

Returns unique identifier the Management System uses to identify this resource. For example, in VMware a VM would return a value like: "vm-26622"

event_log_threshold? (options)

Searches event log records to determine if an event has occurred x number of times within a defined time frame. Returns true if the number of matching records found are greater or equal to the specified freq_threshold, otherwise it returns false

Options values:

:message_filter_type - Must be one of "STARTS WITH", "ENDS WITH", "INCLUDES", "REGULAR EXPRESSION"

The category_create method currently does not work as expected. The user interface shows the value provided for :description in the Display Name field and the value provided for :example_text is displayed in the Description field.

1.41.1. Category and Tags Methods Example

In this example, the VMDB is checked to see if the Department category exists.
If it does, then a message is logged.
If not, the category is created and a message is logged.
Values are then added to the category.

Collect stats based on provisions running on the same day as the current request (based on scheduled date or immediate) by owner or in the same LDAP group as the owner. (Results do not include Provision Requests that have not been approved.)

Collect stats based on provision requests made the same day as the request by the same owner or LDAP group as the owner in the current request, regardless of when the provision request is scheduled to run. (Results do not include Provision Requests that have been denied.)

Appendix A: Terminology

Account Role

A designation assigned to a user allowing or restricting a user to
parts and functions of the ManageIQ console.

Action

An execution that is performed after a condition is evaluated.

Alert

ManageIQ alerts notify administrators and
monitoring systems of critical configuration changes and threshold
limits in the virtual environment. The notification can take the form
of either an email or an SNMP trap.

Analysis Profile

A customized scan of hosts, virtual machines, or instances. You can
collect information from categories, files, event logs, and registry
entries.

Cloud

A pool of on-demand and highly available computing resources. The
usage of these resources are scaled depending on the user requirements
and metered for cost.

ManageIQ appliance

A virtual machine on which the virtual management database (VMDB) and
ManageIQ server reside.

ManageIQ Console

A web-based interface into the ManageIQ appliance.

ManageIQ Role

A designation assigned to a ManageIQ server that
defines what a ManageIQ server can do.

ManageIQ Server

The application that runs on the ManageIQ
appliance and communicates with the SmartProxy and the VMDB.

Cluster

Hosts that are grouped together to provide high availability and load
balancing.

Condition

A test of criteria triggered by an event.

Discovery

Process run by the ManageIQ server which finds
virtual machine and cloud providers.

Drift

The comparison of a virtual machine, instance, host, cluster to itself
at different points in time.

Event

A trigger to check a condition.

Event Monitor

Software on the ManageIQ appliance which monitors
external providers for events and sends them to the ManageIQ server.

Host

A computer on which virtual machine monitor software is loaded.

Instance/Cloud Instance

A on-demand virtual machine based upon a predefined image and uses a
scalable set of hardware resources such as CPU, memory, networking
interfaces.

Managed/Registered VM

A virtual machine that is connected to a host and exists in the VMDB.
Also, a template that is connected to a provider and exists in the
VMDB. Note that templates cannot be connected to a host.

Managed/Unregistered VM

A virtual machine or template that resides on a repository or is no
longer connected to a provider or host and exists in the VMDB. A
virtual machine that was previously considered registered may become
unregistered if the virtual machine was removed from provider
inventory.

Provider

A computer on which software is loaded which manages multiple virtual
machines that reside on multiple hosts.

Policy

A combination of an event, a condition, and an action used to manage a
virtual machine.

Policy Profile

A set of policies.

Refresh

A process run by the ManageIQ server which checks
for relationships of the provider or host to other resources, such as
storage locations, repositories, virtual machines, or instances. It
also checks the power states of those resources.

Regions

Regions are used to create a central database for reporting and
charting. Regions are used primarily to consolidate multiple VMDBs
into one master VMDB for reporting.

A group of virtual machines across which CPU and memory resources are
allocated.

Repository

A place on a datastore resource which contains virtual machines.

SmartProxy

The SmartProxy is a software agent that acts on behalf of the ManageIQ appliance to perform actions on hosts, providers, storage and virtual machines.

The SmartProxy can be configured to reside on the ManageIQ appliance or on an ESX server version.

The SmartProxy can be deployed from the ManageIQ appliance, and provides visibility to the VMFS storage. Each storage location must have a SmartProxy with visibility to it. The SmartProxy acts on behalf of the ManageIQ appliance.

If the SmartProxy is not embedded in the ManageIQ server, it communicates with the ManageIQ appliance over HTTPS on standard port 443.

SmartState Analysis

Process run by the SmartProxy which collects the details of a virtual
machine or instance. Such details include accounts, drivers, network
information, hardware, and security patches. This process is also run
by the ManageIQ server on hosts and clusters. The
data is stored in the VMDB.

SmartTags

Descriptors that allow you to create a customized, searchable index
for the resources in your clouds and infrastructure.

Storage Location

A device, such as a VMware datastore, where digital information
resides that is connected to a resource.

Tags

Descriptive terms defined by a ManageIQ user or
the system used to categorize a resource.

Template

A template is a copy of a preconfigured virtual machine, designed to
capture installed software and software configurations, as well as the
hardware configuration, of the original virtual machine.

Unmanaged Virtual Machine

Files discovered on a datastore that do not have a virtual machine
associated with them in the VMDB. These files may be registered to a
provider that the ManageIQ server does not have
configuration information on. Possible causes may be that the provider
has not been discovered or that the provider has been discovered, but
no security credentials have been provided.

Virtual Machine

A software implementation of a system that functions similar to a
physical machine. Virtual machines utilize the hardware infrastructure
of a physical host, or a set of physical hosts, to provide a scalable
and on-demand method of system provisioning.

Virtual Management Database (VMDB)

Database used by the ManageIQ appliance to store
information about your resources, users, and anything else required to
manage your virtual enterprise.

Virtual Thumbnail

An icon divided into smaller areas that summarize the properties of a
resource.

Zones

ManageIQ Infrastructure can be organized into
zones to configure failover and to isolate traffic. Zones can be
created based on your environment. Zones can be based on geographic
location, network location, or function. When first started, new
servers are put into the default zone.