Active Directory User

An authenticated user in Active Directory that has been assigned a user account in Embotics® vCommander®.

Administrator

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

Affinity Group

Affinity groups allow you to group your Microsoft Azure services to optimize performance. All cloud services and VMs within an affinity group are placed close to one another, thereby reducing latency and increasing performance. When deploying an Azure image to a VM in vCommander, you can choose an affinity group as the target destination.

Alert

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

Approver

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

Auditor

In vCommander, an auditor is a role assigned to a user. The auditor has read-only access to the functions. For more information, see Understanding Embotics® vCommander® 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 cannot 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 vCommander.

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.

Cloud Template

An AWS CloudFormation template or an ARM template.

Custom Component

A component that is not managed by vCommander. 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 vCommander or the Service Portal. See also Service.

Datastore View

A view of datastores in the Operational hierarchy.

For vCenter, the Datastore view also shows out-of-inventory VMs (VMs that exist on a datastore but do not 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 Resource Manager, this view shows both managed and unmanaged storage. The view is region-centric, which means that it does not provide a resource group–centric view of storage accounts. For more information on ARM storage, see Managing Azure with Embotics® vCommander®.

Deployed Name

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

Endpoint

Endpoints handle the inbound network traffic to an Azure VM, consisting of DNS, IP address, protocol and port settings. Endpoints are configured in service catalog entries and during manual provisioning.

Enterprise Administrator

An enterprise administrator is a Embotics® vCommander® user account that has most of the functions of a superuser account. For more information, see Understanding Embotics® vCommander® 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. vCommander 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.

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

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.

Operational View

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

Managed System Type

Details

VMware vCenter

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

Hyper-V SCVMM

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

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

Note that stacks do not have children in the tree, because stack resources are already displayed in the appropriate location in the tree.

Microsoft Azure Resource Manager (ARM)

A hierarchy of ARM 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 Operational View, resource groups do not have children (in contrast to the VMs and Templates view). Note that when you click on a resource group in any view, you can see a list of its resources on its Resources tab.

Microsoft Azure Service Manager (Classic)

A hierarchy of Azure regions, affinity groups, virtual networks, virtual services (cloud services), VMs (instances) and templates (images). Cloud services are displayed under the element where they were deployed. Does not include templates (Azure images).

Operator

An assigned role that allows the user to carry out day-to-day operational activities in vCommander. For more information, see Understanding Embotics® vCommander® 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

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:

multiple VMs

virtual services (vApps and cloud services)

cloud templates (CloudFormation and ARM 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)

NotePencil-smallCustom 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 vCommander or the Service Portal.

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

A few example services:

a new hire service — everything a new hire needs, such as a desktop machine, installed software applications and a phone

a lab service — everything required to set up a software testing lab environment

Superuser

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

Suspect

vCommander comes with a built-in security state of Suspect. You can apply Suspect to a VM,  either manually or through the Suspect Policy, to indicate that the VM does not 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.

VMs and Templates View

A hierarchy of VMs and templates. Use this view for deployment.

Managed System Type

Details

VMware vCenter

A hierarchy of all folders, VMs and templates

Hyper-V SCVMM

Templates in the SCVMM library

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 vCommander for deployment and for addition to the Service Catalog.

Availability zones, containing Amazon EC2 instances (identified as VMs in vCommander), 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 Operational View.

Note that stacks do not have children in the tree, because stack resources are already displayed in the appropriate location in the tree.

Microsoft Azure Resource Manager (ARM)

A hierarchy of ARM 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.

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 VMs and Templates View, the children of a resource group are shown beneath the resource group in the hierarchy (in contrast to the Operational 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 on a resource group in any view, you can see a list of its resources on its Resources tab.

Microsoft Azure Service Manager (Classic)

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

the Private Templates folder, containing private images created in the Azure Management Portal. Azure provides a set of public images; any images you create in the Azure Portal are private images. Only private images are available in vCommander for deployment and for addition to the Service Catalog.

Affinity groups, containing cloud services and their instances (which are identified as VMs in vCommander). Can also contain virtual networks.

Virtual networks, containing cloud services and their instances

Cloud services and their instances that are deployed in the region itself