Installation Guide

Table 13 Important CloudSystem configuration information (continued)
Why it mattersImportant to know
The vCenter Server user that is stored in the base appliance
by csstart does not need full administrator privileges
The vCenter Server user running csstart only needs the
top level privileges for Datastore, Network, Resource, and
Virtual machine. on the Windows server running vCenter Server. The user
does not need full access to vCenter Server. Allocating the
lowest allowed level of privileges optimizes data center
security.
When installing with Windows, you should run the
csstart setup assistant from a directory with restricted
access in order to protect this file.
(Step 2)
The deployer.conf file contains confidential information,
such as passwords, and should be kept secure.
The automatic placement of CloudSystem management
hypervisors in the cluster may overload some hypervisors
if DRS is not in use.
DRS is recommended for use in a cluster that is also hosting
virtual machines other than the CloudSystem management
hypervisors.
csstart creates the virtual appliances in the first host of
a non-DRS cluster. There is no way to select a specific host.
If you use a single management host that is not part of a
DRS cluster, then make sure you have enough resources
to host all CloudSystem virtual appliances.
All hosts in the non-DRS cluster need to be large enough
to support all CloudSystem virtual appliances.
You must have sufficient space for the virtual appliance
boot disks, as well as the Glance disk, or the installation
process will not be able to complete.
(Step 3)
When you run the csstart setup assistant, you will be
asked for a Glance disk size. The installation creates a
Glance disk on the same datastore where the base
appliance template is stored.
See Formula to determine the storage requirements for the
management hypervisor (page 12) for sizing calculations.
Return to procedure
Instances are started in the same datastore that contains
the OVA. If multiple OVAs with the same name are stored
Each OVA in the datastore needs to have a unique name.
You cannot use separate folders in the datastore.
in the datastore, csstart will not know which one to use
to create the instance.
The Enterprise installation will fail if the Enterprise OVA is
not included in the same datastore as the other virtual
appliance images.
The Enterprise image must be deployed in the same
datastore as the other CloudSystem virtual appliance
images.
In order to speed up virtual machine boot times and save
disk space, csstart does not make a full copy of the
Do not move or delete images, or rename the images, after
you create the base appliance.
image. Changing the name or location of the image
disrupts the operation of the shared copy encoded by
csstart.
Prerequisites
• The management hypervisor network infrastructure is in place.
See Create the ESX management hypervisor and configure the network infrastructure (page 27).
• You have administrator privileges to log in to vCenter Server.
• One large datastore is created with approximately 2 TB to support the virtual appliance boot
drives plus additional storage for OpenStack Glance images.
See Formula to determine the storage requirements for the management hypervisor (page 12).
• The management hypervisor has connectivity to the HP 3PAR storage system. This is required
if you are using block storage for instances.
See HP 3PAR StoreServ Storage documents (page 60).
30 Installing CloudSystem on an ESX cluster