vCloud Director

vCloud Director

- January 03, 2016

Components of vCloud Director :
Key Terms you should know :

Cell – The individual vCloud Director Servers that make up a logical vCloud Director instance or cluster
vCNS – vCloud Network and Security (formerly vShield)
vCD – vCloud Director
vDC – Virtual Data Center
PvDC – Provider Virtual Data Center
OvDC – Organization Virtual Data Center

Planning and Design:

Object Identities

–2 IP Addresses

•One for the HTTP service
•One for the console proxy service

–DNS A records
–VM Logical names

Requirements

–vCloud Director 5.1.1 installation bin file
–Red Hat Enterprise Linux (RHEL) 5 or 6

–libXdmcp rpm package

•http://ITtra.in/libXdmcp
–Compatible SQL or Oracle Database

•http://ITtra.in/SQLOracleDB

SQL Database Installation

Installation Guide Scripts

–Create the database instance
–Set transaction isolation level
–Create database user account
–Assign permissions to the database user account
–Use SQL “Mixed Mode” authentication

Create SSL Certificates

Keytool Command
Create Two SSL Certificates

–keytool -keystore certificates.ks -storetype JCEKS -storepass passwd -validity 9999 -genkey -keyalg RSA -alias http
–keytool -keystore certificates.ks -storetype JCEKS -storepass passwd -validity 9999 -genkey -keyalg RSA -alias consoleproxy
–Use chmod to grant read access universally

vCloud Organizations :

The Logical Consumer Object of vCloud

–Unique Organization URL
–Catalogs for vApps
–Email Configuration
–Policies: vApp Leases, Templates, Quotas, Limits, and Passwords

LDAP Integration

–“None” for Local Users
–vCD System LDAP for Internal Users
–Custom LDAP for 3rd Party Directory Services

Organization Roles

–Org Admin
–Catalog Author
–vApp Author
–vApp User
–Console Access

Create an Organization

Create Two Organizations

–One for Public Catalogs for Global Access
–One for the Development Team

Reasons for Choosing Development

–Start with the easy workloads first
–Learning process for everyone
–Adhere to the true development cycle:

Development > Test > Quality Control > Stage > Production

Organizational vDCs

Virtual Data Centers

–Live on top of the Provider vDC (PvDC)
–Further logical definition of existing compute and storage resource pools
–Multiple OvDCs can live on top of the same PvDC

Allocation Models

–Defines the quality of service and cost of vCloud resources
Allocation Pool

Based on Percentages of Guarantee

–CPU Allocation in GHz
–CPU Resources Guaranteed %
–vCPU Speed in GHz
–Memory Allocation in GB
–Memory Resources Guaranteed %
–Maximum number of VMs: Set Value or Unlimited

•Uses a vSphere Resource Pool to Enforce

–Dynamic allocation of reservations
–CPU Resources Guaranteed * vCPUs allocated * vCPU Speed = Resource Pool Reservation
•Example: 50% * 2 GHz * 100 vCPUs = 100 GHz Reserved
–When Reservation reaches Allocation, limit is imposed

Pay as You Go

Granular Resources Based on vApps

–Resources committed only when a vApp is deployed
–CPU Quota: GHz value or Unlimited
–CPU Resources Guaranteed %
–vCPU Speed in GHz
–Memory Quote: GB value or Unlimited
–Memory Resources Guaranteed %
–Maximum number of VMs: Set Value or Unlimited

Notable Information

–vCloud Director 5.1 introduced ability to do CPU and Memory quota
–Common business jargon = “Pay by the drink”

Reservation Pool

•Full Reservation of Resources

–Simplest model to deploy
–CPU Allocation in GHz
–Memory Allocation in GB
–Maximum number of VMs: Set Value or Unlimited

Costly Method

–Resources are reserved regardless of use
–Cannot go back and overcommit your PvDC

Storage Profiles

Allocated Storage

–Use Storage Profiles to identify back end storage layouts
–Storage Profiles are created in the vCenter that owns the vCloud Resource Cluster(s)

Networking

Network Pool

–Choice ultimately determines the amount of available networks
–Drives the quota that can be configured

Edge Gateway

–Provides network services: DHCP, Gateway, DNS, Firewall, 88888
–Use High Availability for critical workloads
–Avoid Advanced Options unless needed – simple is often best

Org vDC Network

–A common network pool for vApp to vApp communication
–Can be utilized by other Org vDCs if desired

Comments