Cisco Virtual Application Container Services Self-Service Portal User Guide, Release 5.1STV1.0
Bias-Free Language
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.
- Updated:
- October 31, 2014
Chapter: Using Self-Service Provisioning
Using Self-Service Provisioning
This chapter contains the following sections.
- About Service Requests
- Service Request Workflows
- Creating a Service Request for Service Container Catalogs
- Viewing the Service Request Status
About 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
- Life cycles 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. Once an administrator or a relevant user approves the service request, the VM is provisioned. VMs can be immediately approved or scheduled to be approved within a maximum of 90 days from the original request.
Note | The service request approval process is optional. |
An administrator can provide an orchestration workflow as a catalog to a service portal. The approval process for a service request requires approval by one or two users. In such a scenario, an administrator and IT manager would have to approve the request before the VM can be provisioned.
Service Request Workflows
The service request workflow can be summarized into several stages:
- Initiation—Service request initiation.
- Resource Allocation—Resources required for VM provisioning.
- Approval—The group's virtual data center (vDC) defines the approval process for a service request. The service request approver is sent an email that describe the request. Once the approver approves the request, the VM is provisioned.
- Provision—The act of provisioning a VM.
- Setup Lifecycle Schedule— The scheduled and termination time.
- Notify—An email notice is sent to the user stating the VM is provisioned.
Creating a Service Request for Service Container Catalogs
The administator publishes catalogs to a group and end users choose the required catalog to create a service request. A catalog published by the administrator can be a standard catalog (VM creation), advanced catalog (orchestration workflow), service container (application container), or a VDI (Xen Desktop).
This type of service request requires that a service container catalog be available for selection.
What to Do Next
View your existing service requests.
Viewing the Service Request Status
| Step 1 | Choose . | ||||||||||||||||||||||||
| Step 2 | Choose a service request. | ||||||||||||||||||||||||
| Step 3 | Click
View Details.
|
Feedback