© 2009 VMware Inc. All rights reserved

VMware vCloud and vCloud Director

Technical Presentation Overview for vCloud Director

2

Why Not Just Virtualization?

Challenges in a Virtualized Environment

• Multi-tenancy support – how to securely segment resources by user organization

• Controlling VM sprawl – pricing resources to shape user behavior

• Self-service provisioning – avoiding the IT provisioning bottleneck

• How do you accurately “charge” users for their resources to

discourage the notion that VMs are “free” resources?

• Can different organizations compete for the same resources?

• Can VMs from different organizations see each other?

Administrator

Users

• Can we have a defined catalog of VMs

for user self-provisioning while ensuring

some level of control?

3

Why Cloud Computing?

Extending vSphere with Cloud Computing Benefits

• Multi-tenancy support – control access and visibility to resources

• Self-service portal for user provisioning through catalogs

• Resource allocation models integrated with chargeback

• Economies of scale with elastic resources under your control

Catalog

Web Portal

Users

• Self-service portal for users

• Role-based security

• Catalogs of predefined VMs

• VMs assigned with allocation/cost model

and quotas

• Resources and access secured along organizational boundaries

• Add capacity seamlessly and reclaim unused resources via leases

• Chargeback reports aligned to resource allocation

models to shape user behavior

4

Cloud Computing

•

•

•

•

•

•

•

•

•

•

A new model enabling delivery of IT as a service

IT consumed as a service

5

Cloud Computing

Cloud Computing is an approach to computing that leverages the efficient pooling

of on-demand, self-managed virtual infrastructure, consumed as a service.

Pooling

From machines to highly

elastic resource pools, with on-

demand capacity

Zero-Touch Infrastructure

Policy-driven automation of

provisioning, deployment and

management

Self-Service

Easy access with policy-

based provisioning and

deployment

Control

Application-aware

infrastructure with built-in

availability, scalability, security

and performance guarantees

Open and Interoperable

Application mobility between

clouds, based on open

standards

Leverage Existing

Investments

Benefits of cloud computing to

existing applications and

datacenters

Efficiency thru Utilization

and Automation Agility with Control Freedom of Choice

6

Three Layers of Cloud Computing (delivering IT as a Service)

Infrastructure as a Service (IaaS)

Platform as a Service (PaaS)

Software as a Service (SaaS)

7

VMware vCloud

Private Cloud

• Built by and for the enterprise

Public Cloud

• Available to enterprises for

added or specific capacity

• vCloud Datacenter Services

program ensure compatibility

Enterprise Service Provider

Common cloud infrastructure and management platform

VMware vCloud

8

VMware vCloud Solution

vShield Edge

vCloud API

vCenter Chargeback

vCenter

Orchestrator

vCloud

Connector

vCloud

Director

vCloud Request Manager

VMware vSphere

VMware vStorage API

for Data Protection

Core components of a cloud infrastructure and

management solution

9

VMware vCloud Components

10

vCloud – Cloud Infrastructure and Management Components

Cloud Computing Capabilities Solution Components

Resource pooling

Resource abstraction

Secured multi-tenancy

Self-service

Resource and cost visibility

Hybrid management and mobility

Open and interoperable

Governance

Workflow automation and

orchestration

Backup and recovery

VMware vCloud Director

vCenter Chargeback

VMware vSphere

vShield Edge

vCloud Connector

vCloud Request Manager

vCloud API

vCenter Orchestrator

vStorage API for Data

Protection

11

vCloud Component: VMware vSphere

Objective

• Abstract hardware through virtualization

• Pool resources – DRS is a requirement for vCloud

Features

• Virtualized compute (CPU, memory), network, and storage resources

Physical

Resources Compute Network Storage

Port Groups or dvPort Groups Datastores

Resource Pools

Host Clusters

vSphere

Abstractions

“Virtualization First” Policy

All new workloads must be virtual

vCloud

Prerequisite

12

vCloud Component: VMware vCloud Director

Objective

• Abstract, organize and allocate vSphere resources for multi-tenancy

• Provide end users a self-service portal to request and access workloads

Features

• Provider

• Resource abstraction, allocation, and separation – virtual datacenters

• Organizations – security boundaries

• Resource leases and quotas

• API for cloud management and interoperability

• Consumer

• Cloud web portal for users

• Catalogs of vApps (workloads)

• Access control

• User clouds for running vApps

• VMware remote console

13

VMware vCloud Director

Abstraction of Resources

• Administrators (providers) allocate resources

• End users (consumers) only see what they need

Catalogs

vApps

vApp Networks

Network Connections

Network Specifications

Network Services

Organization vDCs

Provider vDCs

External Networks

Private Networking Options (Network Pools)

Organization Networks

Organizations

Users (Org Admin)

14

Secured Multi-Tenancy

VMware vCloud Director Organizations

• Each organization is a security/visibility boundary between tenants

• Contains users and virtual datacenter resources

• Users choose vApps from visible catalogs

vShield Edge

• Secures network

Organization A

vDC2 vDC1

Organization B

vDC3

vApp

Organization A’s Catalog

Master Catalog

15

Objective

• Provide network security within organizations for isolated network topologies

• Organization networks and vApp networks

Features

• vShield Edge appliances deployed by VMware vCloud Director on vSphere

• “Routed” networks have security services

• Firewall services

• NAT services

• DHCP

• Port forwarding

• IP masquerading

VMware vCloud Director

vCloud Component: vShield Edge

VMware vSphere vShield Edge

vApp Network

Organization Network

External Network

Organization Network

16

vCloud Component: vCenter Chargeback

Objective

• Accurately assign, measure, and analyze costs of workloads

• Allow consumer to understand and be accountable for usage

Features

• Hierarchical chargeback view of vCenter and vCloud Director objects

• Usage data collection aligned with resource allocation models

• Cost assignment

• Usage data warehouse

• Reporting

• Integrate with third-party billing

17

vCenter Chargeback

Components

• vCenter Chargeback Server

• Data Collectors

• vCloud data collector to collect billable events from VMware vCloud Director database

• vCenter data collector to collect usage data for vCenter Servers providing resources

• vShield data collector to collect usage data for networking

Database

• SQL Server 2005 and 2008

• Oracle 10g/11g Enterprise or Standard

Built-in load balancer

• Create new Chargeback servers to scale with the cloud

Licensed per VM

18

vCloud Components Architecture and Technical Requirements

19

vCloud Architecture

vCenter Server

ESX/ESXi Hosts

vCloud

Agent vCloud

Agent

vCloud

Agent

vCloud

Agent

vCloud

Agent vCloud

Agent

Datastores

VMware vSphere

vCenter Database

LDAP

vSphere Client

vCenter Chargeback Web Interface

vCenter ChargebackDatabase

vCenter Chargeback

vCenter Chargeback Server

VMware vCloud Director (vCD)

vCloud Director Cell

vCloud Director Database

vCloud Director Web Console

End Users

vCloud API

vShield vShield Manager and vShield Edge Virtual Appliances

Data Collectors

NFS Server

20

vCloud Architectural Best Practice

Separate Management from Raw Cloud Resources

Cloud Resource Groups Management Cluster

• vCloud management VMs

• vCenter Server VMs

• vCloud Director Cell VMs

• vCenter Chargeback Server VMs

• vShield Manager (VSM) virtual appliance

• vCenter Database VMs

• vCloud Director Database VM

• vCenter Chargeback Database VM

• Load balancer VMs for vCloud Director Cells

• vCenter Update Manager VMs

• VMware Management Assistant (vMA) VM

• vCloud Connector

• No user workloads

• vSphere resources managed by VMware vCloud Director

• Each resource group represents one or more provider vDCs

• Exclusively for cloud user workloads – no management VMs

(except vShield Edge virtual appliances deployed automatically)

21

VMware vCloud Director Installation and Licensing

Installs on RHEL 5 U4 or higher

64-bit machine

VMware vCloud Director supports

• VMware vSphere Editions

• VMware vSphere Enterprise*

• VMware vSphere Enterprise Plus

• VMware vCenter Server Editions

• VMware vCenter Server 4.0 Standard

• Minimum requirements

• vSphere and vCenter Server versions

4.0 U2 and 4.1.

VMware vCloud Director licensed by concurrent

powered-on VMs managed by vCD

vCenter Server VMware vCloud

Director

*vSphere Enterprise will not support VLAN backed Network Pools and VMware vCloud Director Network Isolation (vCD-NI) backed Network Pools

22

Oracle Database

Oracle 10g/11g Standard or Enterprise database

• Oracle Express is not supported

• Will work for small test/dev, POC type deployments

• See Express database memory and storage restrictions on Oracle website

Database can be run physical or in a virtual machine

Ensure that the database is backed up and replicated

• Consult with your favorite DBA

Sizing requirement guidelines

Database size VMs Users Orgs

173 MB 7943 4096 3854

343 MB 12793 4918 3951

443 MB 16443 11450 5022

23

VMware vShield Edge for VMware vCloud Director

VMware vShield Edge provides end point security

• Available for download with vSphere Enterprise and Enterprise Plus.

One vShield Manager required per vCenter Server

• Provides network edge security

• Provides firewall, NAT, port forwarding, IP masquerading and DHCP

functionality (enforces multi-tenancy)

• Edge appliances deployed and managed by VMware vCloud Director on

vSphere.

• Separate client not required.

• Does not require separate database

Licensing

• Free but requires license key during configuration

• Upgradable to vShield Edge 1.0 (full version which includes site-to-site VPN

and load balancer)

24

vCloud Director Scaling

VMware vCloud Director Cells

• Scale horizontally

• Add load balancer in front of Cells

• Multi-Cells share vCloud Director Database

vSphere Resources

• 1 vCD Cell : many vCenter Servers

• Multiple vCenter Servers attached to vCD can

be in linked mode (optional)

• All vCenter Servers should be in same site to

avoid potential latency

• Scale vSphere resources as needed

• Consider concurrent provisioning operation

limits in vCenter

• vSphere resource limits apply

vCloud Director Database Load Balancer

vCD Web Console

(points to single URL)

Resource Pools

Resource Pools

Resource Pools

Resource Pools

Resource Pools

Resource Pools

vCenter Server

vCenter Server

vCenter Server

vCenter Server

vCenter Server

vCenter Server

Cloud Resource Groups

vCD Cell

vCD Cell

vCD Cell

vCD “Cluster”

25

Questions