vCloud Automation Center 6.0’s “XaaS” feature will allow our customers to utilize any prepackaged, new, or existing vCenter Orchestrator workflow and deliver it as a Self-Serviced, Entitled, Governed, and Lifecycle-managed service. VMware will be shipping a more integrated View/vCAC DaaS integration in Q1’2014. Until then we have to improvise to come up with a “DaaS-like” solution that will help fill in the gap until the products are natively integrated.
vCAC’s Advanced Service Designer (ASD) provides a quick-fix for this needed capability using rather unsophisticated means. This use case guide will walk you on building a Desktop Request service using the ASD and vCenter Orchestrator’s Active Directory Plug-in.
DaaS Use Case Objectives:
- Allow cloud users to request a Horizon View Desktop machine from vCAC’s Service Catalog and add Self-Service, Governance, and Entitlement to existing View Environments
- Use vCAC’s Advanced Service Designer to create a Custom Service to deliver DaaS
- Configure a Governance (Approval) policy for VDI Desktop Requests
- Utilize vCO’s built-in Active Directory plug-in and a simple workflow to do the magic
DaaS Solution Summary:
- Horizon View is configured with 2 Desktop Pools:
- Floating Desktop Pool: DaaS-Engineering
- Dedicated Desktop Pool: DaaS-Operations
- DaaS-Engineering -> “DaaS-Eng”
- DaaS-Development-> “DaaS-Ops”
assumes you have good working knowledge of vCloud Automation Center 6.0
and Horizon View 5.x, as well as familiarity with vCAC’s UI and