Adding the KVM Connector

This chapter contains the following sections:

Creating a RHEV KVM Cloud

Before you begin

Installation of Red Hat Enterprise Virtual Machine (VM) and Hypervisor.

Procedure

Step 1

Choose Administration > Virtual Accounts.

Step 2

On the Virtual Accounts page, click Virtual Accounts.

Step 3

Click Add (+).

Step 4

On the Add Cloud screen, choose Red Hat KVM from the Cloud Type drop-down list.

Note 

The following fields are displayed when RHEV KVM is chosen. Other cloud types display fields that are specific to that cloud type.

Step 5

On the Add Account screen, complete the following fields:

Name Description

Pod drop-down list

Choose a Pod to associate the account to from the drop-down list.

Account Name field

A unique account name.

Description field

A description of the new account.

Server Address field

The RHEV KVM server address.

Use Credentials Policy check box

Check this box if you want to use a credential policy for this account rather than enter the username and password information manually.

Credential Policy drop-down list

This field appears only when the Use Credential Policy box is checked. Choose a policy from the Credential Policy drop-down list.

Server User ID field

This field appears only when the Use Credential Policy box is unchecked. The RHEV KVM server username.

Note 

You must enter only the username in this field. Do not include the domain name with the user name. Enter the domain name in the Domain field.

Server Password field

This field appears only when the Use Credential Policy box is unchecked. The RHEV KVM server password.

Domain field

The domain associated to the new account.

Server Access Port field

The server access port used by the account (default value is 443).

Service Provider field

The service provider associated with the account

Contact field

The contact email address for the cloud.

Location field

The location of the account.

Step 6

Click Submit.

Initiating Inventory Collection for a VM

Procedure

Step 1

Choose Virtual > Compute.

Step 2

On the Compute page, choose the cloud.

Step 3

On the Compute page, click VMs.

Step 4

Click the row with the VM for which you want to request an inventory collection.
Step 5

From the More Actions drop-down list, choose Inventory Collection Request for VM.

Step 6

Click Submit.

Computing Policies

Computing policies determine the compute resources that can be used during provisioning to satisfy group or workload requirements.

As an administrator, you can define advanced policies by mixing and matching various conditions in the computing policy.


Note

We recommend that you thoroughly understand all the fields in the computing policy. Some combinations of conditions can result in no host machines being available during self-service provisioning.

Creating a RHEV KVM Computing Policy

Procedure

Step 1

Choose Policies > Virtual/Hypervisor Policies > Computing.

Step 2

On the Computing page, click RHEV KVM Computing Policy.

Step 3

Click RHEV KVM Computing Policy.

Step 4

Click Add (+).

Step 5

On the Add Policy screen, complete the following fields:

Name

Description

Policy Name field

The name of the policy.

Note 
This name is used during catalog definition

Policy Description field

The description of the policy.

Cloud Name drop-down list

Choose the cloud where resource allocation occurs.

Datacenter drop-down list

Choose a datacenter (Pod).

Cluster Scope drop-down list

Choose a type of cluster scope.

Note 
You can narrow the scope of deployment by specifying whether to use all, include selected cluster, or exclude selected clusters. Depending on the choices, a Selected Clusters field appears where the required clusters can be chosen.

Filter Conditions field

Check the check boxes for one or more conditions and set the condition that should match. Any hosts that do not meet these criteria are excluded from consideration. If more than one condition is chosen, all of the chosen conditions must match.

Deployment Options

Override Template check box

Check the check box to override the template properties. On selection, you will get additional fields to enter custom settings for CPU and memory.

Resizing Options

Allow Resizing of VM check box

Check the check box to allow VM resizing before provisioning or to resize an existing VM.

Permitted Values of No. of CPU Sockets field

The range of CPUs to use while provisioning a VM or resizing an existing VM. A range of more than 8 is visible during VM provisioning or resizing only if the chosen cloud is 5 or above and has VM version 8. Only the values specified in the box are visible.

Note 
This option appears if you choose Allow Resizing of VM.

Permitted Values of No. of Cores per Sockets field

The range of cores poermitted per socket.

Note 
This option appears if you choose Allow Resizing of VM.

Permitted Values for Memory in MB field

The range of memory to use while provisioning a VM or resizing an existing VM. For example: 512, 768, 1024, 1536, 2048, 3072, 4096, and so on. Only the values specified in the box are visible.

Note 
This option appears if you choose Allow Resizing of VM.
Step 6

Click Add.

Creating a RHEV KVM Storage Policy

Procedure

Step 1

Choose Policies > Virtual/Hypervisor Policies > Storage.

Step 2

On the Storage page, click RHEV KVM Storage Policy.

Step 3

Click Add (+).

Step 4

On the Add Policy screen, complete the following fields:

Name

Description

Policy Name field

The name of the storage policy

Policy Description field

The description of the storage policy.

Cloud Name drop-down list

Choose the cloud in which resource allocation occurs.

Datacenter drop-down list

Choose a data center.

Scope

Data Stores Scope drop-down list

Choose All, Include Selected Datastores, or Exclude Selected Datastores as the scope of deployment.

Selected Data Stores field

This field appears when you chose Include Selected Datastores or Exclude Selected Datastores from the Data Stores Scope drop-down list. Exapnd Selected Data Stores and select the appropriate datastores.

Storage Options

Filter Conditions drop-down list

Check the check boxes for one or more conditions and set the condition that should match the data store storage.
Step 5

Click Submit.

Creating a RHEV KVM Networking Policy

Procedure

Step 1

Choose Policies > Virtual/Hypervisor Policies > Network.

Step 2

On the Network page, click RHEV KVM Networking Policy.

Step 3

Click Add (+).

Step 4

On the Add Policy screen, complete the following fields:

Name Description

Policy Name field

The name of the network policy.

Policy Description field

The description of the network policy.

Cloud Name drop-down list

Choose the cloud account to which the policy applies.

Datacenter drop-down list

Choose a data center.

Network Name field

Expand Network Name, check the network that you want to use, and then click Validate.

Link State drop-down list

Choose On or OFF as the NIC link state.

Adapter Type drop-down list

Choose the adapter type. Check this option if you want to have the same Adapter Type that is available in the template.

For customizing the guest OS, while provisioning the KVM, choose Red Hat VirtiO as the adapter type.

Note 

This option is not visible if the Copy Adapter from Template option is chosen.

Step 5

Click Next.

Step 6

Expand Additional Networks and click Add (+).

Step 7

On the Add Entry to Additional Networks screen, complete the following fields:

Name Description

NIC Alias field

The name of the network policy.

Network Name field

Expand Network Name, check the network that you want to use, and then click Validate.

Link State drop-down list

Choose On or OFF as the NIC link state.

Adapter Type drop-down list

Choose the adapter type. Check this option if you want to have the same Adapter Type that is available in the template.

Note 

This option is not visible if the Copy Adapter from Template option is chosen.

Step 8

Click Submit to add the network.

Step 9

Click Next.

Step 10

Expand Guest Networks and click Add (+).

Step 11

On the Add Entry to Guest Networks screen, complete the following fields:

Name Description

Network Name field

The name of the network policy as available in the template. The name should be the same for customizing the guest OS while provisioning the KVM.

For example, if name of the network interface in the template is "eth0", the name of the network policy should be "eth0."

Boot Protocol drop-down list

Choose the type of boot protocol.

IP Address field

Enter the IP address of the network device.

Netmask field

Enter the netmask of the network device.

Gateway field

Enter the IP address of the gateway.
Step 12

Click Submit to add the policy.

Virtual Data Centers

A Virtual Data Center (VDC) is a logical grouping that combines virtual resources, operational details, rules, and policies to manage specific group requirements.

A group or organization can manage multiple VDCs, images, templates, and policies. Organizations can allocate quotas and assign resource limits for individual groups at the VDC level.

You can also define approvers specific to a VDC. The approvers assigned to a particular VDC must approve all service requests from users for VM provisioning.


Note

There is a default VDC in Cisco UCS Director, and all discovered VMs are part of this default VDC. Discovered VMs are VMs that are created outside of Cisco UCS Director or were already created on VMware vCenter before Cisco UCS Director was installed. Cisco UCS Director automatically discovers such VMs and adds them to the default VDC.

A VM that is provisioned using a service request can be associated with a specific VDC. When you create a service request, you can choose the VDC on which this VM is provisioned. You can view a list of the VDCs that are available for a particular group and choose the required VDC when provisioning VMs.

Creating a RHEV KVM Virtual Pod

In this task, you specify deployment, storage, network, and computing policies. Refer to the Cisco UCS Director System Administration Guide for additional information.

Procedure

Step 1

Choose Policies > Virtual/Hypervisor Policies > Virtual Data Centers.

Step 2

On the Virtual Data Centers page, click vDC.

Step 3

Click Add.

Step 4

On the Add vDC screen, choose Red Hat KVM from the Account Type drop-down list.

Step 5

Click Submit.

Step 6

On the Add vDC screen, complete the following fields:

Name Description

vDC Name field

The name of the VDC.

After entering the name, it cannot be edited.

vDC Locked check box

Check the check box to deny the use of the VDC for any further deployments. Actions on existing VMs, within this VDC, are disabled. Uncheck the check box to allow the use of the VDC for further deployments.

vDC Description field

The VDC-specific description.

Group field

Expand Group and check the group for which the VDC is being set up. Click the + icon to add a group.

Cloud Name drop-down list

Choose the cloud on which the VDC is being set up.

Approvers and Contacts

First Level Approver(s) field

Expand First Level Approvers and check each user who must approve the service request at first level.

Second Level Approver(s) field

Expand Second Level Approver(s) and check each user who must approve the service request at second level.

Approval required from all the users check box

If checked, requires approval from all users.

Number of Approval Request Reminders drop-down list

Choose the number of reminders that has to be sent at the specified interval. Set the reminder to zero to send the reminder email at the specified interval till the request is approved or rejected.

Reminder Intervals (Hours) drop-down list

The time interval to send the next request approval reminder email.

Provider Support Email Address field

The contact or user’s email address. The person who is notified about VM provisioning using this VDC.

Copy Notifications to Email Address field

The second contact’s email for copying notifications about this VDC.

Policies

Computing Policy drop-down list

Choose the computing policy applicable to the VDC.

Network Policy drop-down list

Choose the network policy applicable to the VDC.

Storage Policy drop-down list

Choose the storage policy applicable to the VDC.

System Policy drop-down list

Choose the system policy applicable to the VDC.

VM Management Policy drop-down list

Choose the VM management policy applicable to the VDC

End User Self-Service Policies drop-down list

Choose an end user policy.

Creating a KVM System Policy

Procedure

Step 1

Choose Policies > Virtual/Hypervisor Policies > Service Delivery.

Step 2

On the Service Delivery page, click RHEV KVM System Policy.

Step 3

Click Add.

Step 4

On the Add Policy screen, complete the following fields:

Name Description

Policy Name field

The name for the KVM system policy.

Policy Description field

The description of the KVM system policy

VM Name Template field

The VM name template to use. Cisco UCS Director allows automatically created using a set of variable names. Each variable must be enclosed in ${VARIABLE_NAME}. For example: vm-${GROUP_NAME}-SR${SR_ID}.

Cloud Name drop-down list

Choose a cloud from the drop-down list.

Recycle VM Name check box

By default, decommissioned VM names that were previously provisioned are used when creating a new VM. Uncheck this check box if you do not want to recycle previously used VM names.

Host Name Template field

The host name template to use. For example: host-${GROUP_NAME}-SR${SR_ID}.

DNS Domain field

The name of the DNS domain.

DNS Server List field

The DNS server list.
Step 5

Click Submit.

About Managing Catalogs

You can self-provision virtual machines (VMs) and bare metal (BM) servers using predefined catalog items. Only a system administrator can create a catalog. A catalog defines parameters, such as the cloud name and the group name to which the VM is bound.

The following folders are available by default. You cannot edit or delete them.

  • Standard

  • Advanced

  • Service Container

  • Bare Metal

To aid in managing catalogs, Cisco UCS Director allows you to group similar catalogs within a folder. While creating a catalog, you can choose to add it in a previously created folder, or create a new folder. A folder is visible in the system only when it contains a catalog.

The Manage Folder option on the Catalog page allows you to perform the following tasks:

  • Edit a folder—Modify the name of a user-created folder or the folder icon for all folders. You cannot modify the name of a default folder.

  • Delete a folder—Delete a folder from Cisco UCS Director. If this folder contains catalogs, then these catalogs are automatically moved into the folders that are available by default, based on the catalog type.

    Default folders cannot be deleted.

  • Re-order the list of folder—Change the order in which the folders are listed in the Catalog page. By default, folders are listed alphabetically.


Important

If you have upgraded Cisco UCS Director to the latest version, then all catalogs created in prior versions are grouped into folders available by default, based on their catalog types.

By default, catalogs are displayed in a tile view format. You can choose to have the catalogs displayed in a table view format as well. Use the options on the far right of the screen to switch between the table view and the tile view format. In the table view format, you can use the options to expand or collapse all folders.

Publishing a Catalog

Procedure

Step 1

Choose Policies > Catalogs.

Step 2

On the Catalogs page, click Add.

Step 3

On the Add Catalog screen, choose the Catalog Type that you want to add.

It can be one of the following:

  • Standard—Used to create catalogs for VM provisioning, using images from a list of clouds.

  • Advanced—Used to publish orchestration workflows, such as catalog items.

  • Service Container—Used to publish application containers as catalog items.

  • Bare Metal—Used to create catalogs for bare metal server provisioning.

Step 4

Click Submit.

Step 5

On the Add Catalog: Basic Information screen, complete the required fields, including the following:

Name

Description

Catalog Name field

Enter a name for the catalog.

Note 

After created, a catalog name cannot be modified.

Catalog Description field

Enter a description of the catalog.

Catalog Type drop-down list

Displays the type of catalog you previously chose. To change the catalog type, you need to cancel and restart this procedure.

Catalog Icon drop-down list

Choose from a list of icons to associate this catalog with an image. This icon is seen when you are creating a service request using this catalog.

Applied to all groups check box

Check the box to enable all groups to use this catalog. Leave it unchecked to deny its use to other groups.

Support Contact Email Address field

Enter the email address of the support contact who is notified when a service request is created using this catalog item.

Selected Groups list

Click Select to the check the checkboxes of specific user groups. The checked groups use this catalog to provision new VMs. After checking the checkboxes of user groups, click Select to return to the Add Catalog screen.

Publish to end users check box

By default, this box is checked. Uncheck this box if you do not want this catalog to be visible to users. If you do not uncheck this box, then this catalog is visible to the users of the system.

Cloud Name drop-down list

Choose the cloud with the image for VM provisioning.

Provision new VM for ISO mounting check box

Check this box to clone a new VM from a selected image. If you do not check this check box, a blank VM is created.

Image list

Click Select to the check the checkboxes of the type of image (any existing templates such as Windows, Linux, and other files that make up the image) to use when VMs are provisioned using this catalog. After checking the checkboxes of the required images, click Select to return to the Add Catalog screen.

If you are a group administrator, or a user in a group with permissions to create catalogs, this field displays images that are assigned to the group to which you belong.

If you are an MSP administrator, then this field displays images that are assigned to your MSP organization, and to the groups within the MSP organization.

Provision new VM using Content Library VM Template check box

Check this box to ensure that the new VM is provisioned using the Content Library VM Template.

If you choose this option, the Image list is hidden.

Content Library VM Template list

Choose the content library VM template.

Windows License Pool field

Enter the Windows License.

Note 

This field appears only when a Windows image is chosen. This option is not supported in the RHEV KVM Connector.

Use ReadyClone check box

Check the box to ensure that VMs are deployed using ReadyClones.

When this box is checked, the Use Linked Clone and Provision all disks in single datastore check boxes are not available for editing.

Note 

This checkbox is not visible if:

1. The selected image is not on the HX datastore.

2. The VM has multiple disks.

Use Linked Clone check box

Check the box if you want to use a linked clone.

Linked Clone or Full Clone depends on the Linked Clone selection in the Storage Policy.

Note 

This field appears only when a Snapshot image is chosen.

Provision all disks in single datastore check box

Check the box to provision all disks in a single datastore. You can also choose to use the datastores configured for each disk in the storage policy.

Note 

This field appears only if the chosen template has multiple disks. This option is not supported in the RHEV KVM Connector.

Service Container Template Name drop-down list

Choose the template from the list.

Note 

This field appears only when the chosen Catalog Type is Service Container.

Select Folder drop-down list

Choose the folder within which this catalog must be created.

Note 

The drop-down list includes names of folders that are available by default. You can either choose a folder that is available, or click Create New Folder.

On the Add New Folder screen, enter a Folder Name, choose a Folder Icon, and click Add.

Bare Metal Server Provisioning Policy drop-down list

Note 

This field appears only when the chosen Catalog Type is Bare Metal.

Configure Service Request Support Email check box

Check this box to enable the user to set the support email for sending service request status.

Step 6

Click Next.

Step 7

On the Add Catalog: Application Details screen, complete the required fields, including the following:

Name

Description

Category list

Expand the list to choose a VDC category and click Select.

Override check box

Check the box to enable the user to override the selected category while provisioning a VM using a service request.

Support Contact Email Address field

Enter the email address of the contact who is notified when a service request is created using this catalog item.

Specify OS drop-down list

Choose the type of OS installed on the VM when it is provisioned.

Note 

This option is not supported in the RHEV KVM Connector.

Specify Other OS field

Enter an OS that is not available in the Specify OS drop-down list.

Note 

This option is not supported in the RHEV KVM Connector.

Specify Applications check boxes

Check the appropriate boxes to specify applications that are installed on the VM during provisioning.

Note 

This option is not supported in the RHEV KVM Connector.

Specify Other Applications field

Enter other applications that are not available from the Specify Applications check boxes.

Note 

This option is not supported in the RHEV KVM Connector.

Application Code field

Enter an application code that is used in the VM name.

The application code can be between 1 to 4 characters (for example: W2K3, DB, WS). The application code can be used in a system policy for the VM name by using the variable ${APPCODE}.

For example, if the VM Name Template is vm-${GROUP_NAME}-${APPCODE}, the VM provisioned with the system policy has the name vm-groupname-W2K3.

Note 

This option is not supported in the RHEV KVM Connector.

Step 8

Click Next.

Step 9

On the Add Catalog: User credentials screen, complete the required fields, including the following:

Note 

These options are not supported in the RHEV KVM Connector.

Name

Description

Credential Options drop-down list

Choose to allow or disallow users to retrieve VM access credentials (shared). The following options are available:

  • Do not share

  • Share after password reset

  • Share template credentials

The Do not share option is chosen if the administrator wants to send the credentials privately to another user outside Cisco UCS Director.

User ID field

Enter the user ID.

Note 

This field is available only if a choice is made to share under Credential Options.

Password field

Enter the password.

Note 

This field is available only if a choice is made to share under Credential Options.

Step 10

Click Next.

Step 11

On the Add Catalog: Customization screen, complete the required fields, including the following:

Name

Description

Automatic Guest Customization Enable check box

Check the box to enable automatic guest customization.

If you do not check this check box, then Cisco UCS Director does not configure the DNS, Network, and Guest OS properties.

Pre Provisioning Custom Actions Enable Check the Enable check box to enable execution of an orchestration workflow before VM provisioning.

Workflow field

Click Select to check the compound workflow that should be used in the orchestration workflow before VM provisioning.

Check the check boxes of the required workflows, and click Select to return to the Add Catalog screen.

Note 

This field appears when Pre Provisioning Custom Actions Enable is checked.

Post Provisioning Custom Actions Enable check box

Check the box to enable execution of an orchestration workflow after VM provisioning.

Workflow drop-down list

Click Select to check the check boxes of the workflows that need to be used in the orchestration workflow after VM provisioning.

Check the check boxes of the required workflows, and click Select to return to the Add Catalog screen.

Note 

This field appears when Post Provisioning Custom Actions Enable is checked.

Virtual Storage Catalog Enable check box

Check the box to choose storage entries from the Virtual Storage catalog.

Virtual Storage Catalog drop-down list

Chose a storage entry from the catalog.

Note 

This field appears when Virtual Storage Catalog Enable is checked.

Cost Computation

Charge Duration drop-down list

Choose Hourly or Monthly.

Active VM Application Cost USD field

Enter the cost for the application that is included in the template.
Note 

This option is not supported in the RHEV KVM Connector.

Inactive VM Application Cost USD field

Enter the cost to this catalog of a VM in inactive state, per hour or month.
Note 

This option is not supported in the RHEV KVM Connector.

VM Life Cycle Configuration

Lease Time check box

Check the box to define a lease time (in days and hours).

Days field

Enter the number of days.

Note 

This field appears when Lease Time is checked.

Hours field

Enter the number of hours.

Note 

This field appears when Lease Time is checked.

Hide end user lease configuration check box

Check the box to prevent service users from configuring a lease time for VMs.

Hide end user VM provision later check box

Check the box to prevent service users from provisioning VMs at a later time.

Step 12

Click Next.

Step 13

On the Add Catalog: VM Access screen, complete the required fields, including the following:

Name

Description

Web Access Configuration Enable check box

Check the box to enable web access to the VM. By default, this check box is unchecked which means that web access to the VM is disabled.

URL field

Enter the URL of the VM.

Note 

This field appears when Web Access Configuration Enable is checked.

Label field

Enter the label that is defined for this URL.

Note 

This field appears when Web Access Configuration Enable is checked.

Remote Desktop Access Configuration Enable check box

Check the box to enable remote desktop access to the VM. By default, this check box is unchecked, which means that remote desktop access to the VM is disabled.

Server field

Enter the IP address of the server for remote access.

Note 

This field appears when Remote Desktop Access Configuration Enable is checked.

Port field

Enter the port number on the server for remote access.

Note 

This field appears when Remote Desktop Access Configuration Enable is checked.

Label field

Enter the label that is defined for this remote access.

Note 

This field appears when Remote Desktop Access Configuration Enable is checked.

VMRC Console Configuration Enable check box

Check the box to enable VMRC console access to the VM. By default, this check box is unchecked, which means that the VMRC console access to the VM is disabled.

Step 14

Click Next.

Step 15

Review the catalog information on the Add Catalog: Summary screen.

Step 16

Click Submit.

Service Requests

You can use the self-service provisioning feature to create a service request to provision virtual machines (VMs), services, or applications. The service request process produces a provisioning workflow for VM creation that includes the following actions:

  • Budget validation

  • Dynamic resource allocation

  • Approvals

  • Provisioning

  • Lifecycle setup and notification


Note

If you change the number of CPU Cores or memory allocation while in the Deployment Configuration screen, the total cost is automatically updated and displayed.

To provision a VM or execute an orchestration workflow, you must first create a service request. If desired, you can require approval from one or two administrators or designated users before the VM is provisioned or the workflow executed. VMs can be immediately approved or scheduled to be approved within a maximum of 90 days from the original request.

Creating a Service Request for a Standard Catalog

The administrator publishes catalogs to a group and an end user can choose the required catalog to create a service request. The administrator provides the Self-Service portal with orchestration workflows in the form of catalogs. A catalog, published by the administrator, can be a standard catalog, advanced, or service container.


Important

You can complete this procedure only if the administrator has enabled the Create Service Request permission for your role. This Create Service Request permission enables or disables the Create Request option in the Service Requests tab. It does not have any impact on the Create Request option from the Catalog menu option.

Procedure

Step 1

Choose Organizations > Service Requests.

Step 2

On the Service Requests page, click Service Requests.

Step 3

Click Create Request.

Step 4

On the Create Request screen, choose Standard as the catalog type.

Step 5

Click Submit.

Step 6

On the Create Service Request screen, complete the following fields:

Name

Description

Catalog Selection

VM Ownership

Choose one of the following radio button:

  • Group—Select this radio button to choose the group for which a VM is provisioned. On selecting this radio button, expand Select Group, check the group for which the VM has to be provisioned, and then click Validate.

  • User—Select this radio button to choose the users to whom you want a VM is provisioned. On selecting this radio button, expand User, check the user for whom the VM has to be provisioned, and then click Validate.

Catalog Type drop-down list

Displays the catalog type.

Select Catalog drop-down list

Choose the catalog created for the KVM cloud. The chosen catalog is used for VM provisioning
Step 7

Click Next.

Step 8

On the Deployment Configuration screen, complete the following fields:

Name

Description

Select VDC drop-down list

The VDC on which the VM is provisioned.

VDCs are defined by the administrator.

Comment field

Any comments relating to the deployment configuration.

Provision drop-down list

Choose either Now or Later.

When you choose Now, the VM is provisioned immediately or up to 90 days in the future. When you choose Later, a calendar for choosing the date and a drop-down list for choosing the time appear.

Important 

This check box is visible only if the administrator has unchecked the Hide end user VM provision later check box.

Lease Time check box

Check this check box to configure a lease time for the VM.

The lifetime of the VM can be assigned in terms of days and hours (automatically). The VM is terminated after the specified number of days and hours have elapsed.

Important 

This field is editable only if the administrator has not specified a lease time in the catalog used for VM provisioning and has unchecked the Hide end user lease configuration check box.

Days field

The number of days after which the VM is terminated.

Note 

This option appears when the Lease Time check box is checked.

Hours field

Choose the number of hours after which the VM is terminated.

Note 

This option appears when the Lease Time check box is checked.

Charge Duration drop-down list

Choose a charge duration from the drop-down list. It can be Monthly, Daily, or Hourly.

Month field

If you selected Monthly as the charge duration, then specify the number of months the default cost must be calculated for.

Hourly field

If you selected Hourly as the charge duration, then specify the number of hours the default cost must be calculated for.

Daily field

If you selected Daily as the charge duration, then specify the number of days to be included in the cost computation.

Step 9

Click Next.

Step 10

On the KVM Custom Specification screen, complete the following fields.

Name Description

CPU Cores field

The number of CPUs being utilized for the VM being provisioned. This list is available only if you configured the resizing option in the computing policy.

Memory field

The amount of memory for the VM being provisioned. This list is available only if you have configured the resizing option in the computing policy.

Disks field

The datastore for the VM being provisioned. The list of datastores available for selection depends upon the conditions established in the storage policy. You can enable or disable this option in the storage policy.

Storage Tier field

The storage entry for the VM being provisioned. This list appears only if the Virtual Storage Catalog is enabled for the selected catalog.

Select Datastore drop-down list

Choose a datastore. Click Submit to confirm your selection. For templates with multiple disks, you must repeat the datastore selection process for each disk.

Note 

You can select only one datastore for each disk category (System, Data, Database, Swap, and Log). The list of datastore items depends upon the scope conditions in the storage policy.

Step 11

Click Next.

Step 12

On the Custom Workflow Inputs screen, complete the following fields:

Note 

The custom workflow inputs are applicable, if the catalog selected for VM provisioning has Post Provisioning Custom Actions selected during catalog creation. In this scenario, the post provisioning workflow allows end users to specify custom inputs. The inputs option depends upon the workflow attached to a catalog.

Name Description

MAC Address field

The MAC address of the server.

IP Address field

The IP address of the server.

Host Name field

The hostname of the server.

Step 13

Click Next.

Step 14

The Summary screen appears. Review the information for accuracy.

Step 15

Click Submit.

What to do next

View the service request status.