In this section, you download the Photon OS 3.0 Greenplum Database OVA template from VMware Marketplace, deploy the OVA in VMware vSphere, perform a series of configuration changes to the virtual machine, and create a template from it. Finally, you verify that the virtual machine is in configured correctly by running the
The Greenplum Database OVA template is available on VMware Marketplace.
Log in and download the preferred version. Make note of the directory where the file was saved.
greenplum-db-template. Select the desired Datacenter, then click Next.
gp-virtual-externalas the Destination Network, then click Next.
gp-virtual-internalnetwork IP range, for example 192.168.1.
Based on your underlying hardware, you may need to change the default settings for CPU, memory and data disk size, which are preset to 8 vCPU, 30 GB and 16 GB respectively.
Right click the
greenplum-db-template virtual machine, then click Edit Settings.
If you want to change the memory size, click on the number on the right of Memory and enter the desired allocated memory.
If you want to change the number of CPUs, click on the number on the right of CPU and select the desired number of CPUs.
If you want to change the size of Data disk as per the VM Sizing, click on the number on the right of Hard disk 2 and enter the desired size.
Power on the
greenplum-db-template virtual machine.
gpadminwith the password
/etc/gpv/validateand ensure there are no errors.
Use the Terraform software you installed in Creating the Jumpbox Virtual Machine to generate copies of the template virtual machine you just created. The following steps will guide you to configure them based on the number of virtual machines in your environment, IP address ranges, and other settings you specify in the installation script.
Create a file named
main.tf and copy the contents described in OVA Script.
Log in to the jumpbox virtual machine as
scp to copy the
main.tf file to the jumpbox, under the
root user home directory.
Update the following variables under the Terraform variables section of the
main.tf script with the correct values for your environment. You collected the required information in the Prerequisites section.
|vsphere_user||Name of the VMware vSphere administrator level user.|
|vsphere_password||Password of the VMware vSphere administrator level user.|
|vsphere_server||The IP address or, preferably, the Fully-Qualified Domain Name (FQDN) of your vCenter server.|
|vsphere_datacenter||The name of the data center for Greenplum in your vCenter environment.|
|vsphere_compute_cluster||The name of the compute cluster for Greenplum in your data center.|
|vsphere_datastore||The name of the vSAN datastore which will contain your Greenplum data.|
|vsphere_storage_policy||The name of the storage policy defined during Setting Up VMware vSphere Storage or Setting Up VMware vSphere Encryption.|
|gp_virtual_external_ipv4_addresses||The routable IP addresses for mdw and smdw, in that order; for example:
|gp_virtual_external_ipv4_netmask||The number of bits in the netmask for
|gp_virtual_external_gateway||The gateway IP address for the
|dns_servers||The DNS servers for the
|gp_virtual_etl_bar_ipv4_cidr||The leading octets for the internal, non-routable network
$ terraform init
The output would be similar to:
Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, re-run this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary.
Verify that your Terraform configuration is correct by running:
Deploy the cluster:
Answer Yes to the following prompt:
Do you want to perform these actions? Terraform will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: yes
You can check the progress of the virtual machines creation under the Recent Tasks panel on your VMware vSphere client.
Once Terraform has completed, it generates a file named
This file must not be deleted, as it keeps a record of all the virtual machines and their states.
Terraform also uses this file when modifying any virtual machines.
VMware recommends retaining a snapshot of the jumpbox virtual machine.
The initialization of the Greenplum is fully automated in the
mdw virtual machine. Once the
mdw virtual machine is created by the Terraform script, you can log in to
root, and monitor the deployment process by running:
$ journalctl -fu gpv-mdw
When the Greenplum cluster is initialized, you should see the following message:
Dec 02 20:30:32 mdw bash: 2021-12-02 20:30:32 Starting the gpcc agents and webserver... Dec 02 20:30:35 mdw bash: 2021-12-02 20:30:35 Agent successfully started on 6/6 hosts Dec 02 20:30:35 mdw bash: 2021-12-02 20:30:35 View Greenplum Command Center at https://mdw:28080 Dec 02 20:30:35 mdw bash: Greenplum Initialization Complete!
After the initialization, the GPCC (Greenplum Command Center) web service will be available at:
https will be enabled by default.
There are two default login users for GPCC: gpmon and gpcc_user. The GPCC login user gpmon is reserved for the service to function and should not be used, while the GPCC login user
gpcc_user will be used to login to the GPCC web page.
In order to login to the web page, the password for the GPCC login user gpcc_user needs to be reset. Run
/etc/gpv/reset-gpcc-password as the
gpadmin Linux user on the
mdw machine to reset the password. There will be a prompt to type and retype the new password.
Now you can login to the web page with username
gpcc_user and the new password you just set.
Note: if you want to create a new login user for GPCC, refer to the GPCC documentation.
Now that the Greenplum Database has been deployed, follow the steps provided in Validating the Greenplum Installation to verify that Greenplum is installed correctly.