This document discusses integrating VMware's cloud orchestration and desktop virtualization products. It begins with an agenda for the presentation and then discusses the goal of using cloud and automation to enable organizations. It describes how integrating vCloud Automation Center (vCAC) and VMware Horizon View can provide workflow control, approval tracking, and self-service for end users and delegated administrators. The rest of the document covers prerequisites, configuring workflows in vCenter Orchestrator, lessons learned, and frequently asked questions about the integration.
VMworld Europe 2014: What’s New in End User Computing: Full Desktop Automation and Self-Service
2. Disclaimer
• This presentation may contain product features that are currently under development.
• This overview of new technology represents no commitment from VMware to deliver these
features in any generally available product.
• Features are subject to change, and must not be included in contracts, purchase orders, or
sales agreements of any kind.
• Technical feasibility and market demand will affect final delivery.
• Pricing and packaging for any new technologies or features discussed or presented have not
been determined.
CONFIDENTIAL 2
3. Agenda
1 What problem are we trying to solve
2 Integrating Cloud Orchestration and EUC
3 vCAC Blueprints
4 vCAC & View Automation
5 Lessons Learned
6 Q&A
CONFIDENTIAL 3
Paul O’Doherty http://virtualguru.org
Twitter @podoherty
Stephane Asselin http://myeuc.net
Twitter @VirtualStef
5. The Goal – Cloud and Automation Become Enablers for Your Organization
• Least amount of time on
business initiatives
• Manual processes and
business approvals
• Time consuming app/dev
requests
• Effort for upkeep of
operational tools
• Support/Training
• Higher portion of time on new
business initiatives
• Hybrid cloud automates
workflow and approvals
• Self service app/dev
• Silo's of skills
• Standardized and auto-mated
ops tools
6. • Service enabler
• Business approvals
• Workflow and
orchestration
• CAPEX based
• Simple
• Low Cost
• Scalable
• OPEX based
Virtualization
Public Cloud
Cloud Considerations
Virtualization is NOT cloud
• Deploying VM’s is the easy part
• Management and Data
Protection are the hard parts to
deploy
• IT and Business processes are
cumbersome and often manual
Takes time and experience
Ready to use BUT only in
the providers way not yours
~50-
80%
Harder Easier
7. • Service enabler
• Business approvals
• Workflow and
orchestration
• Extend workflow and
approvals
• Optimize Capex AND Opex
• Scalable and flexible
• Simple
• Low Cost
• Scalable
Hybrid Cloud Public
Clouds
Hybrid Enables the Best of Both Worlds
best of both worlds
included control
2 Public Cloud Types:
• Choose Enterprise for SLA
• Choose Public for PAYG
With Hybrid:
• Avoid silos of Private
• Control both sides
Private/Public
8. Scale
Flexibility&TimetoValue
Client Prem
PRIVATE/HYBRID
CLOUD
Traditional IT
CI Modules
vCloud
SLA1 SLA2
Mgmt
SLA3
Converged
Infrastructure
Hybrid (Federated) Cloud
ITaaS, Ent. Apps
VDI/Workspace,
IaaS/DBaaS/PaaS
Various Hosted
Clouds
Federated Cloud
ENTERPRISE AND PUBLIC
CLOUD
ENTERPRISE PUBLIC
CLOUD
WEB PUBLIC CLOUD
*
10. Why Combine vCAC & View
• What is DaaS
• What it provides and what it does not
• The benefits of combining Enterprise and Cloud Desktops
• The importance of Automation if controlling a highly distributed hosted environment
11. Multi-Vendor, Multi-Cloud Infrastructure
CloudPhysical Virtual
vSphere Hyper-V XenServer
Linux Windows
Cloud Providers
vCloud
Hybrid
Service
vCloud Automation Center
Self - Service
Infrastructure
Services
Application
Services
Custom
Services
vCloud Automation Center
Policy-Based Governance with Automated Delivery
12. Introducing Horizon 6
12
PERSONA
APP
OS
Central Image
Management for
Physical, Virtual and
BYO Devices
Unified
Workspace with
Blast Performance
Desktops &
Applications from
a Single Platform
Optimized for
the Software
Defined Datacenter
Hybrid
BrokeringClosed Loop
Management
and Automation
13. Finer Workflow Control and Approval Tracking
• Workflow and Approvals
• Ability to standardize across different Cloud
Providers
• User self enablement
• Better delegation
14. Integration Models
• vCAC & Direct Connect Desktop
– Involves vCAC
– VMware View Direct Connect
• vCAC & View Automation
– VMware Horizon 6
– vCenter Orchestrator
– vCloud Automation Center
– vCenter Server with vCenter Single Sign-On
15. vCAC with Desktop/Direct Connect View Desktops
• View Desktop is created as Blueprint
– View Desktop requires Direct Connect Installed (If PCoIP connectivity is required)
– Regular vCAC console can be used
– Possibility of Automating the application deployment with App Director
• Pros
– Easy to integrate Desktops
– Very little deviation from standard Blueprint Creation
• Cons
– Low level of automation
17. vCloud Automation Center Relationships
Business
Groups
B
A
C
USERS
A
C
B
A
Authentication &
Role-Based
Authorization
Authorized
Users
Resource
Reservations
Cost Profile
A
Tier 1
Public
Physical
Virtual
Shared Infrastructure
Public
Physical
Virtual
C
B
B
A
B
A
C
BA
A
Service
Blueprints
Cost Profile
Provision
Manage
Retire
Entitlements
Approvals
18. About Blueprints:
Blueprints contain the complete specification for the following:
1. A virtual, cloud or physical machine.
2. The ‘machine’s attributes’.
3. The manner in which the machine, policy, and management settings are provisioned.
To request a machine, a group member must select the blueprint from which
it will be provisioned.
19. Service
Catalog
A complete specification defining the CPUs, memory, and storage which is allocated to the machine
that is published to the service catalog.
Can be global to a tenant or local to a business group.
Blueprints
Entitled user
20. Creating a vSphere Blueprint: Blueprint Information
The Blueprint Information tab provides:
General information and configuration settings for the blueprint.
• Which includes: name, reservation policy, and cost.
23. High Level Architecture
End
Users
IT
Admin
IT
Admin
Horizon vCO
Pluggin
Install and Customize Workflows
View Management and Automation
Self-Service End Users
and Delegated Administrators
vCAC Service Catalog vSphere Web Client
1. Self-Service
2. Request & Approval
3. Multi-Tenancy
1. Run & Schedule Workflows
24. Uses for these models
• Development and Test
• Contractors or Temp Workforce
– Allows for the reclaim of desktop at the end of work cycle
• Enhancement to DR strategies
• Task workers needing additional horsepower for specific projects
• Power Users needing multiple desktops for specific projects
25. HvCO Workflows are the building blocks
• Installing the Plugin is simple
• Workflows are customized easily
• Incremental Plugin releases can update
functionality without relying on major
releases . . .
• Admins exercise full control over what is and
isn’t exposed
• Huge opportunity for PSO!!!!
– Complex workflows
– Importable, Exportable, Interchangeable
CONFIDENTIAL 25
26. Every EUC Customer Can Use This !
1. Available w vCenter and provides scheduling and tracking
2. Leverages vCenter SSO and simple config from vCenter ~ vCO
CONFIDENTIAL 26
30. Prerequisites
• VMware Horizon View 6
• vCenter Orchestrator version 5.5.1
• vCloud Automation Center version 6.0.1
• vCenter Server and vCenter Single Sign-On
– 5.5b and SSO 2.0 or higher
31. View Pod Alias is used in configuring workflows
When you add your View Pod you do so using an alias
This alias is used to reference the View Pod in configuring the workflows
When you configure the properties of the workflow and edit Properties the Data Binding is used to specify
constants
32. Delegate Administrator workflow is used to limit access
Log in to the Orchestrator client as an administrator.
Click the Workflows view in the Orchestrator client.
In the workflows hierarchical list, select Library > Horizon > Configuration > Add Delegate
Administrator Configuration
34. You should use an external vCO Appliance
• vCAC comes with vCO however it is not started by default
• You need to enable the service from the vCAC appliance
• You are better off using an external vCO Appliance
35. Ensure you specify proper context for vCO
1. You can specify the default orchestrator folder context on a per-tenant basis
2. You need to login as the original administrator to do so
3. It can be found under Administration, Tenants, Advanced Services and then Default Orchestration
Folder
4. Simply select the Actions and Edit and you can browse to any folder in the root of the tree
37. Additional thoughts on integration
• Ensure that vCO is configured to use SSO locally
• When specifying an external vCO from vCAC the configuration should use basic authentication
• Ensure you have created separate folders for single tenant environments or separate vCO
appliances for multi-tenant
38. FAQ’s
1. How do they implement the HvCO ?
HvCO will be a separate download alongside Horizon 6, customers go to vCO
and install plugin
2. How do the DA workflows use View Admin roles/privileges ?
They DON’T, the admin sets up credentials in vCO to use a trusted service
account
3. Do the workflows expose all the View 6 API’s ?
Not all of them – only certain ones will be available and supported, there could
be more available at release but they may not be supported
4. What are the exciting futures for HvCO ?
DaaS Integration (Desktone) Pool creation, Cost/ITBM, Reclamation
CONFIDENTIAL 38
39. More information
• Download the whitepaper and review the release notes
– https://www.vmware.com/support/horizon-view/doc/horizon-vco-plugin-10-release-notes.html
• Review the vCAC 6.X installation documentation
– https://www.vmware.com/support/pubs/vcac-pubs.html
• Review the VMware View 6 Evaluation guide
– http://www.vmware.com/resources/techresources/10269
3rd Party Resources
• Detailed vCAC implementation Guide
– http://www.virtualjad.com/2014/02/vcloud-automation-center-60-poc-and.html