Setup: Supported GCP machine types

Mon, 01 Jan 0001 00:00:00 +0000

Vertica Analytic Database supports a range of machine types, each optimized for different workloads. When you deploy your Vertica Analytic Database cluster to the Google Cloud Platform (GCP), different machine types are available depending on how you provision your database.

Note

Some machine types are not available across all regions.

The sections below list the GCP machine types that Vertica supports for Vertica cluster hosts, and for use in Management Console. For details on the configuration of the machine type options, see the Google Cloud documentation's Machine types page.

Machine types available for MC hosts

Vertica supports all N1, N2, E2, M1, M2, and C2 machine types to deploy an instance for running the Vertica Management Console.

Tip

In most cases, 8 vCPUs are sufficient when selecting a machine type for running the Management Console.

Machine types available for Vertica database cluster hosts

Vertica supports all N1, N2, E2, M1, M2, and C2 machine types to deploy cluster hosts.

Machine types for Vertica database cluster hosts provisioned from MC

The table below lists the GCP machine types that Vertica supports when you provision your cluster from Management Console.

Machine Type	Machine Name
N1 standard	n1-standard-16 n1-standard-32 n1-standard-64
N1 high-memory	n1-highmem-16 n1-highmem-32 n1-highmem-64
N2 standard	n2-standard-16 n2-standard-32 n2-standard-48 n2-standard-64
N2 high-memory	n2-highmem-16 n2-highmem-32 n2-highmem-48 n2-highmem-64

Setup: Deploy Vertica from the Google cloud marketplace

Mon, 01 Jan 0001 00:00:00 +0000

The Vertica entries in the Google Cloud Launcher Marketplace let you quickly deploy a Vertica cluster in the Google Cloud Platform (GCP). Currently, three entries let you select the database mode and the license you want to use:

The Enterprise Mode launcher deploys a Vertica database with 3 or more nodes, plus an additional VM running the Management Console (MC). See Deploy an Enterprise Mode database in GCP from the marketplace for more information.
The Eon Mode BYOL (bring your own license) launcher deploys a single instance running the MC. You use this MC instance to deploy a Vertica database running on Eon Mode. This database has a community license applied to it initially. You can later upgrade it to a license you have obtained from Vertica. See Deploy an MC instance in GCP for Eon Mode for more information.
The Eon Mode BTH (by the hour) launcher also deploys a single instance running the MC that you use to deploy a database. This database has a by-the-hour license applied to it. Instead of paying for a license up front, you pay an hourly fee that covers both Vertica and running your instances. The BTH license is automatically applied to all clusters you create using a BTH MC instance. See Deploy an MC instance in GCP for Eon Mode for more information. If you choose, you can upgrade this hourly license to a longer-term license you purchase from Vertica. To move a BTH cluster to a BYOL license, follow the instructions in Moving a cloud installation from by the hour (BTH) to bring your own license (BYOL).

Note

Vertica clusters that use IPv6 to identify hosts have not been tested on GCP. Vertica recommends you use IPv4 addresses to identify the hosts in your cluster on GCP.

Setup: Manually deploy an Enterprise Mode database on GCP

Mon, 01 Jan 0001 00:00:00 +0000

Before you create your Vertica cluster in Google Cloud Platform (GCP) using manual steps, you must create a virtual machine (VM) instance from the Compute Engine section of GCP.

Configure and launch a new instance

All VM instances that you create should be launched in the same virtual public cloud (VPC).

To configure and launch a new VM instance, follow these instructions:

From within the Compute Engine section of GCP, from the menu on the left-hand site of the screen, select VM Instances.

GCP displays all the VM instances that you have created so far.
Click CREATE INSTANCE.
Enter a name for the new instance.
Select the zone where you plan to deploy the instance.

GCP breaks its cloud data centers down by regions and zones. Regions are a collection of zones that are all in the same geographical location. Zones are collections of compute resources, which vary from zone to zone. Always pick the zone in your designated region that supports the latest Intel CPUs.

For a complete listing of regions and zones, including supported processors, see Regions and Zones.
Select a machine type.

GCE offers many different types of VM instances. For best results, only deploy Vertica on VM instances with 8 vCPus or more and at least 30 GB of RAM.
Select the boot disk (image).

You create VM instances from a public or custom image. If you are starting with Vertica in GCP for the first time, select either the CentOS 7 or RHEL 7 public image. Those images have been tested thoroughly with Vertica.

For more information about deploying a VM instance, see Creating and Starting an Instance.

After you have configured the VM instance to be used as a Vertica cluster node, GCP allows you to convert that instance into a custom image. Doing so allows you to deploy multiple versions of that VM instance; each VM instance is identical except for the node name and IP address.

For more information about creating a custom image, see Creating, Deleting, and Deprecating Custom Images.

Connect to a virtual machine

Before you can connect to any of the VMs you created, you must first identify the external IP address. The VM instance section of GCP contains a list of all currently deployed VMs and their associated external IP addresses.

Connect to your VM

To connect to your VM, complete the following tasks:

Connect to your VM using SSH with the external IP address you created in the configuration steps.
Authenticate using the credentials and SSH key that you provided to your GCP account upon creation.

Connect to other VMs

To connect to other virtual machines in your virtual network:

Use SSH to connect to your publicly connected VM.
Use SSH again from that VM to connect through the private IP addresses of your other VMs.

Because GCP forces the use of private key authentication, you may need to move your key file to the root directory of your publicly connected VM. Then, use SSH to connect to other VMs in your virtual network.

Prepare the virtual machines

After you create your VMs, you need to prepare them for cluster formation.

Add the Vertica license and private key

Prepare your nodes by adding your private key (if you are using one) to each node and to your Vertica license. The following steps assume that the initial user you configured is the DBADMIN user:

As the DBADMIN user, copy your private key file from where you saved it locally onto your primary node.

Depending upon the procedure you use to copy the file, the permissions on the file may change. If permissions change, the install_vertica script fails with a message similar to the following:
```
Failed Login Validation 10.0.2.158, cannot resolve or connect to host as root.
```
If you see the previous failure message, enter the following command to correct permissions on your private key file:
```
$ chmod 600 /<name-of-key>.pem
```
Copy your Vertica license to your primary VM. Save it in your home directory or other known location.

Install software dependencies for Vertica on GCP

In addition to the Vertica standard Package dependencies, as the root user, you must install the following packages before you install Vertica:

pstack
mcelog
sysstat
dialog

Configure storage

For best disk performance in GCP, Vertica recommends customers use SSD persistent storage, configured to at least 2TB (2000 GB) in size. Disk performance is directly tied to the disk size in GCP. 2000 GBs (2TB) is the minimum disk size for SSD persistent disks that allows maximum throughput.

Caution

Do not store your information on the root volume, especially in your data and catalog directories. Storing information on the root volume may result in data loss.

When configuring your storage, make sure to use a supported file system. See for details.

Create a swap file

In addition to storage volumes to store your data, Vertica requires a swap volume or swap file for the setup script to complete.

Create a swap file or swap volume of at least 2 GB. The following steps show how to create a swap file within Vertica on GCP:

Install the devnull and swapfile files:

$ install -o root -g root -m 0600 /dev/null /swapfile

Create the swap file:

$ dd if=/dev/zero of=/swapfile bs=1024 count=2048k

Prepare the swap file using mkswap:
```
$ mkswap /swapfile
```
Use swapon to instruct Linux to swap on the swap file:
```
$ swapon /swapfile
```

Persist the swapfile in FSTAB:

$ echo "/swapfile swap swap auto 0 0" >> /etc/fstab

Repeat the volume attachment, combination, and swap file creation procedures for each VM in your cluster.

Download Vertica

To download the Vertica server appropriate for your operating system and license type, follow the steps in described in Download and install the Vertica server package.

After you complete the download and extraction, use the install_vertica script to form a cluster and install the Vertica database software, as described in the next section.

Form a cluster and install Vertica

Use the install_vertica script to combine two or more individual VMs to form a cluster and install your Vertica database.

Before you run the install_vertica script, follow these steps:

Check the VM Instances page of the Compute Engine section on GCP to locate a list of current VMs and their associated internal IP addresses.
Identify your storage location on your VMs. The installer assumes that you have mounted your storage to /home/dbadmin. To specify another location, use the --data-dir argument.

Caution

Do not store your data on the root drive.

The following steps show how to combine virtual machines (VMs) into a cluster using the install_vertica script:

While connected to your primary node, construct the following command to combine your nodes into a cluster.

$ sudo /opt/vertica/sbin/install_vertica --hosts 10.2.0.164,10.2.0.165,10.2.0.166 --dba-user-password-disabled --point-to-point --data-dir /vertica/data --ssh-identity ~/.pem --license

Substitute the IP addresses for your VMs, and include your root key file name, if applicable.
Include the --point-to-point parameter to configure spread to use direct point-to-point communication among all Vertica nodes, as required for clusters on GCP when installing or updating Vertica.
After you combine your nodes, to reduce security risks, keep your key file in a secure place—separate from your cluster—and delete your on-cluster key with the shred command:
```
$ shred examplekey.pem
```

Important

You need your key file to perform future Vertica updates.

For complete information about the install_vertica script and its parameters, see Install Vertica with the installation script.

After your cluster is up and running

Now that your cluster is configured and running, and Vertica is running, take these steps:

Create a database. See Creating a database for details.
When you installed Vertica, a database administrator user was created with the DBADMIN role (usually named dbadmin). Use this account to create and start a database.
See Configuring the database for important database configuration steps.

OpenText Analytics Database 26.2.x – Vertica on Google Cloud Platform

Setup: Supported GCP machine types

Note

Machine types available for MC hosts

Tip

Machine types available for Vertica database cluster hosts

Machine types for Vertica database cluster hosts provisioned from MC

Setup: Deploy Vertica from the Google cloud marketplace

Note

Setup: Manually deploy an Enterprise Mode database on GCP

Configure and launch a new instance

Connect to a virtual machine

Connect to your VM

Connect to other VMs

Prepare the virtual machines

Add the Vertica license and private key

Install software dependencies for Vertica on GCP

Configure storage

Caution

Create a swap file

Download Vertica

Form a cluster and install Vertica

Caution

Important

After your cluster is up and running