How it Works
Citrix Systems
Loading...
Switch 4
User Manual
272 pgs2.75 Mb0
Table of contents
Loading...

Citrix Systems Switch 4 User Manual

CloudPlatform
(powered by Apache
CloudStack) Version 4.2
Administrator's Guide
Revised October 27, 2013 10:50 pm Pacific
Citrix CloudPlatform
CloudPlatform (powered by Apache CloudStack) Version 4.2 Administrator's Guide
CloudPlatform (powered by Apache CloudStack) Version 4.2 Administrator's Guide Revised October 27, 2013 10:50 pm Pacific
Author Citrix CloudPlatform
© 2013 Citrix Systems, Inc. All rights reserved. Specifications are subject to change without notice. Citrix Systems, Inc., the Citrix logo, Citrix XenServer, Citrix XenCenter, and CloudPlatform are trademarks or registered trademarks of Citrix Systems, Inc. All other brands or products are trademarks or registered trademarks of their respective holders.
If you have already installed CloudPlatform or you want to learn more about the ongoing operation and maintenance of a CloudPlatform-powered cloud, read this documentation. It will help you start using, configuring, and managing the ongoing operation of your cloud.
1. Getting More Information and Help 1
1.1. Additional Documentation Available ............................................................................... 1
1.2. Citrix Knowledge Center ............................................................................................... 1
1.3. Contacting Support ....................................................................................................... 1
2. Concepts 3
2.1. What Is CloudPlatform? ................................................................................................ 3
2.2. What Can CloudPlatform Do? ....................................................................................... 3
2.3. Deployment Architecture Overview ................................................................................ 4
2.3.1. Management Server Overview ........................................................................... 5
2.3.2. Cloud Infrastructure Overview ............................................................................ 5
2.3.3. Networking Overview ......................................................................................... 6
3. Cloud Infrastructure Concepts 9
3.1. About Regions ............................................................................................................. 9
3.2. About Zones ................................................................................................................ 9
3.3. About Pods ................................................................................................................ 11
3.4. About Clusters ........................................................................................................... 12
3.5. About Hosts ............................................................................................................... 13
3.6. About Primary Storage ............................................................................................... 13
3.7. About Secondary Storage ........................................................................................... 14
3.8. About Physical Networks ............................................................................................ 14
3.8.1. Basic Zone Network Traffic Types .................................................................... 15
3.8.2. Basic Zone Guest IP Addresses ....................................................................... 16
3.8.3. Advanced Zone Network Traffic Types .............................................................. 16
3.8.4. Advanced Zone Guest IP Addresses ................................................................ 16
3.8.5. Advanced Zone Public IP Addresses ................................................................ 17
3.8.6. System Reserved IP Addresses ....................................................................... 17
4. Accounts 19
4.1. Accounts, Users, and Domains ................................................................................... 19
4.1.1. Dedicating Resources to Accounts and Domains ............................................... 20
4.2. Using an LDAP Server for User Authentication ............................................................ 21
4.2.1. Configuring an LDAP Server ............................................................................ 21
4.2.2. Example LDAP Configuration Commands ......................................................... 23
4.2.3. Search Base ................................................................................................... 23
4.2.4. Query Filter ..................................................................................................... 24
4.2.5. Search User Bind DN ...................................................................................... 25
4.2.6. SSL Keystore Path and Password .................................................................... 25
5. User Services Overview 27
5.1. Service Offerings, Disk Offerings, Network Offerings, and Templates ............................. 27
6. User Interface 29
6.1. Supported Browsers ................................................................................................... 29
6.2. Log In to the UI ......................................................................................................... 29
6.2.1. End User's UI Overview ................................................................................... 29
6.2.2. Root Administrator's UI Overview ..................................................................... 30
6.2.3. Logging In as the Root Administrator ................................................................ 30
6.2.4. Changing the Root Password ........................................................................... 31
6.3. Using SSH Keys for Authentication ............................................................................. 31
6.3.1. Creating an Instance from a Template that Supports SSH Keys .......................... 31
6.3.2. Creating the SSH Keypair ................................................................................ 32
6.3.3. Creating an Instance ........................................................................................ 33
6.3.4. Logging In Using the SSH Keypair ................................................................... 33
6.3.5. Resetting SSH Keys ........................................................................................ 33
iii
CloudPlatform (powered by Apache CloudStack) Version 4.2 Administrator's Guide
7. Using Projects to Organize Users and Resources 35
7.1. Overview of Projects .................................................................................................. 35
7.2. Configuring Projects ................................................................................................... 35
7.2.1. Setting Up Invitations ....................................................................................... 35
7.2.2. Setting Resource Limits for Projects ................................................................. 36
7.2.3. Setting Project Creator Permissions .................................................................. 36
7.3. Creating a New Project .............................................................................................. 37
7.4. Adding Members to a Project ...................................................................................... 37
7.4.1. Sending Project Membership Invitations ............................................................ 37
7.4.2. Adding Project Members From the UI ............................................................... 38
7.5. Accepting a Membership Invitation .............................................................................. 38
7.6. Suspending or Deleting a Project ................................................................................ 39
7.7. Using the Project View ............................................................................................... 39
8. Steps to Provisioning Your Cloud Infrastructure 41
8.1. Overview of Provisioning Steps ................................................................................... 41
8.2. Adding Regions (optional) ........................................................................................... 42
8.2.1. The First Region: The Default Region ............................................................... 42
8.2.2. Adding a Region .............................................................................................. 42
8.2.3. Adding Third and Subsequent Regions ............................................................. 43
8.2.4. Deleting a Region ............................................................................................ 44
8.3. Adding a Zone ........................................................................................................... 45
8.3.1. Create a Secondary Storage Mount Point for the New Zone ............................... 45
8.3.2. Prepare the System VM Template .................................................................... 45
8.3.3. Steps to Add a New Zone ................................................................................ 46
8.4. Adding a Pod ............................................................................................................. 55
8.5. Adding a Cluster ........................................................................................................ 56
8.5.1. Add Cluster: KVM or XenServer ....................................................................... 56
8.5.2. Add Cluster: OVM ........................................................................................... 56
8.5.3. Add Cluster: vSphere ....................................................................................... 57
8.6. Adding a Host ............................................................................................................ 60
8.6.1. Adding a Host (XenServer, KVM, or OVM) ........................................................ 60
8.6.2. Adding a Host (vSphere) .................................................................................. 62
8.7. Adding Primary Storage .............................................................................................. 62
8.8. Adding Secondary Storage ......................................................................................... 63
8.8.1. Adding an NFS Secondary Staging Store for Each Zone .................................... 64
8.9. Initialize and Test ....................................................................................................... 65
9. Service Offerings 67
9.1. Compute and Disk Service Offerings ........................................................................... 67
9.1.1. Creating a New Compute Offering .................................................................... 67
9.1.2. Creating a New Disk Offering ........................................................................... 68
9.1.3. Modifying or Deleting a Service Offering ........................................................... 69
9.2. System Service Offerings ........................................................................................... 69
9.2.1. Creating a New System Service Offering .......................................................... 69
9.2.2. Changing the Secondary Storage VM Service Offering on a Guest Network ......... 70
10. Setting Up Networking for Users 73
10.1. Overview of Setting Up Networking for Users ............................................................. 73
10.2. About Virtual Networks ............................................................................................. 73
10.2.1. Isolated Networks .......................................................................................... 73
10.2.2. Shared Networks ........................................................................................... 73
10.2.3. Runtime Allocation of Virtual Network Resources ............................................. 74
10.3. Network Service Providers ........................................................................................ 74
10.4. Network Service Providers Support Matrix ................................................................. 74
iv
10.4.1. Individual ....................................................................................................... 74
10.4.2. Support Matrix for an Isolated Network (Combination) ...................................... 75
10.4.3. Support Matrix for Shared Network (Combination) ............................................ 76
10.4.4. Support Matrix for Basic Zone ........................................................................ 77
10.5. Network Offerings ..................................................................................................... 77
10.5.1. Creating a New Network Offering ................................................................... 78
10.5.2. Changing the Network Offering on a Guest Network ........................................ 81
10.5.3. Creating and Changing a Virtual Router Network Offering ................................. 82
11. Working With Virtual Machines 85
11.1. About Working with Virtual Machines ......................................................................... 85
11.2. Best Practices for Virtual Machines ........................................................................... 85
11.2.1. Monitor VMs for Max Capacity ........................................................................ 86
11.2.2. Install Required Tools and Drivers .................................................................. 86
11.3. VM Lifecycle ............................................................................................................ 86
11.4. Creating VMs ........................................................................................................... 87
11.4.1. Creating a VM from a template ....................................................................... 87
11.4.2. Creating a VM from an ISO ............................................................................ 88
11.4.3. Configuring Usage of Linked Clones on VMware ............................................. 88
11.5. Accessing VMs ......................................................................................................... 89
11.6. Appending a Display Name to the Guest VM’s Internal Name ...................................... 89
11.7. Stopping and Starting VMs ....................................................................................... 90
11.8. Assigning VMs to Hosts ............................................................................................ 90
11.8.1. Affinity Groups ............................................................................................... 91
11.9. Virtual Machine Snapshots for VMware ...................................................................... 92
11.9.1. Limitations on VM Snapshots ......................................................................... 93
11.9.2. Configuring VM Snapshots ............................................................................. 93
11.9.3. Using VM Snapshots ..................................................................................... 93
11.10. Changing the VM Name, OS, or Group .................................................................... 94
11.11. Changing the Service Offering for a VM ................................................................... 95
11.11.1. CPU and Memory Scaling for Running VMs .................................................. 95
11.11.2. Updating Existing VMs ................................................................................. 96
11.11.3. Configuring Dynamic CPU and RAM Scaling ................................................. 96
11.11.4. How to Dynamically Scale CPU and RAM ..................................................... 96
11.11.5. Limitations ................................................................................................... 96
11.12. Resetting the Virtual Machine Root Volume on Reboot ............................................. 97
11.13. Moving VMs Between Hosts (Manual Live Migration) ................................................ 97
11.14. Deleting VMs .......................................................................................................... 98
11.15. Recovering a Destroyed VM .................................................................................... 98
11.16. Working with ISOs .................................................................................................. 98
11.16.1. Adding an ISO ............................................................................................. 99
11.16.2. Attaching an ISO to a VM ........................................................................... 100
11.16.3. Changing a VM's Base Image ..................................................................... 100
12. Working With Hosts 103
12.1. Adding Hosts .......................................................................................................... 103
12.2. Scheduled Maintenance and Maintenance Mode for Hosts ........................................ 103
12.2.1. vCenter and Maintenance Mode ................................................................... 103
12.2.2. XenServer and Maintenance Mode ............................................................... 103
12.3. Disabling and Enabling Zones, Pods, and Clusters ................................................... 104
12.4. Removing Hosts ..................................................................................................... 104
12.4.1. Removing XenServer and KVM Hosts ........................................................... 105
12.4.2. Removing vSphere Hosts ............................................................................. 105
12.5. Re-Installing Hosts .................................................................................................. 105
12.6. Maintaining Hypervisors on Hosts ............................................................................ 105
v
CloudPlatform (powered by Apache CloudStack) Version 4.2 Administrator's Guide
12.7. Using Cisco UCS as Bare Metal Host CloudPlatform ................................................ 105
12.7.1. Registering a UCS Manager ......................................................................... 106
12.7.2. Associating a Profile with a UCS Blade ......................................................... 106
12.7.3. Disassociating a Profile from a UCS Blade .................................................... 107
12.8. Changing Host Password ........................................................................................ 107
12.9. Over-Provisioning and Service Offering Limits .......................................................... 108
12.9.1. Limitations on Over-Provisioning in XenServer and KVM ................................ 109
12.9.2. Requirements for Over-Provisioning .............................................................. 109
12.9.3. Setting Over-Provisioning Ratios ................................................................... 109
12.9.4. Service Offering Limits and Over-Provisioning ................................................ 110
12.10. VLAN Provisioning ................................................................................................ 110
12.10.1. VLAN Allocation Example ........................................................................... 111
12.10.2. Adding Non Contiguous VLAN Ranges ........................................................ 111
12.10.3. Assigning VLANs to Isolated Networks ........................................................ 112
13. Working with Templates 113
13.1. Creating Templates: Overview ................................................................................. 113
13.2. Requirements for Templates ................................................................................... 113
13.3. Best Practices for Templates ................................................................................... 113
13.4. The Default Template ............................................................................................. 113
13.5. Private and Public Templates .................................................................................. 114
13.6. Creating a Template from an Existing Virtual Machine .............................................. 114
13.7. Creating a Template from a Snapshot ..................................................................... 115
13.8. Uploading Templates .............................................................................................. 115
13.9. Exporting Templates ............................................................................................... 117
13.10. Creating a Windows Template ............................................................................... 117
13.10.1. System Preparation for Windows Server 2008 R2 ........................................ 117
13.10.2. System Preparation for Windows Server 2003 R2 ........................................ 121
13.11. Importing Amazon Machine Images ....................................................................... 122
13.12. Converting a Hyper-V VM to a Template ................................................................ 125
13.13. Adding Password Management to Your Templates ................................................. 126
13.13.1. Linux OS Installation .................................................................................. 127
13.13.2. Windows OS Installation ............................................................................. 127
13.14. Deleting Templates ............................................................................................... 127
14. Working With Storage 129
14.1. Storage Overview ................................................................................................... 129
14.2. Primary Storage ..................................................................................................... 129
14.2.1. Best Practices for Primary Storage ............................................................... 129
14.2.2. Runtime Behavior of Primary Storage ........................................................... 129
14.2.3. Hypervisor Support for Primary Storage ........................................................ 129
14.2.4. Storage Tags ............................................................................................... 130
14.2.5. Maintenance Mode for Primary Storage ......................................................... 131
14.3. Secondary Storage ................................................................................................. 131
14.3.1. Best Practices for Secondary Storage ........................................................... 131
14.3.2. Changing the Secondary Storage IP Address ................................................ 131
14.3.3. Changing Secondary Storage Servers ........................................................... 132
14.4. Working With Volumes ............................................................................................ 132
14.4.1. Creating a New Volume ............................................................................... 132
14.4.2. Uploading an Existing Volume to a Virtual Machine ........................................ 133
14.4.3. Attaching a Volume ...................................................................................... 134
14.4.4. Detaching and Moving Volumes .................................................................... 135
14.4.5. VM Storage Migration .................................................................................. 135
14.4.6. Resizing Volumes ........................................................................................ 137
14.4.7. Reset VM to New Root Disk on Reboot ......................................................... 138
vi
14.4.8. Volume Deletion and Garbage Collection ...................................................... 138
14.5. Working with Snapshots .......................................................................................... 138
14.5.1. Automatic Snapshot Creation and Retention .................................................. 139
14.5.2. Incremental Snapshots and Backup .............................................................. 139
14.5.3. Volume Status ............................................................................................. 139
14.5.4. Snapshot Restore ........................................................................................ 140
14.5.5. Snapshot Job Throttling ................................................................................ 140
14.5.6. VMware Volume Snapshot Performance ........................................................ 140
15. Working with Usage 141
15.1. Configuring the Usage Server ................................................................................. 141
15.2. Setting Usage Limits ............................................................................................... 143
15.2.1. Globally Configured Limits ............................................................................ 144
15.2.2. Default Account Resource Limits .................................................................. 145
15.2.3. Per-Domain Limits ....................................................................................... 146
16. Managing Networks and Traffic 147
16.1. Guest Traffic .......................................................................................................... 147
16.2. Networking in a Pod ............................................................................................... 147
16.3. Networking in a Zone .............................................................................................. 148
16.4. Basic Zone Physical Network Configuration .............................................................. 149
16.5. Advanced Zone Physical Network Configuration ....................................................... 149
16.5.1. Configuring Isolated Guest Network .............................................................. 149
16.5.2. Configure Public Traffic in an Advanced Zone ................................................ 150
16.5.3. Configuring a Shared Guest Network ............................................................ 151
16.6. Using Security Groups to Control Traffic to VMs ....................................................... 152
16.6.1. About Security Groups ................................................................................. 152
16.6.2. Security Groups in Advanced Zones (KVM Only) ........................................... 152
16.6.3. Enabling Security Groups ............................................................................. 153
16.6.4. Adding a Security Group .............................................................................. 153
16.6.5. Adding Ingress and Egress Rules to a Security Group .................................... 153
16.7. External Firewalls and Load Balancers .................................................................... 154
16.7.1. About Using a NetScaler Load Balancer ........................................................ 155
16.7.2. Configuring SNMPCommunity String on a RHEL Server ................................. 156
16.7.3. Initial Setup of External Firewalls and Load Balancers .................................... 157
16.7.4. Ongoing Configuration of External Firewalls and Load Balancers ..................... 158
16.8. Load Balancer Rules .............................................................................................. 158
16.8.1. Adding a Load Balancer Rule ....................................................................... 158
16.8.2. Configuring AutoScale .................................................................................. 159
16.8.3. Sticky Session Policies for Load Balancer Rules ............................................ 164
16.8.4. Health Checks for Load Balancer Rules ........................................................ 164
16.9. Global Server Load Balancing ................................................................................. 165
16.9.1. About Global Server Load Balancing ............................................................. 165
16.9.2. Configuring GSLB ........................................................................................ 167
16.10. Using Multiple Guest Networks .............................................................................. 172
16.10.1. Adding an Additional Guest Network ........................................................... 172
16.10.2. Reconfiguring Networks in VMs .................................................................. 172
16.11. Guest IP Ranges .................................................................................................. 174
16.12. Acquiring a New IP Address .................................................................................. 174
16.13. Releasing an IP Address ....................................................................................... 174
16.14. Reserving Public IP Addresses and VLANs for Accounts ......................................... 175
16.14.1. Dedicating IP Address Ranges to an Account .............................................. 175
16.14.2. Dedicating VLAN Ranges to an Account ...................................................... 176
16.15. IP Reservation in Isolated Guest Networks ............................................................. 177
16.15.1. IP Reservation Considerations .................................................................... 177
vii
CloudPlatform (powered by Apache CloudStack) Version 4.2 Administrator's Guide
16.15.2. Limitations ................................................................................................. 178
16.15.3. Best Practices ............................................................................................ 178
16.15.4. Reserving an IP Range .............................................................................. 178
16.16. Configuring Multiple IP Addresses on a Single NIC ................................................. 178
16.16.1. Use Cases ................................................................................................. 179
16.16.2. Guidelines ................................................................................................. 179
16.16.3. Assigning Additional IPs to a VM ................................................................ 179
16.16.4. Port Forwarding and StaticNAT Services Changes ....................................... 179
16.17. Multiple Subnets in Shared Network ...................................................................... 180
16.17.1. Prerequisites and Guidelines ...................................................................... 180
16.17.2. Adding Multiple Subnets to a Shared Network .............................................. 180
16.18. About Elastic IP .................................................................................................... 181
16.19. Portable IPs ......................................................................................................... 183
16.19.1. About Portable IP ....................................................................................... 183
16.19.2. Configuring Portable IPs ............................................................................. 184
16.19.3. Acquiring a Portable IP ............................................................................... 184
16.19.4. Transferring Portable IP .............................................................................. 185
16.20. Static NAT ............................................................................................................ 185
16.20.1. Enabling or Disabling Static NAT ................................................................ 185
16.21. IP Forwarding and Firewalling ............................................................................... 186
16.21.1. Egress Firewall Rules in an Advanced Zone ................................................ 186
16.21.2. Firewall Rules ............................................................................................ 188
16.21.3. Port Forwarding ......................................................................................... 189
16.22. IP Load Balancing ................................................................................................ 189
16.23. DNS and DHCP ................................................................................................... 190
16.24. Remote Access VPN ............................................................................................ 190
16.24.1. Configuring Remote Access VPN ................................................................ 190
16.24.2. Using Remote Access VPN with Windows ................................................... 191
16.24.3. Using Remote Access VPN with Mac OS X ................................................. 192
16.24.4. Setting Up a Site-to-Site VPN Connection .................................................... 192
16.25. Isolation in Advanced Zone Using Private VLAN ..................................................... 200
16.25.1. About Private VLAN ................................................................................... 200
16.25.2. Prerequisites .............................................................................................. 201
16.25.3. Creating a PVLAN-Enabled Guest Network .................................................. 201
16.26. About Inter-VLAN Routing ..................................................................................... 202
16.27. Configuring a Virtual Private Cloud ........................................................................ 204
16.27.1. About Virtual Private Clouds ....................................................................... 204
16.27.2. Adding a Virtual Private Cloud .................................................................... 206
16.27.3. Adding Tiers .............................................................................................. 207
16.27.4. Configuring Network Access Control List ..................................................... 209
16.27.5. Adding a Private Gateway to a VPC ............................................................ 212
16.27.6. Deploying VMs to the Tier .......................................................................... 215
16.27.7. Deploying VMs to VPC Tier and Shared Networks ....................................... 215
16.27.8. Acquiring a New IP Address for a VPC ....................................................... 216
16.27.9. Releasing an IP Address Alloted to a VPC .................................................. 217
16.27.10. Enabling or Disabling Static NAT on a VPC ............................................... 218
16.27.11. Adding Load Balancing Rules on a VPC .................................................... 219
16.27.12. Adding a Port Forwarding Rule on a VPC .................................................. 225
16.27.13. Removing Tiers ........................................................................................ 226
16.27.14. Editing, Restarting, and Removing a Virtual Private Cloud ........................... 227
16.28. Persistent Networks .............................................................................................. 227
16.28.1. Persistent Network Considerations .............................................................. 227
16.28.2. Creating a Persistent Guest Network ........................................................... 228
viii
17. Working with System Virtual Machines 229
17.1. The System VM Template ....................................................................................... 229
17.2. Multiple System VM Support for VMware ................................................................. 229
17.3. Console Proxy ........................................................................................................ 229
17.3.1. Changing the Console Proxy SSL Certificate and Domain ............................... 230
17.4. Virtual Router ......................................................................................................... 231
17.4.1. Configuring the Virtual Router ....................................................................... 231
17.4.2. Upgrading a Virtual Router with System Service Offerings .............................. 232
17.4.3. Best Practices for Virtual Routers ................................................................. 232
17.5. Secondary Storage VM ........................................................................................... 232
18. System Reliability and High Availability 233
18.1. HA for Management Server ..................................................................................... 233
18.2. HA-Enabled Virtual Machines .................................................................................. 233
18.3. Dedicated HA Hosts ............................................................................................... 233
18.4. Primary Storage Outage and Data Loss ................................................................... 234
18.5. Secondary Storage Outage and Data Loss .............................................................. 234
18.6. Limiting the Rate of API Requests ........................................................................... 234
18.6.1. Configuring the API Request Rate ................................................................ 234
18.6.2. Limitations on API Throttling ......................................................................... 235
19. Managing the Cloud 237
19.1. Using Tags to Organize Resources in the Cloud ....................................................... 237
19.2. Setting Configuration Parameters ............................................................................ 238
19.2.1. About Configuration Parameters ................................................................... 238
19.2.2. Setting Global Configuration Parameters ....................................................... 239
19.2.3. Setting Local Configuration Parameters ......................................................... 239
19.2.4. Granular Global Configuration Parameters ..................................................... 240
19.3. Changing the Database Configuration ...................................................................... 242
19.4. Administrator Alerts ................................................................................................. 242
19.4.1. Customizing Alerts with Global Configuration Settings .................................... 243
19.4.2. Sending Alerts to External SNMP and Syslog Managers ................................. 243
19.5. Customizing the Network Domain Name .................................................................. 245
19.6. Stopping and Restarting the Management Server ..................................................... 246
20. CloudPlatform API 247
20.1. Provisioning and Authentication API ........................................................................ 247
20.2. Allocators ............................................................................................................... 247
20.3. User Data and Meta Data ....................................................................................... 247
21. Tuning 249
21.1. Performance Monitoring .......................................................................................... 249
21.2. Increase Management Server Maximum Memory ..................................................... 249
21.3. Set Database Buffer Pool Size ................................................................................ 249
21.4. Set and Monitor Total VM Limits per Host ................................................................ 250
21.5. Configure XenServer dom0 Memory ........................................................................ 250
22. Troubleshooting 251
22.1. Events .................................................................................................................... 251
22.1.1. Event Logs .................................................................................................. 251
22.1.2. Event Notification ......................................................................................... 251
22.1.3. Standard Events .......................................................................................... 252
22.1.4. Long Running Job Events ............................................................................ 252
22.1.5. Event Log Queries ....................................................................................... 253
22.1.6. Deleting and Archiving Events and Alerts ...................................................... 253
22.2. Working with Server Logs ....................................................................................... 254
ix
CloudPlatform (powered by Apache CloudStack) Version 4.2 Administrator's Guide
22.3. Log Collection Utility cloud-bugtool .......................................................................... 255
22.3.1. Using cloud-bugtool ..................................................................................... 255
22.4. Data Loss on Exported Primary Storage .................................................................. 255
22.5. Recovering a Lost Virtual Router ............................................................................. 256
22.6. Maintenance mode not working on vCenter .............................................................. 256
22.7. Unable to deploy VMs from uploaded vSphere template ............................................ 257
22.8. Unable to power on virtual machine on VMware ....................................................... 257
22.9. Load balancer rules fail after changing network offering ............................................ 258
A. Event Types 259 B. Alerts 261
x
Chapter 1.
Getting More Information and Help

1.1. Additional Documentation Available

The following guides are available:
• Installation Guide — Covers initial installation of CloudPlatform. It aims to cover in full detail all the steps and requirements to obtain a functioning cloud deployment.
At times, this guide mentions additional topics in the context of installation tasks, but does not give full details on every topic. Additional details on many of these topics can be found in the CloudPlatform Administration Guide. For example, security groups, firewall and load balancing rules, IP address allocation, and virtual routers are covered in more detail in the Administration Guide.
• Administration Guide — Discusses how to set up services for the end users of your cloud. Also covers ongoing runtime management and maintenance. This guide discusses topics like domains, accounts, service offerings, projects, guest networks, administrator alerts, virtual machines, storage, and measuring resource usage.
• Developer's Guide — How to use the API to interact with CloudPlatform programmatically.

1.2. Citrix Knowledge Center

Troubleshooting articles by the Citrix support team are available in the Citrix Knowledge Center, at
support.citrix.com/product/cs/1.

1.3. Contacting Support

The support team is available to help customers plan and execute their installations. To contact the support team, log in to the support portal at support.citrix.com/cloudsupport2 by using the account credentials you received when you purchased your support contract.
1
http://support.citrix.com/product/cs/
2
http://support.citrix.com/cloudsupport
1
2
Chapter 2.
Concepts

2.1. What Is CloudPlatform?

CloudPlatform is a software platform that pools computing resources to build public, private, and hybrid Infrastructure as a Service (IaaS) clouds. CloudPlatform manages the network, storage, and compute nodes that make up a cloud infrastructure. Use CloudPlatform to deploy, manage, and configure cloud computing environments.
Typical users are service providers and enterprises. With CloudPlatform, you can:
• Set up an on-demand, elastic cloud computing service. Service providers can sell self service virtual machine instances, storage volumes, and networking configurations over the Internet.
• Set up an on-premise private cloud for use by employees. Rather than managing virtual machines in the same way as physical machines, with CloudPlatform an enterprise can offer self-service virtual machines to users without involving IT departments.

2.2. What Can CloudPlatform Do?

Multiple Hypervisor Support
CloudPlatform works with a variety of hypervisors. A single cloud deployment can contain multiple hypervisor implementations. You have the complete freedom to choose the right hypervisor for your workload.
CloudPlatform is designed to work with open source Xen and KVM hypervisors as well as enterprise­grade hypervisors such as Citrix XenServer, VMware vSphere, and Oracle VM (OVM).
3
Chapter 2. Concepts
Massively Scalable Infrastructure Management
CloudPlatform can manage tens of thousands of servers installed in multiple geographically distributed datacenters. The centralized management server scales linearly, eliminating the need for intermediate cluster-level management servers. No single component failure can cause cloud-wide outage. Periodic maintenance of the management server can be performed without affecting the functioning of virtual machines running in the cloud.
Automatic Configuration Management
CloudPlatform automatically configures each guest virtual machine’s networking and storage settings.
CloudPlatform internally manages a pool of virtual appliances to support the cloud itself. These appliances offer services such as firewalling, routing, DHCP, VPN access, console proxy, storage access, and storage replication. The extensive use of virtual appliances simplifies the installation, configuration, and ongoing management of a cloud deployment.
Graphical User Interface
CloudPlatform offers an administrator's Web interface, used for provisioning and managing the cloud, as well as an end-user's Web interface, used for running VMs and managing VM templates. The UI can be customized to reflect the desired service provider or enterprise look and feel.
API and Extensibility
CloudPlatform provides an API that gives programmatic access to all the management features available in the UI. This API enables the creation of command line tools and new user interfaces to suit particular needs.
The CloudPlatform pluggable allocation architecture allows the creation of new types of allocators for the selection of storage and hosts.
High Availability
CloudPlatform has a number of features to increase the availability of the system. The Management Server itself, which is the main controlling software at the heart of CloudPlatform, may be deployed in a multi-node installation where the servers are load balanced. MySQL may be configured to use replication to provide for a manual failover in the event of database loss. For the hosts, CloudPlatform supports NIC bonding and the use of separate networks for storage as well as iSCSI Multipath.

2.3. Deployment Architecture Overview

A CloudPlatform installation consists of two parts: the Management Server and the cloud infrastructure that it manages. When you set up and manage a CloudPlatform cloud, you provision resources such as hosts, storage devices, and IP addresses into the Management Server, and the Management Server manages those resources.
The minimum production installation consists of one machine running the CloudPlatform Management Server and another machine to act as the cloud infrastructure (in this case, a very simple infrastructure consisting of one host running hypervisor software). In a trial installation, a single machine can act as both the Management Server and the hypervisor host (using the KVM hypervisor).
4
Management Server Overview
A more full-featured installation consists of a highly-available multi-node Management Server installation and up to thousands of hosts using any of several advanced networking setups. For information about deployment options, see Choosing a Deployment Architecture in the Installation Guide.

2.3.1. Management Server Overview

The Management Server is the CloudPlatform software that manages cloud resources. By interacting with the Management Server through its UI or API, you can configure and manage your cloud infrastructure.
The Management Server runs on a dedicated server or VM. It controls allocation of virtual machines to hosts and assigns storage and IP addresses to the virtual machine instances. The Management Server runs in a Tomcat container and uses a MySQL database for persistence.
The machine where the Management Server runs must meet the system requirements described in Minimum System Requirements in the Installation Guide.
The Management Server:
• Provides the web user interface for the administrator and a reference user interface for end users.
• Provides the APIs for CloudPlatform.
• Manages the assignment of guest VMs to particular hosts.
• Manages the assignment of public and private IP addresses to particular accounts.
• Manages the allocation of storage to guests as virtual disks.
• Manages snapshots, templates, and ISO images, possibly replicating them across data centers.
• Provides a single point of configuration for the cloud.

2.3.2. Cloud Infrastructure Overview

The Management Server manages one or more zones (typically, datacenters) containing host computers where guest virtual machines will run. The cloud infrastructure is organized as follows:
• Region: To increase reliability of the cloud, you can optionally group resources into multiple geographic regions. A region consists of one or more zones.
5
Chapter 2. Concepts
• Zone: Typically, a zone is equivalent to a single datacenter. A zone consists of one or more pods and secondary storage.
• Pod: A pod is usually one rack of hardware that includes a layer-2 switch and one or more clusters.
• Cluster: A cluster consists of one or more hosts and primary storage.
• Host: A single compute node within a cluster. The hosts are where the actual cloud services run in the form of guest virtual machines.
• Primary storage is associated with a cluster, and it can also be provisioned on a zone-wide basis. It stores the disk volumes for all the VMs running on hosts in that cluster.
• Secondary storage is associated with a zone, and it can also be provisioned as object storage that is available throughout the cloud. It stores templates, ISO images, and disk volume snapshots.
More Information
For more information, see Chapter 3, Cloud Infrastructure Concepts.

2.3.3. Networking Overview

CloudPlatform offers two types of networking scenario:
6
Networking Overview
• Basic. Provides a single network where guest isolation can be provided through layer-3 means such as security groups (IP address source filtering).
• Advanced. For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing guest isolation.
For more details, see Network Setup in the Installation Guide.
7
8
Chapter 3.
Cloud Infrastructure Concepts

3.1. About Regions

To increase reliability of the cloud, you can optionally group resources into multiple geographic regions. A region is the largest available organizational unit within a CloudPlatform deployment. A region is made up of several availability zones, where each zone is equivalent to a datacenter. Each region is controlled by its own cluster of Management Servers, running in one of the zones. The zones in a region are typically located in close geographical proximity. Regions are a useful technique for providing fault tolerance and disaster recovery.
By grouping zones into regions, the cloud can achieve higher availability and scalability. User accounts can span regions, so that users can deploy VMs in multiple, widely-dispersed regions. Even if one of the regions becomes unavailable, the services are still available to the end-user through VMs deployed in another region. And by grouping communities of zones under their own nearby Management Servers, the latency of communications within the cloud is reduced compared to managing widely-dispersed zones from a single central Management Server.
Usage records can also be consolidated and tracked at the region level, creating reports or invoices for each geographic region.
Regions are visible to the end user. When a user starts a guest VM on a particular CloudPlatform Management Server, the user is implicitly selecting that region for their guest. Users might also be required to copy their private templates to additional regions to enable creation of guest VMs using their templates in those regions.

3.2. About Zones

A zone is the second largest organizational unit within a CloudPlatform deployment. A zone typically corresponds to a single datacenter, although it is permissible to have multiple zones in a datacenter.
9
Chapter 3. Cloud Infrastructure Concepts
The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required).
A zone consists of:
• One or more pods. Each pod contains one or more clusters of hosts and one or more primary storage servers.
• (Optional) If zone-wide primary storage is desired, a zone may contain one or more primary storage servers, which are shared by all the pods in the zone. (Supported for KVM and VMware hosts)
• Secondary storage, which is shared by all the pods in the zone.
Zones are visible to the end user. When a user starts a guest VM, the user must select a zone for their guest. Users might also be required to copy their private templates to additional zones to enable creation of guest VMs using their templates in those zones.
Zones can be public or private. Public zones are visible to all users. This means that any user may create a guest in that zone. Private zones are reserved for a specific domain. Only users in that domain or its subdomains may create guests in that zone.
Hosts in the same zone are directly accessible to each other without having to go through a firewall. Hosts in different zones can access each other through statically configured VPN tunnels.
10
About Pods
For each zone, the administrator must decide the following.
• How many pods to place in a zone.
• How many clusters to place in each pod.
• How many hosts to place in each cluster.
• (Optional) If zone-wide primary storage is being used, decide how many primary storage servers to place in each zone and total capacity for these storage servers. (Supported for KVM and VMware hosts)
• How many primary storage servers to place in each cluster and total capacity for these storage servers.
• How much secondary storage to deploy in a zone.
When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage.
(VMware) In order to support zone-wide functions for VMware, CloudPlatform is aware of VMware Datacenters and can map each Datacenter to a CloudPlatform zone. To enable features like storage live migration and zone-wide primary storage for VMware hosts, CloudPlatform has to make sure that a zone contains only a single VMware Datacenter. Therefore, when you are creating a new CloudPlatform zone, you can select a VMware Datacenter for the zone. If you are provisioning multiple VMware Datacenters, each one will be set up as a single zone in CloudPlatform.
Note
If you are upgrading from a previous CloudPlatform version, and your existing deployment contains a zone with clusters from multiple VMware Datacenters, that zone will not be forcibly migrated to the new model. It will continue to function as before. However, any new zone-wide operations introduced in CloudPlatform 4.2, such as zone-wide primary storage and live storage migration, will not be available in that zone.

3.3. About Pods

A pod often represents a single rack. Hosts in the same pod are in the same subnet. A pod is the third-largest organizational unit within a CloudPlatform deployment. Pods are contained within zones, and zones can be contained within regions. Each zone can contain one or more pods. A pod consists of one or more clusters of hosts and one or more primary storage servers. Pods are not visible to the end user.
11
Chapter 3. Cloud Infrastructure Concepts

3.4. About Clusters

A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, a set of OVM hosts, or a VMware cluster preconfigured in vCenter. The hosts in a cluster all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared primary storage. Virtual machine instances (VMs) can be live-migrated from one host to another within the same cluster without interrupting service to the user.
A cluster is the fourth-largest organizational unit within a CloudPlatform deployment. Clusters are contained within pods, pods are contained within zones, and zones can be contained within regions. Size of the cluster is only limited by the underlying hypervisor, although the CloudPlatform recommends you stay below the theoretically allowed maximum cluster size in most cases.
A cluster consists of one or more hosts and one or more primary storage servers.
Even when local storage is used, clusters are still required. In this case, there is just one host per cluster.
(VMware) If you use VMware hypervisor hosts in your CloudPlatform deployment, each VMware cluster is managed by a vCenter server. The CloudPlatform administrator must register the vCenter
12
About Hosts
server with CloudPlatform. There may be multiple vCenter servers per zone. Each vCenter server may manage multiple VMware clusters.

3.5. About Hosts

A host is a single computer. Hosts provide the computing resources that run guest virtual machines. Each host has hypervisor software installed on it to manage the guest VMs. For example, a host can be a Citrix XenServer server, a Linux KVM-enabled server, or an ESXi server.
The host is the smallest organizational unit within a CloudPlatform deployment. Hosts are contained within clusters, clusters are contained within pods, pods are contained within zones, and zones can be contained within regions.
Hosts in a CloudPlatform deployment:
• Provide the CPU, memory, storage, and networking resources needed to host the virtual machines
• Interconnect using a high bandwidth TCP/IP network and connect to the Internet
• May reside in multiple data centers across different geographic locations
• May have different capacities (different CPU speeds, different amounts of RAM, etc.), although the hosts within a cluster must all be homogeneous
Additional hosts can be added at any time to provide more capacity for guest VMs. CloudPlatform automatically detects the amount of CPU and memory resources provided by the hosts. Hosts are not visible to the end user. An end user cannot determine which host their guest has been
assigned to. For a host to function in CloudPlatform, you must do the following:
• Install hypervisor software on the host
• Assign an IP address to the host
• Ensure the host is connected to the CloudPlatform Management Server.

3.6. About Primary Storage

Primary storage is associated with a cluster or (in KVM and VMware) a zone, and it stores the disk volumes for all the VMs running on hosts.
You can add multiple primary storage servers to a cluster or zone. At least one is required. It is typically located close to the hosts for increased performance. CloudPlatform manages the allocation of guest virtual disks to particular primary storage devices.
It is useful to set up zone-wide primary storage when you want to avoid extra data copy operations. With cluster-based primary storage, data in the primary storage is directly available only to VMs within that cluster. If a VM in a different cluster needs some of the data, it must be copied from one cluster to another, using the zone's secondary storage as an intermediate step. This operation can be unnecessarily time-consuming.
CloudPlatform is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor, including, for example:
13
Chapter 3. Cloud Infrastructure Concepts
• Dell EqualLogic™ for iSCSI
• Network Appliances filers for NFS and iSCSI
• Scale Computing for NFS If you intend to use only local disk for your installation, you can skip adding separate primary storage.

3.7. About Secondary Storage

Secondary storage stores the following:
• Templates — OS images that can be used to boot VMs and can include additional configuration information, such as installed applications
• ISO images — disc images containing data or bootable media for operating systems
• Disk volume snapshots — saved copies of VM data which can be used for data recovery or to create new templates
The items in secondary storage are available to all hosts in the scope of the secondary storage, which may be defined as per zone or per region.
CloudPlatform manages the allocation of guest virtual disks to particular primary storage devices.
To make items in secondary storage available to all hosts throughout the cloud, you can add object storage in addition to the zone-based NFS Secondary Staging Store. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere.
Object storage is provided through third-party software such as Amazon Simple Storage Service (S3) or any other object storage that supports the S3 interface. Additional third party object storages can be integrated with CloudPlatform by writing plugin software that uses the object storage plugin capability.
CloudPlatform provides some plugins which we have already written for you using this storage plugin capability. The provided plugins are for OpenStack Object Storage (Swift, swift.openstack.org1) and Amazon Simple Storage Service (S3) object storage. The S3 plugin can be used for any object storage that supports the Amazon S3 interface. When using one of these storage plugins, you configure Swift or S3 storage for the entire CloudPlatform, then set up the NFS Secondary Staging Store for each zone. The NFS storage in each zone acts as a staging area through which all templates and other secondary storage data pass before being forwarded to Swift or S3. The backing object storage acts as a cloud-wide resource, making templates and other data available to any zone in the cloud.
There is no hierarchy in the Swift storage, just one Swift container per storage object. Any secondary storage in the whole cloud can pull a container from Swift at need.

3.8. About Physical Networks

Part of adding a zone is setting up the physical network. One or (in an advanced zone) more physical networks can be associated with each zone. The network corresponds to a NIC on the hypervisor host. Each physical network can carry one or more types of network traffic. The choices of traffic
1
http://swift.openstack.org
14
Basic Zone Network Traffic Types
type for each network vary depending on whether you are creating a zone with basic networking or advanced networking.
A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks. An administrator can:
• Add/Remove/Update physical networks in a zone
• Configure VLANs on the physical network
• Configure a name so the network can be recognized by hypervisors
• Configure the service providers (firewalls, load balancers, etc.) available on a physical network
• Configure the IP addresses trunked to a physical network
• Specify what type of traffic is carried on the physical network, as well as other properties like network speed

3.8.1. Basic Zone Network Traffic Types

When basic networking is used, there can be only one physical network in the zone. That physical network carries the following traffic types:
• Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod.
• Management. When CloudPlatform’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudPlatform to perform various tasks in the cloud), and any other component that communicates directly with the CloudPlatform Management Server. You must configure the IP range for the system VMs to use.
Note
We strongly recommend the use of separate NICs for management traffic and guest traffic.
• Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudPlatform UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address. Public traffic is generated only in EIP-enabled basic zones. For information on Elastic IP, see Section 16.18, “About Elastic IP”.
• Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudPlatform uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network.
In a basic network, configuring the physical network is fairly straightforward. In most cases, you only need to configure one guest network to carry traffic that is generated by guest VMs. If you use a NetScaler load balancer and enable its elastic IP and elastic load balancing (EIP and ELB) features,
15
Chapter 3. Cloud Infrastructure Concepts
you must also configure a network to carry public traffic. CloudPlatform takes care of presenting the necessary network configuration steps to you in the UI when you add a new zone.

3.8.2. Basic Zone Guest IP Addresses

When basic networking is used, CloudPlatform will assign IP addresses in the CIDR of the pod to the guests in that pod. The administrator must add a direct IP range on the pod for this purpose. These IPs are in the same VLAN as the hosts.

3.8.3. Advanced Zone Network Traffic Types

When advanced networking is used, there can be multiple physical networks in the zone. Each physical network can carry one or more traffic types, and you need to let CloudPlatform know which type of network traffic you want each network to carry. The traffic types in an advanced zone are:
• Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. This network can be isolated or shared. In an isolated guest network, the administrator needs to reserve VLAN ranges to provide isolation for each CloudPlatform account’s network (potentially a large number of VLANs). In a shared guest network, all guest VMs share a single network.
• Management. When CloudPlatform’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudPlatform to perform various tasks in the cloud), and any other component that communicates directly with the CloudPlatform Management Server. You must configure the IP range for the system VMs to use.
• Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudPlatform UI to acquire these IPs to implement NAT between their guest network and the public network, as described in “Acquiring a New IP Address” in the Administration Guide.
• Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudPlatform uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network.
These traffic types can each be on a separate physical network, or they can be combined with certain restrictions. When you use the Add Zone wizard in the UI to create a new zone, you are guided into making only valid choices.

3.8.4. Advanced Zone Guest IP Addresses

When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired. Additionally, the administrator can reserve a part of the IP address space for non-CloudPlatform VMs and servers (see Section 16.15, “IP Reservation in
Isolated Guest Networks”).
16
Advanced Zone Public IP Addresses

3.8.5. Advanced Zone Public IP Addresses

When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired.

3.8.6. System Reserved IP Addresses

In each zone, you need to configure a range of reserved IP addresses for the management network. This network carries communication between the CloudPlatform Management Server and various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP.
The reserved IP addresses must be unique across the cloud. You cannot, for example, have a host in one zone which has the same private IP address as a host in another zone.
The hosts in a pod are assigned private IP addresses. These are typically RFC1918 addresses. The Console Proxy and Secondary Storage system VMs are also allocated private IP addresses in the CIDR of the pod that they are created in.
Make sure computing servers and Management Servers use IP addresses outside of the System Reserved IP range. For example, suppose the System Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7. CloudPlatform can use .2 to .7 for System VMs. This leaves the rest of the pod CIDR, from .8 to .254, for the Management Server and hypervisor hosts.
In all zones:
Provide private IPs for the system in each pod and provision them in CloudPlatform. For KVM and XenServer, the recommended number of private IPs per pod is one per host. If you
expect a pod to grow, add enough private IPs now to accommodate the growth.
In a zone that uses advanced networking:
When advanced networking is being used, the number of private IP addresses available in each pod varies depending on which hypervisor is running on the nodes in that pod. Citrix XenServer and KVM use link-local addresses, which in theory provide more than 65,000 private IP addresses within the address block. As the pod grows over time, this should be more than enough for any reasonable number of hosts as well as IP addresses for guest virtual routers. VMWare ESXi, by contrast uses any administrator-specified subnetting scheme, and the typical administrator provides only 255 IPs per pod. Since these are shared by physical machines, the guest virtual router, and other entities, it is possible to run out of private IPs when scaling up a pod whose nodes are running ESXi.
To ensure adequate headroom to scale private IP space in an ESXi pod that uses advanced networking, use one or more of the following techniques:
• Specify a larger CIDR block for the subnet. A subnet mask with a /20 suffix will provide more than 4,000 IP addresses.
• Create multiple pods, each with its own subnet. For example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses.
For vSphere with advanced networking, we recommend provisioning enough private IPs for your total number of customers, plus enough for the required CloudPlatform System VMs. Typically, about 10 additional IPs are required for the System VMs. For more information about System VMs, see Working with System Virtual Machines in the Administrator's Guide.
17
18
Chapter 4.
Accounts

4.1. Accounts, Users, and Domains

Accounts
An account typically represents a customer of the service provider or a department in a large organization. Multiple users can exist in an account.
Domains
Accounts are grouped by domains. Domains usually contain multiple accounts that have some logical relationship to each other and a set of delegated administrators with some authority over the domain and its subdomains. For example, a service provider with several resellers could create a domain for each reseller.
For each account created, the Cloud installation creates three different types of user accounts: root administrator, domain administrator, and user.
Users
Users are like aliases in the account. Users in the same account are not isolated from each other, but they are isolated from users in other accounts. Most installations need not surface the notion of users; they just have one user per account. The same user cannot belong to multiple accounts.
Username is unique in a domain across accounts in that domain. The same username can exist in other domains, including sub-domains. Domain name can repeat only if the full pathname from root is unique. For example, you can create root/d1, as well as root/foo/d1, and root/sales/d1.
Administrators are accounts with special privileges in the system. There may be multiple administrators in the system. Administrators can create or delete other administrators, and change the password for any user in the system.
Domain Administrators
Domain administrators can perform administrative operations for users who belong to that domain. Domain administrators do not have visibility into physical servers or other domains.
Root Administrator
Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains
Resource Ownership
Resources belong to the account, not individual users in that account. For example, billing, resource limits, and so on are maintained by the account, not the users. A user can operate on any resource in the account provided the user has privileges for that operation. The privileges are determined by the role. A root administrator can change the ownership of any virtual machine from one account to any other account by using the assignVirtualMachine API. A domain or sub-domain administrator can do the same for VMs within the domain from one account to any other account in the domain or any of its sub-domains.
19
Chapter 4. Accounts

4.1.1. Dedicating Resources to Accounts and Domains

The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain.
There are several types of dedication available:
• Explicit dedication. A zone, pod, cluster, or host is dedicated to an account or domain by the root administrator during initial deployment and configuration.
• Strict implicit dedication. A host will not be shared across multiple accounts. For example, strict implicit dedication is useful for deployment of certain types of applications, such as desktops, where no host can be shared between different accounts without violating the desktop software's terms of license.
• Preferred implicit dedication. The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure.
4.1.1.1. How to Dedicate a Zone, Cluster, Pod, or Host to an Account or
Domain
For explicit dedication: When deploying a new zone, pod, cluster, or host, the root administrator can click the Dedicated checkbox, then choose a domain or account to own the resource.
To explicitly dedicate an existing zone, pod, cluster, or host: log in as the root admin, find the resource
in the UI, and click the Dedicate button.
For implicit dedication: The administrator creates a compute service offering and in the Deployment Planner field, chooses ImplicitDedicationPlanner. Then in Planner Mode, the administrator specifies either Strict or Preferred, depending on whether it is permissible to allow some use of shared resources when dedicated resources are not available. Whenever a user creates a VM based on this service offering, it is allocated on one of the dedicated hosts.
4.1.1.2. How to Use Dedicated Hosts
To use an explicitly dedicated host, use the explicit-dedicated type of affinity group (see
Section 11.8.1, “Affinity Groups”). For example, when creating a new VM, an end user can choose to
place it on dedicated infrastructure. This operation will succeed only if some infrastructure has already been assigned as dedicated to the user's account or domain.
4.1.1.3. Behavior of Dedicated Hosts, Clusters, Pods, and Zones
The administrator can live migrate VMs away from dedicated hosts if desired, whether the destination is a host reserved for a different account/domain or a host that is shared (not dedicated to any particular account or domain). CloudPlatform will generate an alert, but the operation is allowed.
Dedicated hosts can be used in conjunction with host tags. If both a host tag and dedication are requested, the VM will be placed only on a host that meets both requirements. If there is no dedicated resource available to that user that also has the host tag requested by the user, then the VM will not deploy.
20
Loading...
+ 242 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use