Glossary

Active Directory User

An authenticated user in Active Directory that has been assigned a user account in Commander.

Administrator

An assigned role to a user that allows that user to carry out almost all functions without restriction in Commander. For more information, see Understanding Commander Access Control.

Alert

A message generated by Commander when an event or task that has been started requires attention. Alerts are sent out by Commander when a policy has been triggered.

Approver

A level of access rights assigned role to an administrative user in Commander that allows that user to change the approval status of VMs. For more information, see Assigning Access Rights to Administrative Users.

Auditor

In Commander, an auditor is a role assigned to a user. The auditor has read-only access to the functions. For more information, see Understanding Commander Access Control.

Authentication

The process of attempting to verify the digital identity of the sender of a communication such as a request to log in. The sender being authenticated may be a person using a computer, a computer itself, or a computer program.

Authorization

The process of verifying that a known person has the authority to perform a certain operation. Authorization can't occur without authentication.

Availability Set

Azure's method of ensuring both fault tolerance and service availability during upgrade. You have the option of specifying an availability set for Service Catalog components and when deploying an Azure image in Commander.

Billing Record

A record of current VM costs, generated nightly from values entered in cost models. Billing records are also generated automatically for retrieved historical events. Billing records form the basis for reports such as the VM Billing Report and the VM Comparative Economics Report. See Configuring Cost Models for details. If billing data is retrieved, billing costs replace estimated costs in billing records for AWS and Azure. For GCP, however, VM billing records always use estimated costs, rather than historical costs.

Cloud Template

An AWS CloudFormation template or an ARM template.

Custom Component

A component that is not managed by Commander. Custom components include both non-virtual assets (like a phone) and tasks that modify existing assets (like the installation of a database instance on an existing server). Custom components are different from VM and virtual service components: once a request for a custom component is completed, the custom component is not displayed or tracked in Commander or the Service Portal. See also Service.

Storage View

A view of datastores in the Infrastructure hierarchy. Previously the Datastore view.

For vCenter, the Storage view also shows out-of-inventory VMs (VMs that exist on a datastore but don't exist in vCenter's inventory).

For AWS, this view shows both the EBS and S3 datastores. For more information on AWS storage, see the Root Device Type property for VMs.

For Azure, this view shows both managed and unmanaged storage. The view is region-centric, which means that it doesn't provide a resource group-centric view of storage accounts. For more information on Azure storage, see Managing Azure with Embotics Commander.

Deployed Name

The name of a service or component after it's deployed. Not to be confused with the published name for a service or component that appears in the Service Catalog.

Applications View

A hierarchical view of deployed resources.

Managed System Type

Details

AWS

A hierarchy of AWS templates, VMs and stacks. For each AWS region, this view shows:

  • the Private Templates folder, containing private AMIs (Amazon Machine Images) created in the AWS console. AWS provides a set of public AMIs; any AMIs you create in the AWS console are private AMIs. Only private AMIs are available in Commander for deployment and for addition to the Service Catalog.
  • Availability zones, containing Amazon EC2 instances (identified as VMs in Commander), AWS CloudFormation stacks and Amazon RDS databases. Does not include load balancers or Auto Scaling Groups, which can span availability zones; these objects are displayed only in the Infrastructure View.

Note that stacks don't have children in the tree, because stack resources are already displayed in the appropriate location in the tree.

Google Cloud Platform

An application-centric view of GCP resources (including VMs and deployments), logically grouped by organization, folder and project.

Note that deployments don't have children in the tree, because deployment resources are already displayed in the appropriate location in the tree.

Kubernetes

An application-centric view of the Kubernetes cluster, composed of pods, containers and other resources, broken down by namespace.

Microsoft Azure

A hierarchy of Azure popular public images, resource groups, private templates, virtual networks and VMs. Because this view is resource group-centric, it's the view you should use for lifecycle management.

Commander supports only VM images, not OS images.

Resource groups are created in a specific region, but the contents of a resource group can span regions, so regions are not shown in this view. In the Applications view, the children of a resource group are shown beneath the resource group in the hierarchy (in contrast to the Infrastructure View). Because virtual networks may not be in the same resource group as the VMs within it, virtual networks and VMs are displayed at the same level in this view, right under the resource group.

Note that when you click a resource group in any view, you see a list of its resources on its Resources tab.

Hyper-V SCVMM

Templates in the SCVMM library.

VMware vCenter

A hierarchy of all folders, VMs and templates.

Enterprise Admin

One of the Commander roles. For more information, see Understanding Commander Access Control.

Events

A record of activities that have occurred in your virtualized infrastructure. You can see all events that have taken place through the information panel accessed through the historical Events tab.

Fingerprint

A unique ID number assigned to a VM. Commander uses a fingerprint to track a VM and all its associated images for history and audit purposes.

Hot Add

A feature allowing you to add CPU and/or memory resources for a vCenter VM while the machine is powered on. The CPU Hot Plug and Memory Hot Plug properties must be set for the VM in vCenter to enable this feature.

Intelligent Placement

Ensures that service requests are deployed to the best location.

Lifespan Cost

The estimated cost for the entire life of a requested service, rather than for a cost period such as annually or monthly. To learn how to display lifespan cost during the service request process, see Customizing Service Request Forms.

Local User

A user set up locally through Commander.

Managed System

A VMware vCenter or vSphere Server, or a Microsoft SCVMM Server.

Metadata

Information assigned to objects in your virtualized infrastructure, such as custom attributes, expiry dates, and ownership. Metadata can be assigned directly to objects, configured in service catalog entries, or assigned through workflows and policy.

Network Zone

A simple label that describe a network's purpose within your infrastructure — for example, DMZ, Corporate Intranet, Storage and Production. Network zones enable your users to select a network when requesting a new service, help administrators keep track of a large list of networks, simplify automated deployment in multi-tenant environments and simplify automated deployment when using multiple managed system types. See Configuring Networks.

Infrastructure View

A hierarchical view of the entire compute infrastructure. Use this view for daily operations.

Managed System Type

Details

AWS

A hierarchy of AWS regions, stacks, Virtual Private Clouds (VPCs), Auto Scaling Groups, VMs (Amazon EC2 instances), load balancers (Amazon Elastic Load Balancers) and databases (Amazon RDS database instances). Does not include templates (AMIs). See also note below.

Stacks don't have children in the tree, because stack resources are already displayed in the appropriate location in the tree.

GCP

A hierarchy of GCP resources, grouped by region and zone. Because this view is region-centric, it's the view you should use when thinking about geographic distribution. GCP deployments are not shown in this view.

Kubernetes

An infrastructure-centric view showing the logical grouping of pods and containers, based on the node where they reside.

Microsoft Azure

A hierarchy of Azure regions, resource groups, virtual networks, VMs and templates (images). Because this view is region-centric, it's the view you should use when thinking about geographic distribution.

Resource groups are created in a specific region, but the contents of a resource group can span regions. Therefore, in the Infrastructure View, resource groups don't have children (in contrast to the Applications view). When you click a resource group in any view, you can see a list of its resources on its Resources tab.

Hyper-V SCVMM

Hosts, clusters and any folders or datacenters that you have created in the hierarchy. Shows VMs and templates in the hierarchy.

VMware vCenter

Hosts, clusters, resource pools and any folders or datacenters that you have created in vCenter. Shows VMs and templates in the hierarchy.

Operator

An assigned role that allows the user to carry out day-to-day operational activities in Commander. For more information, see Understanding Commander Access Control.

Organization

A group of consumers with a common business purpose. Organizations allow you to:

  • isolate data for your consumer groups
  • delegate administrative tasks to consumers
  • set up distinct cloud automation configurations for your consumer groups

Placement attribute

A special kind of custom attribute used in Intelligent Placement. By identifying the capabilities of each deployment destination and the requirements of a service, placement attributes help ensure that service requests are deployed to the best destination. For example, placement attributes can help Commander decide whether to deploy to public or private cloud, or which datacenter or geographic region is best suited to a service.

Service

A service is a container for IT assets — something that is requested, approved, deployed and completed as a unit. A service can consist of anything from a single VM to a combination of service components, such as:

  • multi-cloud templates
  • VM templates
  • Amazon Marketplace AMIs
  • virtual service templates
  • cloud templates (CloudFormation templates, ARM templates and GCP deployment configurations)
  • OVA/OVF templates
  • custom components — used to represent both non-virtual assets (such as a phone) as well as tasks that modify existing assets (such as the installation of a database instance on an existing server)
  • Custom components are different from VM and virtual service components. Once a request for a custom component is completed, the custom component isn't displayed or tracked in Commander or the Service Portal.

A service can be predefined (for example, as a vApp in vCenter) or built from individual components in Commander.

A few example services:

  • new hire service — everything a new hire needs, such as a desktop machine, installed software applications and a phone
  • lab service — everything required to set up a software testing lab environment

Storage View

A view of storage resources in the Infrastructure hierarchy.

  • AWS: Shows both the EBS and S3 datastores. For more information on AWS storage, see the Root Device Type property for VMs.
  • Google Cloud Platform: Shows storage resources grouped by region. For GCP, all storage resources are displayed under the Managed folder. Both regional and zonal storage resources are organized into Commander datastores, which are logical groups aggregating persistent VM disks. When you look at a datastore, you can see which VMs have persistent disks, as well as the total storage usage in that zone or region. Disks for images and local disks are not attached to any datastore, so they're not visible in the Storage view.
  • Kubernetes: Provides a storage footprint view of all volumes in the cluster, as well as a list of volumes for each pod, broken down by volume type. It doesn't show volume backings or storage classes.
  • Azure: Shows both managed and unmanaged storage. The view is region-centric, which means that it doesn't provide a resource group–centric view of storage accounts. For more information on Azure storage, see Storage Accounts.
  • vCenter: The Unmanaged folder in this view shows out-of-inventory VMs (VMs that exist on a datastore but don't exist in vCenter's inventory).

Superuser

An account that allows a user to carry out all Commander functions without restriction. One superuser account is always maintained locally on Commander. For more information, see Understanding Commander Access Control.

Suspect

A security state that can be applied to a VM, either manually or through the Suspect Policy, to indicate that the VM doesn't meet the operating standards for your environment.

Task

A user-initiated action that appears under the Tasks tab.

VM Group

A container for VMs used to automate automating policy, lifecycle management, service request fulfillment and capacity management. For more information, see Managing Service Groups.