Customer Handbook - Rackspace Private Cloud powered by

Customer Handbook - Rackspace Private Cloud powered by
docs.rackspace.com/api
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Customer Handbook: Rackspace Private Cloud powered by VMware
vCloud
v1.0 (2015-12-17)
©2015 Rackspace US, Inc.
Rackspace Private Cloud powered by VMware vCloud® (hereafter referred to as Dedicated vCloud) provides a single-tenant hosted
private cloud. It is designed with server, storage, and networking hardware from trusted vendors such as Dell®, EMC®, and Cisco®,
and it's proactively managed 24x7x365 by our VMware Certified Professionals. You get VMware's cloud management platform to
build upon, while maintaining control through the vCloud web portal and the vCloud API. The document is for informational purposes only and is provided “AS IS.”
RACKSPACE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THIS DOCUMENT AND RESERVES THE RIGHT TO MAKE CHANGES TO SPECIFICATIONS AND PRODUCT/SERVICES DESCRIPTION AT ANY TIME WITHOUT NOTICE. RACKSPACE SERVICES OFFERINGS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS MUST TAKE FULL RESPONSIBILITY FOR APPLICATION OF ANY SERVICES MENTIONED HEREIN. EXCEPT AS SET
FORTH IN RACKSPACE GENERAL TERMS AND CONDITIONS AND/OR CLOUD TERMS OF SERVICE, RACKSPACE ASSUMES NO LIABILITY
WHATSOEVER, AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO ITS SERVICES INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
Except as expressly provided in any written license agreement from Rackspace, the furnishing of this document does not give you any
license to patents, trademarks, copyrights, or other intellectual property.
Rackspace®, Rackspace logo and Fanatical Support® are registered service marks of Rackspace US, Inc. All other product names and
trademarks used in this document are for identification purposes only and are property of their respective owners.
ii
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Table of Contents
1. Preface ........................................................................................................................ 1
1.1. Support ............................................................................................................ 1
2. Getting started ........................................................................................................... 2
2.1. Product description .......................................................................................... 2
2.2. Understanding Dedicated VMware vCloud ........................................................ 2
2.3. Components, features and permissions ............................................................. 2
2.3.1. Dedicated VMware vCloud components ................................................. 2
2.3.2. Dedicated VMware vCloud customer features ........................................ 3
2.3.3. Dedicated VMware vCloud permissions list ............................................. 5
2.4. Rackspace support services ............................................................................... 7
2.4.1. Dedicated VMware vCloud services ........................................................ 7
2.4.2. Virtual machine types ............................................................................ 8
2.4.3. VM requirements ................................................................................... 9
2.4.4. vCloud automation events ................................................................... 11
2.5. Compatibility .................................................................................................. 12
2.6. Authentication methods ................................................................................. 13
2.6.1. Authentication settings ........................................................................ 14
3. Managing vCloud ...................................................................................................... 16
3.1. vCloud Director tabs ....................................................................................... 16
3.2. Accessing the environment ............................................................................. 16
3.3. Setting user preferences ................................................................................. 17
3.4. Managing and monitoring virtual data centers ................................................ 17
3.5. Managing vApp Leases ................................................................................... 17
4. Working with vCloud elements .................................................................................. 19
4.1. Working with catalogs .................................................................................... 19
4.2. Working with media files ................................................................................ 21
4.3. Working with vApps ....................................................................................... 22
4.4. Working with virtual machines ....................................................................... 23
4.4.1. Managing virtual machines .................................................................. 23
4.4.2. VM Console ......................................................................................... 25
4.4.3. Snapshots ............................................................................................ 25
4.4.4. Downloading a VM as a template ........................................................ 25
4.5. Working with vCloud networks ....................................................................... 26
4.5.1. External networks ................................................................................ 26
4.5.2. Organization networks ........................................................................ 27
4.5.3. vApp networks .................................................................................... 28
4.5.4. Network pools ..................................................................................... 29
4.5.5. Virtual machines IP management ......................................................... 30
4.6. Catalog templates .......................................................................................... 31
4.6.1. Monthly template patching .................................................................. 31
5. Additional VMware services ....................................................................................... 32
6. Billing ........................................................................................................................ 33
6.1. Billing methods for each Dedicated VMware vCloud component ...................... 33
6.2. Detailed usage report in MyRack .................................................................... 33
6.3. Usage collection ............................................................................................. 35
7. Licensing ................................................................................................................... 36
7.1. Windows VM OS licensing .............................................................................. 36
7.2. Red Hat VM OS licensing ................................................................................ 38
iii
RPC VMware vCloud Handbook
December 17, 2015
v1.0
8. FAQ ..........................................................................................................................
9. Spheres of support ....................................................................................................
9.1. Spheres of support for supported virtual machines ..........................................
9.2. Spheres of support for unsupported virtual machines ......................................
vCloud terms and definitions .........................................................................................
10. Additional resources ................................................................................................
iv
39
43
43
44
46
48
RPC VMware vCloud Handbook
December 17, 2015
v1.0
List of Figures
2.1.
4.1.
4.2.
4.3.
4.4.
Guest OS customization page .................................................................................
External networks ..................................................................................................
Organization networks ...........................................................................................
vApp Networks ......................................................................................................
Selecting a network ................................................................................................
v
11
26
28
29
30
RPC VMware vCloud Handbook
December 17, 2015
v1.0
List of Tables
2.1. vCloud feature responsibility .................................................................................... 3
2.2. vCloud permissions ................................................................................................... 5
2.3. Organization email settings .................................................................................... 14
2.4. Organization LDAP settings .................................................................................... 14
2.5. Organization federation settings ............................................................................ 15
4.1. Rackspace Catalog Templates ................................................................................. 31
6.1. Usage report table ................................................................................................. 34
9.1. Virtualization support ............................................................................................. 43
9.2. Hardware support .................................................................................................. 43
9.3. Operating system support ...................................................................................... 43
9.4. Monitoring support ................................................................................................ 43
9.5. Network support .................................................................................................... 44
9.6. Security support ..................................................................................................... 44
9.7. Virtualization support ............................................................................................. 44
9.8. Hardware support .................................................................................................. 44
9.9. Operating system support ...................................................................................... 45
9.10. Monitoring support .............................................................................................. 45
9.11. Network support .................................................................................................. 45
9.12. Security support .................................................................................................... 45
vi
RPC VMware vCloud Handbook
December 17, 2015
v1.0
1. Preface
Rackspace Private Cloud powered by VMware vCloud® provides a single-tenant hosted private cloud, designed with server, storage, and networking hardware from trusted vendors
such as Dell®, EMC®, and Cisco®, that's proactively managed 24x7x365 by our VMware
Certified Professionals. You get VMware's cloud management platform to build upon,
while maintaining control through the vCloud web portal and the vCloud API.
1.1. Support
Rackspace offers 365x24x7 support for Rackspace Private Cloud powered by VMware
vCloud.
You can also visit the Rackspace Managed Virtualization community forums. The forum is
open to all vCloud users and is moderated and maintained by Rackspace personnel:
https://community.rackspace.com/products/f/52
For more information, visit the following pages:
• Product page
• Resources
1
RPC VMware vCloud Handbook
December 17, 2015
v1.0
2. Getting started
This section provides the following information:
• An overview of the Dedicated VMware vCloud product
• Features and components
• Rackspace support
• vCloud compatibility with other Rackspace products
• Authentication methods
2.1. Product description
Dedicated VMware vCloud provides a single-tenant hosted private cloud designed with
server, storage, and networking hardware from vendors like Dell, EMC, and Cisco. Dedicated VMware vCloud is managed 24x7x365 by Rackspace VMware Certified Professionals.
Dedicated VMware vCloud provides a cloud management platform to build upon, while
maintaining control through the vCloud web portal and vCloud API-compatible orchestration tools.
2.2. Understanding Dedicated VMware vCloud
The Dedicated VMware vCloud service uses a software suite that creates an abstraction layer on top of VMware vCenter Servers. This software makes creating virtual machines (VMs)
for a variety of workloads easy. Rackspace configures the infrastructure, sets up virtual networks, and establishes storage policies. With the Rackspace catalog of vApp templates in
the vCloud web portal, you can create VMs for testing, development, or production.
Rackspace can help you set cloud policies that control how resources are used. Optionally,
you can segregate business units or groups of users into "organizations" within the hosted
private cloud. Users can provision resources in this application, where they have access to
vApps and the resources used by vApps, without involving IT.
2.3. Components, features and permissions
This section describes the components of Dedicated VMware vCloud, its features, and the
permissions available to each role.
2.3.1. Dedicated VMware vCloud components
The Dedicated VMware vCloud product comprises several VMware services and a backup
system to ensure the availability of those services. The VMware services operate on a management cluster with two hypervisors, which increases availability.
The following services are installed in a Dedicated VMware vCloud environment.
• vCenter Server
• vCloud Director Cell - Qty: 2
• Dedicated Virtual Machine Recovery Appliance
2
RPC VMware vCloud Handbook
•
•
•
•
December 17, 2015
v1.0
vShield Manager
Edge FW Appliance - Qty: 2
vRealize Operations (vROps) Virtual Appliance
VMware Update Manager
Note
Access to these VMware services is limited to the user interface or API for
vCloud, vCenter, and vROps. Rackspace manages and maintains servers running
the Dedicated VMware vCloud VMware services.
2.3.2. Dedicated VMware vCloud customer features
The following table provides a list and description of vCloud features and responsibilities related to vApps, VMs and catalogs.
Table 2.1. vCloud feature responsibility
Feature
Responsibility
Description
Creating one or more managed VMs as a
vApp
Customer
A customer can create vApps with Rackspace-managed VMs using templates provided by Rackspace.
Creating one or more unmanaged VMs as a Customer
vApp
vApps with unmanaged VMs are created using templates provided by Rackspace.
Creating one or more customer-provided
VMs as a vApp from a template
Customer
vApps with customer-provided VMs using templates
created by uploading OVA/OVF files to a customer
catalog.
Creating one or more customer-provided
VMs as a vApp from an ISO
Customer
vApps with blank VMs that have an OS installed by
connecting an ISO file from a customer catalog.
Power on/off and suspend/resume a VM or Customer
entire vApp
Stop, start and suspend a VM or vApp.
Modify a VM
Customer
Changing the resources of a VM, such as the CPU,
memory, disk, or name.
Deleting a VM
Customer
Deleting a VM.
Access to vCloud API
Customer
The RESTful vCloud API used to enable automation and integration of third-party tools (such as
VMware vRealize Automation) into Dedicated
VMware vCloud.
Uploading a customer-provided OVA as a
vApp
Customer
vApps created by uploading a OVA/OVF template
into Dedicated VMware vCloud.
Uploading a customer-provided OVA as a
template in a customer catalog
Customer
vApp templates created by uploading a OVA/OVF
template into a customer catalog.
Uploading a customer-provided ISO in a
customer catalog
Customer
ISO files stored in Dedicated VMware vCloud by uploading it into a customer catalog media store.
Read-only access to the vCenter Server via
the vSphere API
Customer
Viewing vCenter information with read-only permissions from the vSphere web or full client, or thirdparty software.
Accessing the vCloud Director user interface
Customer
Using the Dedicated VMware vCloud user interface
to operate vCloud.
Editing a template or media item in a Customer Catalog
Customer
Modifying the details of a template or media item in
a customer catalog.
Creating or deleting a Customer Catalog
Customer
A catalog can be created or deleted on the provisioned storage to contain uploaded templates or
ISO files.
Changing the Customer Catalog Owner
Customer
Reassigning the ownership of a catalog to a different vCloud user account.
3
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Feature
Responsibility
Description
Editing a Customer Catalog Properties
Customer
Editing the properties of a created catalog.
Publishing a Customer Catalog to another
Organization in the same vCloud
Customer
Choosing which vCloud organizations can access the
created catalog.
Sharing a Customer Catalog with other
Customer
users within the same vCloud Organization
Selecting users in the vCloud organization to use the
catalog.
Creating, modifying and deleting Org vCD
independent disks
Customer
Create, modify and delete independent disks.
Sharing a vApp with other users in the
vCloud Organization
Customer
Sharing access to a vApp with another user in their
vCloud Organization.
Snapshot a VM or vApp
Customer
Creating or reverting to snapshots of VMs or entire
vApps.
Removing a snapshot from a VM or vApp
Customer
Deleting snapshots of VMs or entire vApps.
Accessing the VM Console
Customer
Using the VM console to interact with a VM.
Ticket notification of completed VM
Rackspace
Notifying a customer that a VM is ready for use with
a ticket that includes access information.
Publishing a customer catalog for external
(VCSP) subscription
Rackspace
Publishing a customer catalog for use between two
Dedicated VMware vCloud environments.
Creating a customer catalog that is subscribed to an external (VCSP) catalog
Rackspace
Creating a customer catalog that is subscribed to an
external vCloud catalog.
Enabling a customer provided catalog item Rackspace
for download
Enabling customer-provided templates in a catalog
to be downloaded by the customer.
Enabling an unsupported VM catalog item
for download
Rackspace
Enabling Rackspace-provided unmanaged VM templates in a catalog to be downloaded by the customer.
Managing vCloud users
Rackspace
Managing the vCloud users and groups for a customer.
Managing vCloud external networks
Rackspace
Creating, modifying or deleting external networks
for a customer.
Editing organization email settings
Rackspace
Customizing the organization email settings as requested by a customer.
Editing organization LDAP settings
Rackspace
Customizing the organization LDAP settings as requested by a customer.
Editing organization policies settings - leases
Rackspace
Customizing the organization policies settings - leases as requested by a customer.
Editing organization policies settings - quotas
Rackspace
Customizing the organization policies settings - quotas as requested by a customer.
Editing organization policies settings - limits Rackspace
Customizing the organization policies settings - limits as requested by a customer.
Editing organization guest personalization
settings
Rackspace
Customizing the organization guest personalization
settings (Active Directory defaults) as requested by
a customer.
Editing organization federation settings
Rackspace
Customizing the organization federation settings
(SAML) as requested by a customer.
Manual migration of Rackspace-managed
Rackspace
VMs from Server Virtualization powered by
VMware® to Dedicated VMware vCloud
Migrating Rackspace-managed customer VMs from
the Server Virtualization offering to Dedicated
VMware vCloud. This is a manual process that requires down time for the VM.
Manual migration of unmanaged VMs from Rackspace
Dedicated VMware® vCenter Server(TM)
to Dedicated vCloud
Migrating unmanaged VMs from the Dedicated
vCenter product to Dedicate vCloud. After the migration, the VMs remain unmanaged by Rackspace.
This is a manual process that requires down time for
the VM.
4
RPC VMware vCloud Handbook
December 17, 2015
Feature
Responsibility
v1.0
Description
Manual migration of unmanaged VMs from Rackspace
Server Virtualization to Dedicated VMware
vCloud
Migration of unmanaged VMs from the Server
Virtualization product to Dedicate vCloud. After
the migration, the VMs remain unmanaged by
Rackspace. This is a manual process that requires
down time for the VM.
Manual clone process for customer-provided VMs
Rackspace
A copy or template of a customer-provided VM.
Manual clone process for unmanaged VMs
Rackspace
A copy or template of an unmanaged VM.
2.3.3. Dedicated VMware vCloud permissions list
This table lists the permissions and privileges available to different user roles in vCloud. As a
Dedicated VMware vCloud customer, you are granted the permissions listed as "Customer"
in the Responsibility column. The default vCloud roles are listed as a reference.
Table 2.2. vCloud permissions
Object
Privileges
Catalog
Add vApp
from My
Cloud
Catalog
Change owner
Catalog
VCSP publish
subscribe
Catalog
Enable a
vApp template or media item for
download
Catalog
Create or
delete a catalog
Catalog
Customer
role
Org Admin*
Catalog
author*
x
x
x
x
x
x
x
x
x
x
x
Edit properties
x
x
x
Catalog
Publish
x
x
x
Catalog
Sharing
x
x
x
Catalog
View private
and shared
catalogs
x
x
x
Catalog
View published catalogs
x
x
Catalog item Create or upload
x
x
x
Catalog item Edit
x
x
x
Catalog item View
x
x
x
x
x
Catalog item Checkout
(add to My
Cloud)
x
x
x
x
x
Catalog item Copy
x
x
vApp author* vApp user*
x
Catalog item Enable download
5
x
x
Console
only*
RPC VMware vCloud Handbook
Object
Privileges
Disk
December 17, 2015
v1.0
Customer
role
Org Admin*
Catalog
author*
Change owner
x
x
x
Disk
Create
x
x
x
x
Disk
Delete
x
x
x
x
Disk
Edit properties
x
x
x
x
Disk
View properties
x
x
x
x
General
Administrator
control
General
Administrator
view
General
Send notification
Group or us- View
er
x
x
x
x
x
x
Organization
Edit federation settings
x
Organization
Edit leases
policy
x
Organization
Edit password
policy
x
Organization
Edit properties
x
Organization
Edit quotas
policy
x
Organization
Edit SMTP settings
x
Organization
View
x
OrganizaEdit propertion network ties
x
x
OrganizaView
tion network
x
x
Organization VDC
View
x
x
Organization VDC
gateway
Configure services
x
Organization VDC
network
Edit properties
x
Organization VDC
network
View properties
Organization VDC
storage policy
Set default
vApp
Upload
vApp
Download
x
x
x
x
x
x
6
vApp author* vApp user*
Console
only*
RPC VMware vCloud Handbook
December 17, 2015
Customer
role
Org Admin*
x
x
v1.0
Object
Privileges
Catalog
author*
vApp author* vApp user*
vApp
Change owner
vApp
Copy
x
x
x
vApp
Create or reconfigure
x
x
x
x
vApp
Delete
x
x
x
x
x
vApp
Edit properties
x
x
x
x
x
vApp
Edit VM CPU
x
x
x
x
vApp
Edit VM hard
disk
x
x
x
x
vApp
Edit VM memory
x
x
x
x
vApp
Edit VM network
x
x
x
x
x
vApp
Edit VM properties
x
x
x
x
x
vApp
Manage VM
password settings
x
x
x
x
x
vApp
Power operations
x
x
x
x
x
vApp
Sharing
x
x
x
x
x
vApp
Snapshot operations
x
x
x
x
x
vApp
Use console
x
x
x
x
x
Console
only*
x
x
x
2.4. Rackspace support services
This section describes the following topics:
• Support and automation services for Dedicated VMware vCloud environments
• Supported VM types
• vCloud automation events
2.4.1. Dedicated VMware vCloud services
Rackspace provides some specific support and automation services for the Dedicated
VMware vCloud environment and the virtual machines that are built in it.
Infrastructure support
Rackspace offers Fanatical Support for the hardware infrastructure resources including Network, Server and
Storage components.
VMware virtualization services
Rackspace is one of VMware's largest global vCloud Air
Network partners, with elevated access to technical specialists for rapid resolution of unexpected software-related issues within the VMware stack.
7
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Rackspace's VMware Certified Professionals (VCPs) assist in the architecture, deployment and troubleshooting of the environment. Rackspace monitors and maintains the VMware software stack, including installing
and configuring the vCloud, vCenter and vROps servers,
backing up the VMware service VMs, and monitoring
the hypervisors. Rackspace supports the vCloud and
vCenter web UI, and APs.
Virtual machines
Rackspace patches and monitors guest operating systems, backs up VMs, and installs and patches antivirus
on VMs created from Rackspace Managed OS templates. Rackspace also provides support for Rackspace
unmanaged or customer-provided virtual machine containers and their performance within the cloud. See Section 2.4.2, “Virtual machine types” [8] and Section 2.4.3, “VM requirements” [9] for more information.
vCloud support automation
Certain activities in vCloud trigger Rackspace automation. This allows Rackspace to populate information
in the support systems for tracking, monitoring, and
supporting VMs created in vCloud. See Section 2.4.4,
“vCloud automation events” [11] for more information.
2.4.2. Virtual machine types
The following VM types can be included in vApps. See Section 2.4.3, “VM requirements” [9] for information about the features required for a vApp virtual machine.
Rackspace Managed
Rackspace managed VMs are created from templates in
the Rackspace Catalog designated as "Managed" and have
Rackspace support services including for the guest OS. Since
Rackspace supports the guest OS, we add services, user accounts, and OS modifications necessary for that managed service.
Rackspace Unmanaged
Rackspace Unmanaged VMs are created from templates in the
Rackspace Catalog designated as "Unmanaged" and do not
have Rackspace guest OS support services. Rackspace does not
support the guest OS; our support teams and automation services do not interact with the guest OS.
Customer provided
Customer-provided VMs are created from templates that you
upload to a catalog or you can directly upload virtual machines
to vCloud. Rackspace does not support the guest OS; our support teams and automation services do not interact with the
guest OS.
8
RPC VMware vCloud Handbook
December 17, 2015
v1.0
2.4.3. VM requirements
A new virtual machine must meet the following requirements:
Networking
Rackspace Managed VMs: These VMs should have at least
two NICs. Only one secondary NIC can be connected to a ServiceNet network. Connect all other NICs, including the primary NIC, to one of the ExNet networks.
Note
If you select a NIC to be the primary NIC, vCloud
Director pushes the gateway and DNS settings to
the network adapter of the Guest OS running in
this virtual machine. No DNS or gateway settings
are pushed to other NICs, since they are not the
primary NIC. vCD only pushes the IP address and
subnet to these other NICs.
All other VMs: These VMs should have one or more NICs
connected to the ExNet networks and cannot be connected to any ServiceNet networks. ServiceNet only supports
Rackspace-managed VMs.
IP allocation: Use the allocation type "Static - IP Pool". Using
DHCP is not supported. Rackspace does not recommend using "Static Manual", since an incorrect IP entry causes our automation to fail.
Warning
Since the firewall is configured to deny access by
default, add ACL rules to allow inbound access to
the new VM. Otherwise, our automation generates a ticket when the VM is initially powered on,
requesting that the network configuration be corrected before support automation can continue.
Rackspace automation assigns a public IP address
for every private IP address assigned to the VM
and creates NAT rules on the firewall to allow external communication. The firewall is configured
to deny access by default. To allow inbound access, add appropriate ACL rules.
Advanced vCloud networking: Rackspace does not support
the use of advanced networking features such as routed, isolated, or fenced vApp networks. All VM network connections
must be made directly to the Rackspace-provided external
networks.
9
RPC VMware vCloud Handbook
Virtual machine name
December 17, 2015
v1.0
Warning
Special characters in a VM name are automatically
removed by our automation, leaving only the remaining allowed characters. The name field is restricted to 128 characters.
Rackspace VM names are created in accordance with the following standards:
• The original VM name is stored as the device nickname in
the MyRackspace portal.
• A six digit number followed by a "-" (hyphen) is added to
the beginning of the VM name. This number is used by our
support team.
• The first eight characters of a Windows VM or the first 55
characters of a Linux VM computer name entered in vCloud
are used for the next portion of the VM name.
• A default domain name taken from email of the primary
contact name at your company is added to the name of
the VM.
• No special characters other than "-" (hyphen) and "." (period) are allowed in the VM container name. (See VMware
KB: VMware Knowledge Base). Special characters are automatically removed.
Computer Name
If guest customization is enabled, the Computer Name field
in vCloud is used to set the host name in the guest OS. The
name is subject to the following limitations:
• This field is restricted to 15 characters for Windows. For
non-Windows systems, it is restricted to 63 characters and
can contain dots.
• Alphanumeric characters and hyphens are allowed. The
name must not contain only digits.
For Managed VMs, only the support system 6 digit device
number and a "-" (hyphen) is prepended to the Computer
Name. This may truncate the original name to meet the character length limitations.
For example, if a new VM is created with the VM Name
App1VM and the Computer Name app1, the resulting name for the Rackspace Managed VM is 123456app1.domain.com for a Linux VM and 123456-app1 for a
Windows VM. The original App1VM VM name is listed as the
alias for 123456-app1.domain.com in the MyRackspace
portal.
10
RPC VMware vCloud Handbook
Passwords
December 17, 2015
v1.0
Warning
Do not change the default password settings on
the Guest OS Customization page.
All vCloud VMs use the administrator or root password set by
vCloud guest customization as displayed in the VM properties.
Figure 2.1. Guest OS customization page
2.4.4. vCloud automation events
The following vCloud events trigger Rackspace automation:
Building a new VM
Rackspace automation is triggered when a VM is initially
powered on. Dedicated VMware vCloud environments
interact with Rackspace back-end automation and support systems, putting limitations and requirements on
the type of VM that is built.
After a new virtual machine is powered on, a ticket is
produced to notify the user that an automation process started. Do not log in to, make modifications to, or
power cycle the VM until you receive a ticket indicating
that this process is complete. Only make modifications
to the VM if a ticket from Rackspace explicitly requests a
modification.
If Rackspace automation experiences any issues registering a new VM with our support systems or adding
the public IP or NAT assignments to the firewall, we are
immediately notified of the issue. If there are delays in
processing the new VM, Rackspace issues a notification
ticket.
For Rackspace-managed VMs, Rackspace automation
logs in to the VM to configure monitoring, patching,
11
RPC VMware vCloud Handbook
December 17, 2015
v1.0
and backup services in accordance with the Rackspace
support system. All accounts have default settings for
these services. To change settings, contact the support
team after the automation is complete.
Modifying a VM
Rackspace automation is triggered if VM attributes
change. This keeps Rackspace systems up to date with
the properties of the VM. Do not change the computer name for a Rackspace-managed VM. Also, the virtual machine name for any VM should not be changed,
since Rackspace tracks the virtual machine by name in
your environment. If the name is changed, Rackspace
automation rewrites the name to its former value. To
change either of these names, contact your account
team for assistance.
Changing the power state of a
VM
When a VM is powered on or off, suspended, or resumed after suspending, Rackspace adjusts the monitoring systems so that the user does not receive alerts for
a VM that is intentionally shut down. Our automation
also suspends usage for VMs that are powered off. Suspended VMs do not qualify for usage suspension.
Deleting a VM
If a VM is deleted, Rackspace automation removes references to that VM from Rackspace support systems and
makes the local IP assigned to the deleted VM available
for reuse. The Rackspace automation process does not
remove or alter any ACLs created for those IPs. Since a
new VM can receive the local or public IP of a deleted
VM, use the MyRackspace portal to remove all associated physical firewall ACLs associated with the deleted
VM.
2.5. Compatibility
Dedicated VMware vCloud is compatible with certain other Rackspace products. Contact
your Rackspace support specialist for detailed information.
Additional guest OS software
To install MS SQL Server, Sharepoint, Microsoft Exchange, MySQL, or other Rackspace-provided software in a Dedicated VMware vCloud VM, contact the
Rackspace account team.
Compatibility with third-party
products
Rackspace is working to certify third-party products for
use with Dedicated VMware vCloud such as vRealize
Automation (formerly vCloud Automation Center) and
vCloud Connector. Rackspace provides details about the
compatibility level and requirements as they become
available.
Determination of compatibility
when elevated permissions are
needed
In some cases, existing role permissions provided by
Rackspace do not allow a custom or third-party tool to
12
RPC VMware vCloud Handbook
December 17, 2015
v1.0
function. Contact the Rackspace account team to determine if role permission adjustments are possible.
2.6. Authentication methods
VMware vCloud Director uses different authentication mechanisms for subscriber authentication to the vCloud portal and API.
Internal vCloud accounts
When configuring a new organization, internal vCloud
accounts do not use any kind of LDAP service. Instead,
new users are configured by Rackspace directly in the
vCloud User Interface and these users are stored within
the vCloud database.
Some of the disadvantages of using internal vCloud authentication include:
• Groups are unavailable
• A minimum length of 6 characters
• No password complexity policies
• No password expiration policies
• No password history
• No authentication failure controls
• No integration with enterprise identity management
systems
vCloud System LDAP Service
Selecting vCloud System with LDAP Service allows the
organization to use the Rackspace-provided identity service. Rackspace creates and manages users and groups
for an organization. Multiple organizations can share
the same LDAP service.
Note
This is not a self-service identity solution.
Contact Rackspace support services for any
identity needs.
Custom LDAP Service
A custom LDAP service enables the organization to use
its own private LDAP service. Each organization gets a
completely separate and unique LDAP service. Organizations do not have to use the same service as the vCloud
system; Dedicated VMware vCloud can use a completely separate unique Active Directory forest with no network links to any other forest.
For each organization, a single LDAP service for that
organization must be configured as a custom LDAP
to authenticate to. To enable this functionality, the
vCloud Director cells must be able to connect to all
LDAP servers over TCP port 389 or port 636. Network
connectivity to each organization’s LDAP services must
13
RPC VMware vCloud Handbook
December 17, 2015
v1.0
be secured. Refer to the VMware vCloud Security Hardening Guide for more information about the connectivity options for subscriber access to LDAP services.
SAML Identity Provider
A SAML Identity Provider can be used to authenticate
users in an organization. SAML v2.0 meta data is required for the service to be configured. The meta data
must include the location of the single sign-on service,
the single logout service, and the X.509 certificate for
the service.
When using SAML Identity Providers and API access,
follow these instructions in the VMware Programming
Guide: Create a Login Session Using a SAML Identity
Provider.
2.6.1. Authentication settings
The following tables show specialized organization settings for email, LDAP and federation.
Note
Contact Rackspace to request these settings.
Table 2.3. Organization email settings
Setting
Type
Description
Use system default SMTP server
SMTP Server
Set organization SMTP server
SMTP Server
SMTP server name
SMTP Server
The DNS host name or IP address of
the SMTP mail server
SMTP server port
SMTP Server
The SMTP server port number
Requires Authentication
SMTP Server
(Optional) Select if the SMTP server requires a user name
User name
SMTP Server
The user name for the SMTP account
Password
SMTP Server
The password for the SMTP account
Use system default notification settings
Notification Settings
Set organization notification settings
Notification Settings
Sender's email address
Notification Settings
The email address that appears as
the sender for vCloud Director emails.
vCloud Director uses the sender's email
address to send runtime and storage
lease expiration alerts.
Email subject prefix
Notification Settings
The text to use as the subject prefix for
vCloud Director emails
Test destination
Notification Settings
(Optional) Enter a destination email
address and click Test SMTP settings to
test the SMTP settings.
Table 2.4. Organization LDAP settings
Setting
Type
Description
Do not use LDAP
LDAP Options
14
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Setting
Type
Description
VCD system LDAP service
LDAP Options
Distinguished name for OU
LDAP Options
Custom LDAP service
LDAP Options
If custom LDAP service is enabled, the
following settings are available.
Server
Connection
Port
Connection
Base distinguished name
Connection
SSL
Connection
SSL Certificate
Connection
Key Store Password
Connection
Authentication method
Connection
Use external Kerberos
Connection
Realm
Connection
User name
Connection
Password
Connection
Enable SSPI
SSPI
Service Principal Name
SSPI
KeyTab
SSPI
Object class
User Attributes
Unique identifier
User Attributes
User name
User Attributes
Display name
User Attributes
Given name
User Attributes
Surname
User Attributes
Email
User Attributes
Telephone
User Attributes
Group membership identifier
User Attributes
Group back link
User Attributes
Object class
Group Attributes
Unique identifier
Group Attributes
Name
Group Attributes
Membership
Group Attributes
Group membership identifier
Group Attributes
Group back link identifier
Group Attributes
Table 2.5. Organization federation settings
Setting
Type
Description
Use SAML Identity Provider
Identity Provider
15
RPC VMware vCloud Handbook
December 17, 2015
v1.0
3. Managing vCloud
This section describes the vCloud Director interface and the following tasks:
• Accessing the vCloud environment
• Setting user preferences
• Managing virtual data centers
• Resetting vApp leases
3.1. vCloud Director tabs
The vCloud Director interface contains the following tabs.
• The Home tab displays the running vApps in the environment and the number of days
until their Lease expires. On the right side of the page, a Tasks section gives quick access
to most tasks and to organization management links.
• The My Cloud tab displays the vApp and VMs. The tag also displays expired items and
logs. This tab enables creation of vApps from Catalog or OVF.
• The Catalogs tab displays the Catalogs, vApp Templates, and Media. The resources to
create new vApps and the Rackspace-provided catalogs of VM templates are also displayed. The Rackspace catalog is read-only, but any additional catalogs will be available
through the following sub-tabs:
• The Media & Other tab is where ISOs can be uploaded or accessed.
• The vApp Templates is where new Templates can be loaded. Modified or existing Templates can be copied and removed from the inventory.
• The Catalogs tab is where catalogs can be accessed and some properties can be
changed.
3.2. Accessing the environment
The vCloud environment is accessible via web browser. Rackspace provides the URL for the
vCloud Director web console.
Note
vCloud is only accessible over a VPN connection to Rackspace. This can be configured for site-to-site VPN and/or single user VPN connections. Rackspace provides VPN details.
1.
Navigate to the URL in the browser.
A login screen appears.
2.
Enter the login and password details and press Enter.
16
RPC VMware vCloud Handbook
December 17, 2015
v1.0
3.3. Setting user preferences
To set user preferences, click the Preferences link at the top right of the page to open the
Edit User Preferences menu.
You can set the following preferences:
• Default login page
• The length of time to send out Lease Alerts before the time of expiration
You can also change a password by selecting Change Password.
3.4. Managing and monitoring virtual data centers
To manage a virtual data center, navigate to the Home page and click Manage VDCs on
the top right of the page. Most of the settings here are grayed out and cannot be changed.
Please contact support if any of these settings need to be changed.
Procedure 3.1. Monitoring virtual data centers
Monitoring the available resources is important. The following procedure shows where to
audit vApps, Templates, Media, Storage Policies, and available Org VDC Networks.
1.
On the Home page, click Org Settings on the top right of the page.
2.
Under Cloud Resources, click Virtual Datacenters. All Virtual data centers (VDCs) and
their Allocation Model are displayed.
3.
Click on the Monitor tab to see the current resources used by the VDC. This tab is divided into columns for CPU, Memory, and Storage. You can review the following information:
• vApps and their running status
• Templates, Media, Storage Policies
• Org VDC Networks and their current IP Pool consumption
3.5. Managing vApp Leases
To reset the lease on a vApp, it is not necessary to wait for it to expire. A vApp can be reset
before it expires if the vApp is required for longer than expected. Expired leases can be renewed or deleted.
Procedure 3.2. Resetting a lease
1.
Click My Cloud.
2.
In the left pane, click vApps.
17
RPC VMware vCloud Handbook
December 17, 2015
v1.0
3.
Select a vApp, right-click, and select Properties.
4.
On the General tab, select the Reset leases check box, select a runtime and storage
lease, and clickOK.
Procedure 3.3. Resetting an expired lease
1.
Login to the console and click the My Cloud tab.
2.
On the left-hand menu click the Expired Items, Expired vApps, or Expired vApp Templates tab depending on the type of lease to reset.
3.
Locate the expired vApp for which you want to reset the lease. Right click on the vApp
and select Renew.
The restored vApp appears on the vApps page.
Procedure 3.4. Deleting an expired lease
1.
Login to the console and click the My Cloud tab.
2.
On the left-hand menu click the Expired Items, Expired vApps, or Expired vApp Templates tab depending on the type of lease to delete.
3.
Locate the expired vApp for which you want to delete the lease. Right click on the
vApp and select Delete.
The vApp is deleted from the list.
18
RPC VMware vCloud Handbook
December 17, 2015
v1.0
4. Working with vCloud elements
This section describes how to work with the following vCloud elements:
• Catalogs
• Media files
• vApps
• Virtual machines
• vCloud networks
• Catalog templates
4.1. Working with catalogs
Rackspace provides Dedicated VMware vCloud customers with a catalog of vApp templates
to use when creating vApps with various operating systems. The Rackspace Catalog is subscribed to a Content Subscription Endpoint using the VMware Content Subscription Protocol (VCSP). This catalog is hosted as a web service in a central location for each Rackspace
data center and synchronized with array-based replication. The vCloud Director Cells have
access to this using the back-end services network.
More information about vApp templates, including a full list of the current vApp templates
offered in the Rackspace Catalog can be found at Section 4.6, “Catalog templates” [31].
The Rackspace catalog is provided by default to vCloud customers. This section discusses
how to add and manage additional catalogs.
Procedure 4.1. Creating a customer catalog
1.
Sign in to the organization where the catalog will be created.
2.
Select the Catalogs tab.
3.
Click the green + sign to create a new catalog.
4.
Enter a name and description for the catalog.
5.
If items in the catalog need to be accessed by users other than the original creator of
the catalog, select the users or groups with which the catalog needs to be shared An
item can be shared to all users in an organization by selecting the Everyone in the Organization option.
6.
If the organzation has permission to publish a catalog, the Publishing the Catalog is
available. Publishing a catalog enables all organizations in the vCloud Director instance
to access it. The access is read-only; other organizations can deploy items from the catalog but cannot add or remove items from the catalog.
19
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Note
Sharing across organizations is prohibited. If other organizations require access
to a catalog, it must be published. After a catalog is published, all organizations
can read it.
Procedure 4.2. Accessing a Catalog
1.
Click Catalogs.
2.
In the left pane, select one of the following catalog options:
• My Organization's Catalogs
• Public Catalogs
3.
In the right pane, select a catalog, right-click, and select Open.
Procedure 4.3. Sharing a catalog
Shared catalogs are available to users in your organization. Users with the correct rights
and access level can use vApp templates and media from the shared catalog to create their
own vApps.
The actions a user can perform on a catalog and its contents depend on the the rights of
the user and their access to the catalog. Sharing a catalog with full control does not grant a
user rights that the user does not already have.
1.
Click Catalogs.
2.
Select My Organization's Catalogs.
3.
Right-click a catalog and select Share.
4.
Click Add Members.
5.
Select the users and groups to share with.
• Everyone in the organization Select this option to share the catalog with everyone.
• Specific users and groups Select this option, click specific users and groups, and click
Add.
6.
Select an access level and click OK.
7.
Click OK.
Procedure 4.4. Deleting a Catalog
When deleting a catalog, it must not contain any vApp templates or media files. These
items can be moved to a different catalog or deleted.
1.
Click Catalogs.
2.
Select My Organization's Catalogs.
20
RPC VMware vCloud Handbook
December 17, 2015
3.
Right-click on a catalog and select Delete.
4.
Click Yes to confirm the deletion.
v1.0
The empty catalog is deleted from your organization.
4.2. Working with media files
To populate a catalog, vApp templates or media files must be added. This section describes
how to upload ISO and OVF files to a catalog.
Note
Java Plug-in 1.6.0_10 or later must be installed to complete this process.
Procedure 4.5. Upload an ISO file
1.
Open a catalog.
2.
Select the Media tab and click Upload.
3.
Click Browse and navigate to the ISO file.
4.
Provide a name and description and click Upload.
Click Uploads and Downloads Transfer to watch the upload progress.
5.
When the file is uploaded, wait until it is imported in vCloud Director.
When the status is stopped, the ISO file is now added to the catalog and can be used
to provision new VMs.
Procedure 4.6. Upload an OVF file
1.
Open a catalog.
2.
Select the vApps Templates tab and click Upload.
3.
Click Browse and navigate to the OVF file.
4.
Provide a name and description. Click Upload.
Click Uploads and Downloads Transfer to watch the upload progress.
5.
When the file is uploaded, wait until it is imported in vCloud Director.
When the status is stopped, the OVF file is now added to the catalog and can be used
to provision new VMs.
Procedure 4.7. Delete media files
1.
Click Catalogs then My Organization's Catalogs.
2.
On the Media tab, right-click on a media file and select Delete.
3.
Click Yes to confirm deletion.
21
RPC VMware vCloud Handbook
December 17, 2015
v1.0
4.3. Working with vApps
vCloud uses vApps as containers for all VMs. A vApp may contain one or more VMs. Before
creating a VM, a vApp must be created first.
Note
Before building, modifying or deleting a virtual machine in vCloud, review the
Rackspace Managed service automation and support requirements listed in Section 2.4, “Rackspace support services” [7]
Procedure 4.8. Build a new empty vApp
1.
On the Home page, click Build New vApp.
2.
Enter a name and description for the vApp. Click Next.
3.
To proceed without creating a VM, Click Next on the Configure Resources page, the
Configure Virtual Machines page, and the Configure Networking page.
4.
Review the settings and click Finish to create the vApp.
An empty vApp is created. When the process is complete, the vApp can be populated
with VMs.
Procedure 4.9. Build a new vApp and add a VM
1.
On the Home page, click Build New vApp.
2.
Enter a name and description for the vApp. Click Next.
3.
Click New Virtual Machine to create a new VM.
4.
In the Configure Resources page, name the newly created VM.
5.
In the Configure Virtual Machines , page change the computer name if needed
6.
On the Configure Networking page, click Next.
7.
Review the settings and click Finish to create the vApp.
A vApp is created with a VM. When the process is complete, the vApp can be populated with more VMs.
Procedure 4.10. Build a new vApp from OVF
An OVF file can have one or more VMs inside of it.
1.
On the Home page, click Add vApp from OVF.
2.
Browse to the location of the vApp OVF on a local drive or via a URL. Click Next.
3.
Review details and click Next.
4.
In the Select Name and Location page, name the VM and choose the VDC.
5.
On Configure Resources choose the storage policy
22
RPC VMware vCloud Handbook
December 17, 2015
6.
On the Configure Networking page, name the Computer.
7.
Choose your Customized Hardware settings of CPU, Memory and Hard Disk size.
8.
Review the settings and click Finish to create the vApp.
v1.0
A vApp is created from the OVF file. When the process is complete, the vApp can be
populated with VMs.
Procedure 4.11. Restarting a vApp
1.
Right click on a vApp and click Power Off.
2.
Right click on the vApp and click Start.
Procedure 4.12. Suspending and resuming a vApp
1.
Right click on a vApp and click Suspend.
2.
Right click the vApp and click Start.
4.4. Working with virtual machines
vCloud Direct uses vApps as containers for all VMs. A vApp may contain one or more
VMs. To create a VM, a vApp must be created first. Refer to Section 4.3, “Working with
vApps” [22] for more information.
Currently, the following limitations apply:
• There is no copy function available. Rackspace recommends creating new VMs. However, if a copy is required, contact the Rackspace support team. Rackspace can only make
copies of a Rackspace Unmanaged or Customer Provided VM.
• Existing VMs or templates from outside Rackspace are available only if they are packaged
in OVF or OVA formats and imported into vCloud as a VM or template. Please refer to
the documentation of the source system for instructions on exporting to these formats.
• To download a Rackspace Managed VM, please contact the Rackspace support team.
Note
Before building, modifying or deleting a virtual machine in vCloud, review the
Rackspace Managed service automation and support requirements listed in Section 2.4, “Rackspace support services” [7]
Note
To make changes to an element that appears greyed out, shut down the VM
and make the changes while it is powered off.
4.4.1. Managing virtual machines
Procedure 4.13. Adding a VM to a vApp
1.
Double-click on the vApp.
23
RPC VMware vCloud Handbook
December 17, 2015
v1.0
2.
Click on the green (+) button to add a single VM to the vApp.
3.
Select the VM(s) to add from the catalog and click on Add, or create a completely new
VM by clicking on New Virtual Machine.
4.
If choosing New Virtual Machine, pick the machine name and hardware settings.
5.
Select the storage profile where the new VMs are to be placed.
6.
Select the network connectivity.
7.
Customize the hardware of the VM before adding it to the vApp.
8.
After clicking on Finish in the wizard window, the VM(s) will be added to the current
vApp.
Procedure 4.14. Restarting a VM
1.
Right click on a VM and select Shut Down Guest OS.
2.
Right click on the VM and select Power On.
Note
When a VM is powered off, the automation will suspend monitoring alerts for
this VM. When the VM is powered on again our automation will resume monitoring and alerting functions.
Procedure 4.15. Suspending and resuming the VM
1.
Right click on a VM and select Suspend.
2.
Right click a VM and select Resume.
Note
Usage will continue to be captured in this status as if it was still powered on.
For details see Chapter 6, “Billing” [33].
Procedure 4.16. Modifying the VM
1.
To modify a vApp or VM, right click it and click Properties.
2.
Edit the lease, CPU and Memory as needed.
Note
For more information, see Section 2.4.4, “vCloud automation events” [11] .
Procedure 4.17. Deleting the VM
1.
Shut down the VM.
2.
Right click and click Delete.
3.
Delete any ACLs created on personal firewalls in the MyRackspace portal.
24
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Warning
When a VM is deleted, it is unretrievable. Rackspace does not have backups of
personal VMs. Rackspace recommends that users create their own backups for
any accidental deletion incidents.
vCloud organization policies can be used to preserve VMs for a short period
of time after deletion by setting a vApp Storage Cleanup option. This feature
is disabled by default since a deleted VM will continue to occupy storage resources until the cleanup delay time expires and the VM is actually deleted from
storage.
4.4.2. VM Console
To access the VM console, right click on a VM and click Popout Console. You can also access
the VM by double clicking on its icon.
Note
When first connecting to a console, the browser may prompt the download of
a client plug-in for the console. The certificate of the console may need to be
manually accepted prior to access a console session. To manually accept the certificate point, open the custom console URL in your browser.
4.4.3. Snapshots
A snapshot captures the state of a VM.
• To create a snapshot, right click on a VM and click Create Snapshot.
• To revert back to a previous snapshot click Revert to Snapshot.
• To delete an unneeded snapshot click Remove Snapshot.
When reverting to a previous snapshot, Rackspace recommends removing the snapshot as
soon as the new VM's settings have been confirmed and the VM is working as expected.
Performance will decrease as time elapses between the snapshot and any updates. As the
delta file continues to grow, the VM can become unstable or experience data loss. Running
out of disk space can cause not only the snapshot VM to become unresponsive, but also
any other VMs running on the same data store.
4.4.4. Downloading a VM as a template
To download a VM as a template from vCloud, submit a request to Rackspace to enable a
template or media file in the catalog for download. When the request is met, the item can
be downloaded from the catalog. You can also save an existing Rackspace Unmanaged or
Customer Provided VM as a template in the catalog and request that Rackspace enable the
template for download.
Note
Currently, the ability to download an existing powered-off vApp has been disabled.
25
RPC VMware vCloud Handbook
December 17, 2015
v1.0
4.5. Working with vCloud networks
There are three types of networks in vCloud.
• External networks
• Organization networks
• vApp networks
These networks, along with network pools, comprise the building blocks of the vCD infrastructure.
The following network information is for reference and not all of it applies to Dedicated
vCloud. At this time, Dedicated vCloud supports only the use of:
• External networks
• Direct Organization networks
• Port-group backed network pools with Static IP pool assignments
4.5.1. External networks
External networks are the foundation of organization networks. If the organization network must access a corporate network or the internet, it will move along an external network. Configuring an external network requires preconfiguration in vCenter and for all
hosts to have access to the new port group. Once this is completed, the external network
can be added to vCD.
Figure 4.1. External networks
26
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Setting up an external network requires the following layer 3 information:
• Gateway
• Subnet mask
• DNS address
• IP address
This information is abstracted from the end user, and used to provide VMs with direct connection to the external network. The pool of IP addresses is reserved for use only with vCD.
Warning
If these addresses are not reserved and are used outside of vCD, network conflicts will occur.
4.5.2. Organization networks
An Organization is a logical representation of a tenant in vCD. End users and resources are
allocated and defined here. In each Organization, three types of networks that can be configured.
Direct network
Direct networks connect an organization to an external
network by directly connecting to a port group where
the external network is. A VM will use one IP address
from a list of IP addresses that is configured when the
network is created. A vShield edge can be deployed between the vApp and the external network to provide
NAT service and route to the external network.
Routed network
A routed network is a dedicated layer 2 network that
is a routed to an external network through a vShield
Edge. vCD deploys a vShield Edge when this network is
created and provides services that include DHCP, NAT,
Router, Firewall, Load balancing and DNS relay. Routed
networks use IPs from network pools.
Internal network (isolated)
An internal network is internal to the organization. It
does not connect to any external networks and essentially is isolated. vApps connected to this network can
only talk with other vApps on the same network. However, internal networks can span between organizations
if needed.
27
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Figure 4.2. Organization networks
4.5.3. vApp networks
vApp networks are isolated to a single vApp. They cannot span across vApps unless it they
connected to an organization network through a routed or direct connection. If a vApp
network is going to be a routed network, a vShield Edge is automatically deployed to
provude NAT services when the vApp is powered on. When connected to a routed network, a network pool is required. However, a vApp network does not need to connect to
an organization network, which enables an isolated network.
28
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Figure 4.3. vApp Networks
4.5.4. Network pools
A network pool is a group of network resources that can only be used by a vCloud Organization. These can be either logical or physical networking resources.
The network pool shares the IP address pool with organization and vApp networks for NAT
routing. vCloud supports three types of network pools that can be used by vApps.
Port-group backed
Port-group backed pools require pre-created port-groups
within the vSphere environment. Port-group backed pools do
not require vDS and can be based on vSS, vDS or Cisco Nexus
1000v.
Rackspace uses a port-group backed layer 2 network, which
enables autonomous control of the network resources and
ease of configuration.
VLAN backed
VLAN-backed network pools require a set of unused VLANs.
When an Org or vApp network based on a VLAN-backed pool
is created, a port-group is created on a dvSwitch and a VLAN is
assigned to this port-group.
vCD-NI backed
vCloud Network Isolation-backed (VCNI) network pools are
flexible, easy to configure and do not require VLANs. vCNI provides layer 2 isolation by utilizing a network overlay. This net29
RPC VMware vCloud Handbook
December 17, 2015
v1.0
work overlay is provided by MAC in MAC encapsulation and
requires a vDS. For each consumed network vCloud Director
creates a port-group and assigns this port-group a network ID
number. This network ID number is used for the encapsulation
of the traffic.
Because vCD uses MAC in MAC for the encapsulation of traffic, vCD-NI requires an increase in the MTU of the underlying
transport network (dvSwitch). This avoids frame fragmentation caused by the minor overhead in MAC encapsulation.
4.5.5. Virtual machines IP management
vCloud can be configured to allocate IP addresses to VMs automatically, allow you to manually specify an IP address, or make use of a DHCP server for IP address allocation. When assigning a VM an IP address, there are three options:
• Static IP Pool
• Static manual
• DHCP
The following image shows the options for IP Mode and the pull down for choosing the
Network:
Figure 4.4. Selecting a network
Static IP pool
This is a pool of IP addresses that is defined when the
newly created network is connected. A private IP Pool is
created when a Routed Network, Internal Network or a
vApp Network is created. Connecting the vNIC to a network with Static IP pool selected it automatically pulls
an IP from the pool at Guest Customization time and
considers it a static IP.
DHCP
This is standard DHCP services usually provided by a
vShield Edge if it is a vApp network or a Routed Network. When the vNIC starts it will request a DHCP lease
from the network. When it reaches half its lease it will
request an extension. When it is not used and the lease
expires the address will be returned back to the pool.
30
RPC VMware vCloud Handbook
December 17, 2015
Static manual
v1.0
This is manually assigning an IP to the vNIC providing it
an IP address and subnet mask. The IP address will be
persistent until it is changed.
4.6. Catalog templates
Rackspace provides a catalog of OS and Application templates. The following is a list of the
various template types that have been developed for inclusion in the Rackspace Catalog.
This list will be updated as new templates are developed.
Table 4.1. Rackspace Catalog Templates
Template Type
Templates Available
Windows Operating Systems that include Rackspace guest Windows 2012, Windows 2008 R2 Standard
OS Support
Linux Operating Systems that include Rackspace guest OS
Support
RHEL 6
Windows Operating Systems that do not include
Rackspace guest OS Support
Coming soon
Linux Operating Systems that do not include Rackspace
guest OS Support
RHEL 6
Applications that will include Rackspace guest OS and application support
Coming soon
3rd party applicances for security, monitoring and other
services
Coming soon
Rackspace will continue to enhance the vApp templates offered in the Rackspace Catalog.
The following is a list of some of the vApp template types that may be available as the catalog is developed:
• Various operating systems that will include Rackspace guest OS support on VMs that are
provisioned.
• Various operating systems that will not include Rackspace guest OS support on VMs that
are provisioned.
• Various applications that will include Rackspace guest OS support on VMs that are provisioned.
• Various 3rd party appliances to provide additional features in your cloud like security,
monitoring and other services.
4.6.1. Monthly template patching
Each month, OS vendors release patches to address security, stability, performance or other
concerns. Rackspace will update the templates in the Rackspace catalog on a monthly basis
to provide the most up-to-date versions of each operating System. A notification of monthly patches is sent to indicate which patches will be applied.
31
RPC VMware vCloud Handbook
December 17, 2015
v1.0
5. Additional VMware services
In addition to the Dedicated VMware vCloud and vCenter servers, additional types of
servers can be displayed in the management cluster. The number and type of these servers
can change over time. The following is a brief description of additional server types.
Virtual machine recovery appliance
A virtual machine recovery appliance enables image-based backup of the management cluster VMs and
provides point-in-time data restoration as well as entire VM restoration. These features allow Rackspace to
quickly recover VMs or data in the management cluster.
This system is only for use by Rackspace for this purpose
and will not back up any of the VMs created vCloud. No
customer access is provided.
vShield Manager
VMware vShield Manager is a required component of
Dedicated VMware vCloud Director that is intended to
be accessed through features in vCloud. No direct customer access is provided.
Edge FW appliances
The Edge firewall appliances provide additional security and access restrictions to the management cluster
VMs and back-end Rackspace services networks. No customer access is provided.
vRealize Operations (vROps) Virtual Appliance
VMware vRealize™ Operations™ (vROps) is a customer-managed software tool from the VMware vRealize Suite product line. It provides read-only visibility into
the VMware vSphere infrastructure and host machines.
The tool monitors the performance and efficiency of the
hosted compute infrastructure, and also enables capacity planning.
VMware Update Manager
The Update Manager automates patch management and eliminates manual tracking and patching of
vSphere hosts and virtual machines. It compares the
state of vSphere hosts with baselines, then updates and
patches hosts to enforce compliance. Rackspace uses
this system to maintain dedicated VMware services. No
customer access is provided.
32
RPC VMware vCloud Handbook
December 17, 2015
v1.0
6. Billing
Usage of the Dedicated VMware vCloud product is billed based on monthly recurring fees
for hardware and infrastructure, plus hourly utility usage fees for compute virtual machines.
6.1. Billing methods for each Dedicated VMware
vCloud component
Management and compute hypervisors , Hypervisor clusters
Management and compute hypervisors in the environment incur a monthly recurring fee. This fee is set by a
negotiated contract price.
Dedicated VMware vCloud infrastructure environment
All virtual machines and appliances included in the management cluster incur a monthly recurring. This fee is set
by a negotiated contract price.
Virtual machines
All compute virtual machines in the Dedicated VMware
vCloud environment incur an hourly recurring fee that
relates to the the Dedicated VMware vCloud services
rate card. This fee is set by a negotiated contract price.
For more information, see Dedicated vCloud Rate Card.
6.2. Detailed usage report in MyRack
The monthly invoice displays one line item per virtual machine created during the billing period. A monthly detailed usage report provide additional details about how invoiced line
items are calculated.
Access the detailed usage report by logging into the MyRackspace.com portal. Select Transactions from the account menu. Select the vCloud account type on the left
pane to see the available reports. The following graphic shows the user interface.
33
RPC VMware vCloud Handbook
December 17, 2015
v1.0
From the list of usage reports, click on the transaction ID of the report to view it. A .csv
file is generated and displayed, and you can save or export the report. The usage report includes a record for each usage event captured for each VM created. The following table
provides a description for each field in the report:
Table 6.1. Usage report table
Usage report item
Description
ACCOUNT_NUMBER
The usage report is generated for one
account number.
CHARGE
The total amount charged or discounted for this line item.
CHARGE_TYPE
This field shows whether the usage
event was a charge or a discount
to be calculated in the VM monthly
price.
DC_ID
This ID corresponds to the physical
Multiple data center IDs are listed if
Rackspace data center containing the the account contains multiple Dedicatvirtual machine.
ed VMware vCloud environments deployed in multiple Rackspace data centers.
END_DATE
The last date of the billing invoice period.
EVENT_TYPE
These events describe the type of usage recorded for each VM: OS license,
OS support, application license, application support.
GEO_ID
The geographic location where the usage is collected.
QUANTITY
The number of hours that the virtual machine is powered on or in a suspended state.
RATE_TAG
The rate for which the event type is
charged (or discounted).
REGION_ID
The region code for the geographic
location where the usage is collected.
RES_ID
The device ID number generated for
the virtual machine in Rackspace internal systems.
RES_NAME
The system name assigned to the device number for the virtual machine in
Rackspace internal systems.
SERVICE_TYPE
The product that the usage was generated for. The detailed usage report displays the Dedicated VMware
vCloud service type.
START_DATE
The first date of the billing invoice period.
vCPU
The amount of virtual CPUs deployed
for the Virtual Machine from vCloud.
34
Notes
A maximum of one event type per VM
per day is recorded. If no applications
are added, no application event types
are recorded. No OS support event
types are recorded for unsupported virtual machines.
RPC VMware vCloud Handbook
December 17, 2015
v1.0
6.3. Usage collection
Virtual machines that are powered on or suspended have usage captured for the time they
are in that state. Daily usage events are sent at midnight UTC for each server that exists at
that time.
An additional usage event is captured when the following events occur:
•
•
•
•
•
A VM is resized (vCPU or vRAM changes)
Guest OS support is added or removed
An application license is added or removed
Application support is added or removed
The server is shut down or suspended
A server is not charged for time when the server is shut down. A server is charged upon
restart.
Suspended VMs
All virtual machines in a powered on or suspended state
will incur usage during the power on period. If a virtual
machine is powered off, usage is not collected or billed.
Test VMs
During the implementation process, Rackspace will create and power on a virtual machine to test that the environment is properly configured and to ensure connectivity with Rackspace internal systems that are required
for provisioning virtual Machines. This test virtual machine is tagged to identify it, ensuring that the account
is not billed for the usage during our testing. A record
for a testing virtual machine shows an inactive and decommissioned status in vCloud and in the MyRackspace
portal.
Note
During testing, ticket notifications showing
status of the new virtual machine are displayed.
35
RPC VMware vCloud Handbook
December 17, 2015
v1.0
7. Licensing
VMware licenses purchased from Rackspace for Dedicated vCloud are installed during provisioning. Customer-supplied VMware licenses are applied by Rackspace when Dedicated
VMware vCloud is provisioned. Prior to this point, a VMware installation uses an evaluation
license.
7.1. Windows VM OS licensing
When a Rackspace-supported Windows VM is deployed from the Rackspace catalog, the
Windows license is automatically activated against the Rackspace KMS server. If an unsupported Windows VM is deployed from the Rackspace catalog, it activates with the KMS
server but requires manual configuration.
Note
The Rackspace KMS server is only accessible to systems hosted with Rackspace.
Procedure 7.1. Activating a Windows KMS client
1.
Deploy the virtual machine from the provided Windows template.
2.
After the virtual machine is deployed, assign networking resources to the virtual machine and power it on.
3.
Set DNS server entries in the virtual machine to use Rackspace DNS servers.
4.
After the virtual machine is assigned an IP address, try to ping kms.rackspace.com. For example:
Note
If the virtual machine uses an internal or a custom DNS server, add a host
name entry for KMS.RACKSPACE.COM – 50.57.57.36.
36
RPC VMware vCloud Handbook
December 17, 2015
v1.0
To check the virtual machine activation status,
type the slmgr /xpr command. For example:
5.
To activate Windows, type the slmgr /ato command. For example:
To check activation status of the virtual machine,
type the slmgr /xpr command. For example:
The Windows machine is activated. It will automatically contact the KMS server and reactivate itself after the expiration date and time passes.
Note
If the re-activation fails for any reason, Windows will display a notification. Try to ping the kms.rackspace.com server. If this fails, contact the
Rackspace account team for assistance.
37
RPC VMware vCloud Handbook
December 17, 2015
v1.0
7.2. Red Hat VM OS licensing
If you deploy a supported Red Hat virtual machine from the Rackspace catalog, the Windows license is automatically activated against our RHN server. Unsupported Red Hat virtual machines also activate with the Rackspace RHN server, but require additional manual
steps. Follow the instructions provided by the Rackspace account team, who can provide
specific activation keys.
38
RPC VMware vCloud Handbook
December 17, 2015
v1.0
8. FAQ
General
8.1.
What is Dedicated vCloud?
Dedicated VMware vCloud® is a private cloud based on VMware services hosted on
a dedicated management cluster. For more information, see the Dedicated vCloud
product page.
8.2.
How do I access Dedicated vCloud?
Dedicated vCloud environment is only accessible through a VPN connection to
Rackspace.
8.3.
What Rackspace data centers provide Dedicated vCloud?
Dedicated vCloud is available in IAD, and LON data centers.
8.4.
Are backup and antivirus included with Dedicated vCloud?
Dedicated vCloud environments are protected using the CommVault SQL server
agent in conjunction with Rackspace VM Recovery, which is an image-based backup solution. Antivirus is installed and configured using the latest Rackspace-supported platform. Only VMs in vApps created from Rackspace catalog templates with the
Managed designation include backup and antivirus services.
8.5.
How can I migrate virtual machines?
Dedicated vCloud provides a way to upload a VM, vApp, or virtual appliance in either the OVF or OVA format.
You can also migrate data to Rackspace using VMware vCloud Connector, which is
a free tool to move from your local VMware environment to the Rackspace-hosted
Dedicated vCloud environment. For additional information about migrating to Dedicated vCloud, contact Rackspace Support.
8.6.
What versions of the VMware services are currently supported in Dedicated VMware
vCloud?
Dedicated VMware vCloud supports vCloud Director and vSphere version 5.5 and
vROps version 6.x.
8.7.
Where can I find a list of known issues for Dedicated vCloud?
Known issues are listed in the release notes for each version of vCloud. You can find
your version number by clicking Help > About in vCloud. For more information, see
the VMware vCloud Director Documentation.
Access control
8.1.
How are the permissions for users controlled in Dedicated VMware vCloud?
39
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Rackspace retains administrator access to vCenter and vCloud instances. Customers
are given a limited access account. Elevated access levels are granted only as needed
to maintain security. New users are created on request, except for Active Directory
installations managed by the customer.
8.2.
How many active concurrent users can access vCloud?
A vCloud environment is limited on a per cell basis to 5000 logged-in users and 1500
active concurrent users. The limit applies to the total number of users accessing both
the user interface and the API.
8.3.
Is the same infrastructure used for login information if I have multiple vCloud instances in a single data center?
Each vCloud environment is self-contained, with its own set of user accounts.
Rackspace can provide a single authentication source for all environments; for example, the Intensive domain. Rackspace can create the same local users across all environments.
8.4.
What single sign on (SSO) capabilities are provided?
By default, vCenter and vCloud authenticate to the Rackspace Intensive domain.
Rackspace can add your domain to the VMware SSO service for vCenter and the
vCloud Organization as an additional authentication source.
8.5.
What are the restrictions to vCloud features?
Customer role limitations are described in the features and permissions tables in our
Dedicated vCloud Handbook.
Architecture
8.1.
Are Dedicated vCloud environments deployed in high availability (HA) configuration?
Yes, Dedicated vCloud environments are deployed in HA configuration.
8.2.
Is there a limit to the number of VMs per environment?
Rackspace does not impose a limit on VMs per environment. We can provide recommendations for best practices to maintain optimal performance.
8.3.
Can I access the vCenter API? Can I access the vCloud API?
Yes. You can access vCloud and vSphere APIs, subject to permissions restrictions on a
user account.
8.4.
Can I do a stretched layer 2 to allow vMotion between my existing sites?
No, stretching the data link layer across environments is not supported in Dedicated
vCloud.
8.5.
Can I add ESXi hypervisors in my data center to the Dedicated VMware vCloud environment?
40
RPC VMware vCloud Handbook
December 17, 2015
v1.0
No. Only hypervisors provided by Rackspace can be added.
8.6.
Can I manage Rackspace-hosted VMware ESXi hypervisors if I have Dedicated
VMware vCloud?
We do not provide direct access to the hypervisor. You can make hypervisor change
requests by creating a Rackspace support ticket.
8.7.
With Dedicated VMware vCloud, do I have full control over ESXi hypervisors to import or export my own VMs?
Import and export privileges are not provided on individual hypervisors. You can upload images to your Dedicated vCloud environment using the OVF Import function
of vCloud Connector.
8.8.
Can I manage vCenter plugins and add my own third party plugins?
No, write access to the vCenter server is not provided.
8.9.
Are Storage RDMs supported?
Yes, by opening a support ticket with our storage and virtualization team.
Integration
8.1.
What other VMware products are supported?
Dedicated vCloud allows customers to use other VMware products like vRealize Automation, but these products are not fully supported by Rackspace.
8.2.
Is Rackspace RackConnect supported with Dedicated VMware vCloud?
Yes.
8.3.
Does the MyRack portal work with vCloud?
Yes, you can view devices on MyRack.
8.4.
You can view devices in the MyRack portal, but VM management is only available
when using the vCloud portal or API.
You can deploy vCloud Connector, but Rackspace does not provide support for it.
8.5.
Can I deploy AlertLogic IDS with Dedicated VMware vCloud?
Yes.
Monitoring
8.1.
How are the components of this product monitored?
The management infrastructure is monitored using a combination of tools.
41
RPC VMware vCloud Handbook
December 17, 2015
v1.0
• HP SiteScope for vCenter services. This alerts Rackspace virtualization engineers
when any web services associated with Dedicated vCloud and vCloud Director are
unavailable.
• Rackwatch for hypervisor connectivity. This alerts Rackspace virtualization engineers when devices don't respond to ping requests.
• CA® Nimsoft Monitor for vCenter alarms. This alerts Rackspace virtualization engineers to alarms raised in vCenter.
Any supported vApps deployed from the Rackspace-provided catalog are monitored
by these systems.
8.2.
Is monitoring available for my unsupported VMs?
No.
8.3.
How do I know if resources are low?
Dedicated vCloud includes vRealize Operations (vROps) if the customer purchases
Rackspace-provided ESXi licensing. vROps provides advanced reporting and forecasting capabilities, as well as the ability to set Smart Alerts to notify you when resources
are low. This IT operations management tool can be helpful when optimizing resources and identifying performance bottlenecks.
42
RPC VMware vCloud Handbook
December 17, 2015
v1.0
9. Spheres of support
Spheres of support and support requests for Dedicated VMware vCloud are similar to the
current Server Virtualization product. With Dedicated VMware vCloud, you can create supported and unsupported VMs. The Rackspace virtualization team maintains the Dedicated
VMware vCloud configuration and services to ensure uptime.
9.1. Spheres of support for supported virtual machines
The following tables show spheres of support for all supported VMs.
Table 9.1. Virtualization support
Virtualization
Rackspace
VMware vCloud Director
x
VMware vCenter Server
x
VMware vCenter Operations Manager
x
VM Troubleshooting
x
Remote Administration for VMs
x
Customer
Table 9.2. Hardware support
Hardware
Rackspace
Manage delivery of equipment
x
Procure, inventory spare parts, and "Break-Fix"
equipment
x
Rackspace fully-managed dedicated NAS
x
Rackspace fully-managed dedicated SAN
x
Customer
Table 9.3. Operating system support
Operating Systems
Rackspace
Customer
Provision MS Windows and Red Hat Enterprise Linux x
(RHEL) operating system images
Ensure OS licensing compliance
x
Patch operating system
x
Table 9.4. Monitoring support
Monitoring
Rackspace
Provide monitoring for virtual machine OS and applications
x
Configure monitoring for virtual machine OS and
applications
x
Respond to monitoring alerts for virtual machine OS x
and applications
Configure and respond to infrastructure monitoring x
alerts (such as ping and port alerts)
43
Customer
RPC VMware vCloud Handbook
December 17, 2015
v1.0
Configure and respond to vCenter monitoring alerts x
Configure and respond to vCenter Operations Man- x
ager alerts (such as ping and port alerts)
Configure and respond to Infrastructure Navigator
alerts (such as(ping and port alerts)
x
Table 9.5. Network support
Network
Rackspace
Architecture design, review, and consultation
x
Configure routing and switching equipment
x
Allocate IP blocks for guest OS virtual machines
x
IP management for IP blocks assigned for all guest
OS virtual machines
x
Manage firewalls
x
Manage load balancer
x
Manage intrusion detection system
x
Monitor bandwidth consumption
x
Troubleshoot network connectivity
x
Manage firewall rule sets
x
Manage virtual machine DNS
Customer
x
x
Table 9.6. Security support
Security
Rackspace
Maintain security specifications for virtual machines
Customer
x
9.2. Spheres of support for unsupported virtual
machines
The following tables show spheres of support for all unsupported VMs, including customer-provided images.
Table 9.7. Virtualization support
Virtualization
Rackspace
Virtual machine Troubleshooting
Customer
x
vCenter Server appliance support
x
VMware vCenter Operations Manager - UI
x
VMware vCenter Operations Manager - Analytics
x
Remote administration for virtual machines
x
Table 9.8. Hardware support
Hardware
Rackspace
Manage delivery of equipment
x
Procure, inventory spare parts, and "Break-Fix"
equipment
x
Rackspace fully-managed dedicated NAS
x
44
Customer
RPC VMware vCloud Handbook
December 17, 2015
Rackspace fully-managed dedicated SAN
v1.0
x
Table 9.9. Operating system support
Operating Systems
Rackspace
Customer
Provision MS Windows and RHEL operating system
images
x
Ensure OS licensing compliance
x
Patch operating systems
x
Table 9.10. Monitoring support
Monitoring
Rackspace
Customer
Monitor virtual machine operating systems and applications
x
Configure monitoring for virtual machine OS and
applications
x
Respond to monitoring alerts for virtual machine OS
and applications
x
Configure and respond to infrastructure monitoring x
alerts (such as ping and port alerts)
Configure and respond to vCenter monitoring alerts x
Configure and respond to vCenter Operations Man- x
ager alerts (such as ping and port alerts)
Table 9.11. Network support
Network
Rackspace
Architecture design, review and consultation
x
Configure routing and switching equipment
x
Customer
Allocation of IP Blocks for guest OS virtual machines x
IP management for IP Blocks assigned for all guest
OS virtual machines
x
Manage firewalls
x
Manage load balancers
x
Manage intrusion detection systems
x
Monitor bandwidth consumption
x
Troubleshoot network connectivity
x
Manage firewall rule sets
x
Manage virtual machine DNS
x
x
Table 9.12. Security support
Security
Rackspace
Maintain security specifications for virtual machines
45
Customer
x
RPC VMware vCloud Handbook
December 17, 2015
v1.0
vCloud terms and definitions
Catalogs
Organizations use catalogs to store vApp templates and media files. The members of an organization that have access to a catalog can use the catalog's vApp templates and media files to create
their own vApps. A system administrator can allow an organization to publish a catalog to make
it available to other organizations. Organizations administrators can then choose which catalog
items to provide to their users.
Cloud Director Networking
vCloud Director supports three types of networks:
• External networks
• Organization networks
• vApp networks
Some organization networks and all vApp networks are backed by network pools.
Cloud Resources
Cloud resources are an abstraction of their underlying vSphere resources and provide the compute and memory resources for vCloud Director virtual machines and vApps, and access to storage
and network connectivity. A vApp is a virtual system that contains one or more individual virtual
machines, along with parameters that define operational details. Cloud resources include Provider
and Organization virtual Data Centers, external networks, organization networks, and network
pools.
External Networks
An external network is a logical, differentiated network based on a vSphere port group. Organization networks can connect to external networks to provide Internet connectivity to virtual machines inside of a vApp.
Network Pools
A network pool is a group of undifferentiated networks that is available for use within an Org
vDC. A network pool is backed by vSphere network resources such as VLAN IDs, port groups, or
Cloud isolated networks. vCloud Director uses network pools to create NAT-routed and internal
organization networks and all vApp networks. Network traffic on each network in a pool is isolated at layer 2 from all other networks. Each Org vDC in vCloud Director can have one network
pool. Multiple Org vDCs can share the same network pool. The network pool for an organization
vDC provides the networks created to satisfy the network quota for an Org vDC.
Organizations
vCloud Director supports multi-tenancy through the use of organizations. A vCloud organization is
a unit of administration for a collection of users, groups, and computing resources. Users authenticate at the organization level, supplying credentials established by an organization administrator
when the user was created or imported.
Organization Networks
An organization network is contained within a vCloud Director organization and is available to all
the vApps in the organization. An organization network allows vApps within an organization to
communicate with each other. You can connect an organization network to an external network
46
RPC VMware vCloud Handbook
December 17, 2015
v1.0
to provide external connectivity. Isolated organization networks are internal to the organization.
Certain types of organization networks are backed by network pools.
Organization Virtual Data Centers
An Organization Virtual Data Center (Org vDC) provides resources to an organization and is partitioned from a PvDC. Org vDCs provide an environment where virtual systems can be stored,
deployed, and operated. They also provide storage for virtual media, such as floppy disks and
CDROMs. A single organization can have multiple Org vDCs.
Provider Virtual Data Centers
A Provider Virtual Data Center (PvDC) combines the compute and memory resources of a single
vCenter Server resource pool with the storage resources of one or more data stores connected to
that resource pool. Multiple provider vDCs can be created for users in different geographic locations or business units, or for users with different performance requirements. A PvDC is the source
for Org vDCs.
Users and Groups
An organization can contain an arbitrary number of users and groups. Users can be created by the
organization administrator or imported from a directory service such as LDAP. Groups must be imported from the directory service. Permissions within an organization are controlled through the
assignment of rights and roles to users and groups.
vApp Network
A vApp network is contained within a vApp and allows virtual machines in the vApp to communicate with each other. A vApp network can connect to an organization network to allow the vApp
to communicate with other vApps in the organization and outside of the organization, if the organization network is connected to an external network. vApp networks are backed by network
pools.
vSphere Resources
vCloud Director relies on vSphere resources to provide CPU and memory to run virtual machines.
In addition, vSphere data stores provide storage for virtual machine files and other files necessary
for virtual machine operations. vCloud Director also utilizes vNetwork Distributed Switches and
vSphere port groups to support virtual machine networking. The underlying vSphere resources
can be used to create cloud resources.
47
RPC VMware vCloud Handbook
December 17, 2015
10. Additional resources
Use these additional resources to learn more about Dedicated vCloud.
• Dedicated vCloud product page
• Dedicated vCloud resources
• External VMware web site
48
v1.0
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising