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 | On the menu bar, choose Policies > Virtual/Hypervisor Policies > Computing. | ||||||||||||||||||||||||||||||||||||
Step 2 | Choose the RHEV KVM Computing Policy tab. | ||||||||||||||||||||||||||||||||||||
Step 3 | Click Add (+). | ||||||||||||||||||||||||||||||||||||
Step 4 | In the
Add
Computing Policy dialog box, complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 5 | Click Add. |
Step 1 | On the menu bar, choose Policies > Virtual/Hypervisor Policies > Storage. | ||||||||||||||||||||
Step 2 | Choose the RHEV KVM Storage Policy tab. | ||||||||||||||||||||
Step 3 | Click Add (+). | ||||||||||||||||||||
Step 4 | In the
Add
Policy dialog box, complete the following fields:
| ||||||||||||||||||||
Step 5 | Click Submit. |
Step 1 | On the menu bar, choose Policies > Virtual/Hypervisor Policies > Network. | ||||||||||||||||||
Step 2 | Choose the RHEV KVM Networking Policy tab. | ||||||||||||||||||
Step 3 | Click Add (+). | ||||||||||||||||||
Step 4 | In the
Network
Policy Information dialog box, complete the following fields:
| ||||||||||||||||||
Step 5 | Click Next. | ||||||||||||||||||
Step 6 | Click Add (+) in the Additional Networks section. The Add Entry to Additional Networks dialog box displays. | ||||||||||||||||||
Step 7 | In the
Add Entry
to Additional Networks dialog box, complete the following fields:
| ||||||||||||||||||
Step 8 | Click Submit. |
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 | On the menu bar, choose Policies > Virtual/Hypervisor Policies > Virtual Data Centers. | ||||||||||||||||||||||||||||||||||||||
Step 2 | Choose the vDC tab. | ||||||||||||||||||||||||||||||||||||||
Step 3 | Click
Add
(+). In the
VDC
Add dialog box, complete the following field:
| ||||||||||||||||||||||||||||||||||||||
Step 4 | Click Submit. | ||||||||||||||||||||||||||||||||||||||
Step 5 | In the
Add
vDC dialog box, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||
Step 6 | Click Add. |
Step 1 | On the menu bar, choose Policies > Virtual/Hypervisor Policies > Service Delivery. | ||||||||||||
Step 2 | Click the KVM Deployment Policy tab. | ||||||||||||
Step 3 | Click Add. | ||||||||||||
Step 4 | In the
Add
Policy dialog box, complete the following fields:
| ||||||||||||
Step 5 | Click Submit. |
You can self-provision virtual machines (VMs) using predefined catalog items. A system administrator or an end-user 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, the catalogs will be displayed in a tile view format.
Note | Place the Catalogs option on the menu bar to easily access all the catalog-related options. Click your user name on the top right corner of the interface, choose the Catalogs tab in the User Information dialog box, and check the Enable Catalogs check box. |
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||||||||||||||||||||
Step 2 | Choose the Catalog tab. | ||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Add (+). | ||||||||||||||||||||||||||||||||||||||||||
Step 4 | In the Catalog Add dialog box, select the type of catalog that you want to add. | ||||||||||||||||||||||||||||||||||||||||||
Step 5 | Click Submit. | ||||||||||||||||||||||||||||||||||||||||||
Step 6 | In the
Create
Catalog dialog box, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||
Step 7 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||
Step 8 | In the
Applications Details pane, complete the following
fields:
| ||||||||||||||||||||||||||||||||||||||||||
Step 9 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||
Step 10 | In the
User
Credentials pane, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||
Step 11 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||
Step 12 | In the
Customization pane, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||
Step 13 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||
Step 14 | In the
VM
Access pane, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||
Step 15 | Click Next. | ||||||||||||||||||||||||||||||||||||||||||
Step 16 | Review the catalog information in the Summary page. | ||||||||||||||||||||||||||||||||||||||||||
Step 17 | 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 pane, 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 that is accessible only from the Services menu option. It does not have any impact on the Create Request option from the Catalog menu option.
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||||||||||
Step 2 | Click the Service Requests tab. | ||||||||||||||||||||||||||||||||
Step 3 | Click Create Request. | ||||||||||||||||||||||||||||||||
Step 4 | In the
Create Service Request dialog box, complete the
following field:
| ||||||||||||||||||||||||||||||||
Step 5 | Click Submit. | ||||||||||||||||||||||||||||||||
Step 6 | In the
Catalog
Selection pane, complete the following fields:
| ||||||||||||||||||||||||||||||||
Step 7 | Click Next. The Deployment Configuration screen appears. | ||||||||||||||||||||||||||||||||
Step 8 | In the
Deployment Specification
screen, complete the following fields:
| ||||||||||||||||||||||||||||||||
Step 9 | Click
Next.
In the Custom Specification screen, complete the following fields.
| ||||||||||||||||||||||||||||||||
Step 10 | Click
Next.
The Custom Workflow Inputs screen appears. 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. Complete the following fields:
| ||||||||||||||||||||||||||||||||
Step 11 | Click Next. | ||||||||||||||||||||||||||||||||
Step 12 | If you checked
the
Perform deployment assessment check box, then review
the report of the assessment displayed in the
Deployment Assessment pane.
If this assessment report identifies errors, then you must return to the previous panes and rectify the errors before submitting the request. If the assessment report shows no errors, then you can proceed to the next pane. | ||||||||||||||||||||||||||||||||
Step 13 | Click
Next.
The Summary screen appears. Review the information for accuracy. | ||||||||||||||||||||||||||||||||
Step 14 | Click
Submit.
The Submit Result dialog box confirms that the service request was submitted successfully. |
View the service request status.