VCP-IaaS Study Notes: Section 1.1

This is Section 1.1 in the VCP-IaaS blueprint Guide 1.2. The rest of the (completed) sections can be found here.

  • Identify required vCloud components and pre-requisites for installation
    • Components (Figure 1.1)
      • vCloud Director Cell or Cells
        • vCloud Director Database
      • vCenter and ESXi hosts
        • vCenter Database
      • vShield Manager
        • Connected to each vCenter.

    • Prerequisites vCloud Director
      • Networks to be used as external networks should be available to all hosts for the vCloud Director to use.
      • DVS must be used for cross-fencing and network pool allocation.
      • Automated DRS must be configured.
      • vCenter 5.0 cluster can not use storage DRS.
      • vCenter server must trust their ESXi hosts. (certificates)
      • Need to have the appropriate licences 🙂
      • Supported OS:
        • Red Hat Enterprise 5 (64bit), U4,U5 or U6.
      • 950Mb for installation files
      • 1 GB min memory, 2 GB recommended.
      • MSSQL and Oracle supported as databases.
      • SSL certificates for each vCloud network interface (http and consoleproxy)
    • Prerequisites vShield
      • 8GB Memory
      • Disk space – 8GB vShield Manager, 5GB vShield App per ESX host, 200mb per vShield Edge.
      • 2x Gigabit NICs on ESX hosts for all vShield components.
  • Describe installation order of vCloud components
    • Install vCenter and ESXi hosts
      • Configure a cluster with a DVS, Automatic DRS, and External DVS portgroup for external networks.
    • Setup vShield Manager
    • Setup the vCloud Database
    • Install vCloud Director instances.
    • Verify DNS resolution.
    • Verify NTP between vCloud Director Cells and databases
    • Open necessary ports
  • Explain the purpose and use case of each vCloud component
  • VMware vCloud Director (vCD)
  • Cloud Coordinator and UI. Abstracts vSphere resources.
  • vCloud API
    • API used to programmatically interact with a vCloud
  • VMware vSphere
    • Underlying foundation of virtualized resources.
  • VMware vShield
    • Provides network security services
  • VMware vCenter Chargeback
    • Optional component that provides resource metering and reporting to facilitate resource showback/chargeback
  • VMware vCenter Orchestrator
    • Optional component that facilitates orchestration at the vCloud API and vSphere levels.
  • VMware vCloud Request Manager
    • Optional component that provides provisioning request and approval workflows, software license tracking, and policy-based cloud partitioning.
  • VMware vCloud Connector
    • Optional component to facilitate transfer of a powered-off vApp in OVF format from a local vCloud or vSphere to a remote vCloud

  • Create a SysPrep package
    • You will need access to the Sysprep binary files from Windows.
  • Copy the Sysprep binary files for each operating system to a convenient location on a vCloud Director server host.

Each operating system requires its own folder. NOTE Folder names are case-sensitive.

Guest OS Copy Destination
Windows 2000 SysprepBinariesDirectory /win2000
Windows 2003 (32-bit) SysprepBinariesDirectory /win2k3
Windows 2003 (64-bit)  SysprepBinariesDirectory   /win2k3_64
Windows XP (32-bit) SysprepBinariesDirectory /winxp
Windows XP (64-bit) SysprepBinariesDirectory /winxp_64

SysprepBinariesDirectory represents a location you choose to which to copy the binaries.

  • Run the /opt/vmware/cloud-director/deploymentPackageCreator/ SysprepBinariesDirectory command.
  • For example, /opt/vmware/clouddirector/deploymentPackageCreator/ /root/MySysprepFiles.
  • Use the service vmware-vcd restart command to restart the cloud cell.
  •  If you have multiple cloud cells, copy the package and properties file to all cloud cells.
  • scp /opt/vmware/cloud-director/guestcustomization/
  • /opt/vmware/clouddirector/guestcustomization/
  • root@next_cell_IP:/opt/vmware/cloud-director/guestcustomization
  •  Restart each cloud cell to which you copy the files.
  • Install vCloud Director
    • Download installation package to target server
    • Verify checksum
      • md5sum -c checksum-value installation-file
    • Ensure installation file is executable
      • chmod u+x installation-file
    • Run the installation file in console:
      • ./installation-file
    • Press N to run the configuration script later.
    • Setup a NFS volume to be used as temporary storage for uploads and downloads
      • Root needs write permission.
      • The path is /opt/vmware/vcloud-director/data/transfer
      • Need several hundred GB volume.
      • To mount a NFS drive in Red Hat
        • Edit /etc/fstab and add this line
        • IP_of_NFS_Server:/path/mount /opt/vmware/vcloud-director/data/transfernfs   intr   0 0
        • Save your /etc/fstab.
        • Run this command: mount-a
        • Try writing on the newly mounted NFS volume. (vi test, :wq!)
    • Run the configure script again – /opt/vmware/vcloud-director/bin/configure
      • At this time you will need to have your database and SSL certificates ready.
      • Select which IP address will be used for HTTP and Console Proxy.
      • Specify the full path to the Java keystore file. (eg. opt/keystore/certificates.ks)
      • Type keystore and certificate password.
      • Configure audit message handling – send to a syslog server & vCloud database or just the vCloud database.
      • Specify database type. SQL or Oracle.
        • Enter IP address of database.
        • Enter port to listen to. (1521 for Oracle, and 1433 SQL)
        • Type the database service name
          • Note, in SQL don’t change the default value.
        • Type username and password.
    • Choose to start the services.
  • Install vShield Manager
    • Obtain the vShield Manager OVA file.
    • Install the Virtual Appliance.
    • Configure Network settings
      • Go to Console – login as admin/default
      • Go to Enabled mode – command: enable.
      • Run the Setup wizard – command: setup.
    • Go to IP address of appliance in a browser
      • Log in with user admin/default.
      • Change password
    • Sync with vCenter
      • Settings and Reports -> Configuration -> vCenter
    • Register vShield Manager plug-in with vSphere Client
      • Settings and Reports -> Configuration -> vSphere Plug-in
  • Install vCenter Chargeback
    • Pre-req:
      • Ports HTTP-8080,Load-balancer-8009 and HTTPS-443 need to be free.
      • Static IP.
      • Installation files need to be run locally.
      • 2GHz CPU,4GB RAM,2-3GB Disk space, 10-100-1000 ethernet
      • SQL or Oracle 10g
      • Open ports in Windows firewall if needed.
    • Run vCenter-CB.exe
      • Next->Accept EULA->Choose path for installation->Enter database info->Enter load-balancer related info->Install vCenter Chargeback Server-> Enter username and pw for vCenter Chargeback Manager administrative account->Select data collectors that you want to install->If installing vCloud data collector enter database info->Press install ->Generate my own SSL certificate.
  • Install vCloud Connector
    • Download vCC Server virtual appliance and the vCC Node virtual appliance from
    • You can install the server&node appliance in a vSphere environment or an vCloud environment (1.0,1.0.1,1.5).
    • vSphere Environment
      • Import the OVA and assign an IP.
    • vCloud Environment
      • Make the appliances as vApp Template in the vCloud
      • Create the vCloud Connector Server/Node from the template
      • Setup NAT mapping for the Server or Node
  • Configure vCloud Director network connections
    • You need two IP addresses. One for HTTP and one for the ConsoleProxy.
    • When you run the configuration script it asks you what IP you will be using for each.
    • Then you need to point to the SSL certificate keystore.
  • Configure vCloud Director database settings
    • In the same configuration script you select what kind of database will be used: SQL or Oracle
    • Host IP->Port->Database Service name->Database user and password
  • Troubleshoot basic installation issues
    • Ive had trouble with the database connection when running the configure script. Do not change the default name of the SQL Database Service Name.
    • Other than that I can’t think of any… Please comment if you had any problems with basic installation and I will gladly add it this section.

About larushjartar
VMware Specialist and IBM Technician.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: