The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Installation of Red Hat Enterprise Virtual Machine (VM) and Hypervisor.
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. |
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||
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:
| ||||||||||||||||||||||||||||||||||||||
Step 6 | Click Add. |
Step 1 | Choose . | ||||||||||||||||||||
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:
| ||||||||||||||||||||
Step 5 | Click Submit. |
Step 1 | Choose . | ||||||||||||||||||
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:
| ||||||||||||||||||
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:
| ||||||||||||||||||
Step 8 | Click Submit to add the network. | ||||||||||||||||||
Step 9 | Click Submit to add the policy. |
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.
In this task, you specify deployment, storage, network, and computing policies. Refer to the Cisco UCS Director System Administration Guide for additional information.
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||
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:
|
Step 1 | Choose . | ||||||||||||
Step 2 | On the Service Delivery page, click RHEV KVM Deployment Policy. | ||||||||||||
Step 3 | Click Add. | ||||||||||||
Step 4 | On the Add Policy screen, complete the following fields:
| ||||||||||||
Step 5 | Click Submit. |
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.
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.
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.
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click Submit. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | On the
Add
Catalog: Basic Information screen, complete the required fields,
including the following:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | On the
Add
Catalog: Application Details screen, complete the required fields,
including the following:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 8 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 9 | On the
Add
Catalog: User credentials screen, complete the required fields,
including the following:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 10 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 11 | On the
Add
Catalog: Customization screen, complete the required fields,
including the following:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 12 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 13 | On the
Add
Catalog: VM Access screen, complete the required fields, including
the following:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 14 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 15 | Review the catalog information on the Add Catalog: Summary screen. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 16 | Click Submit. |
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.
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.
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.
Step 1 | Choose . | ||||||||||||||||||||||||||
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:
| ||||||||||||||||||||||||||
Step 7 | Click Next. | ||||||||||||||||||||||||||
Step 8 | On the Deployment Configuration screen, complete the following fields:
| ||||||||||||||||||||||||||
Step 9 | Click Next. | ||||||||||||||||||||||||||
Step 10 | On the KVM Custom Specification screen, complete the following fields.
| ||||||||||||||||||||||||||
Step 11 | Click Next. | ||||||||||||||||||||||||||
Step 12 | On the Custom Workflow Inputs screen, complete the following fields:
| ||||||||||||||||||||||||||
Step 13 | Click Next. | ||||||||||||||||||||||||||
Step 14 | The Summary screen appears. Review the information for accuracy. | ||||||||||||||||||||||||||
Step 15 | Click Submit. |
View the service request status.