Deploy Vertica from the Azure Marketplace
Deploy Vertica in the Microsoft Azure Cloud using the Vertica Data Warehouse entry in the Azure Marketplace. Vertica provides the following deployment options:
-
Eon Mode: Deploy a Management Console (MC) instance, and then provision and create an Eon Mode database from the MC. For cluster and storage requirements, see Eon Mode on Azure prerequisites.
-
Enterprise Mode: Deploy a four-node Enterprise Mode database comprised of one MC instance and three database nodes. This requires an Azure subscription with a minimum of 12 cores for the Vertica Marketplace solution.
The Enterprise Mode deployment uses the MC primarily as a monitoring tool. For example, you cannot provision and create a database with an Enterprise Mode MC. For information about creating and managing an Enterprise Mode database, see Create a database using administration tools.
Create a deployment
Eon Mode and Enterprise Mode require much of the same information for deployment. Any information that is not required for both deployment types is clearly marked.
1. Select the deployment type
-
Sign in to your Microsoft Azure account. From the Home screen, select Create a resource under Azure services.
-
Search for Vertica Data Warehouse and select it from the search results.
-
On the Vertica Data Warehouse page, select one of the following:
-
To deploy an MC instance that can manage an Eon Mode database, select Vertica Data Warehouse, Eon BYOL.
-
To deploy an Enterprise Mode database, select Vertica Data Warehouse, Enterprise BYOL.
-
-
On the next screen, select Create.
After you select your deployment type, the Basics tab on the Create Vertica Data Warehouse page displays.
2. Add project and instance details on the basics tab
Provide the following information in the Project details and Instance details sections:
-
Subscription: Azure bills this subscription for the cluster resources.
-
Resource group: The location to save all of the Azure resources. Create a new resource group or choose an existing one from the dropdown list.
-
Region: The location where the virtual machine running your MC instance is deployed.
-
VerticaManagement ConsoleUser: Eon Mode only. The administrator username for the MC.
-
SSH public key for OS Access: Provide the SSH public key associated with the Vertica User, for command line access to the virtual machine.
-
Password for MC Access: Enter a password to log in to Management Console. Note that Management Console requires that you change your password after the initial login.
-
Confirm password: Reenter the value you entered in Password for MC Access.
-
Select Next: Virtual Machine Settings >.
3. Select virtual machine settings
Provide the following information on the Virtual Machine Settings tab:
-
Management Console VM size: Select Change size to customize the VM settings or select the default. For a list of VM types recommended by use case, see Recommended Azure VM types and operating systems.
-
Storage account of Eon DB: Eon Mode only. The storage account associated with the database deployment.
-
Number of Vertica Cluster nodes: Enterprise Mode only. The number of nodes to deploy in the cluster, in addition to the MC instance.
The Community Edition (CE) license is automatically applied to the cluster. This license is limited to 1 TB of RAW data 3 Vertica nodes. If you select more than 3 nodes with a CE license, the initial database is created on the first 3 nodes. For information about upgrading your license, see Managing licenses. -
Vertica Node VM size: Enterprise Mode only. Select the VM type to deploy in your cluster. Use the default or select Change size to customize the VM settings. For a list of VM types recommended by use case, see Recommended Azure VM types and operating systems.
-
Total RAW storage per node: Enterprise Mode only. Select the amount of storage per node from the dropdown list. Each VM has a set of premium data disks that are configured and presented as a single storage location.
-
Select Next: Network Settings >.
4. Select network settings
Provide the following information on the Network Settings tab:
-
Virtual Network: The virtual network that hosts the Vertica cluster. Create a new virtual network or select an existing one from the dropdown list.
If you select an existing virtual network, Vertica recommends that you already created a subnet to use for the deployment. -
First subnet: The subnet for the associated Virtual Network. Create a new subnet or select an existing one from the dropdown list.
-
Public IP Address Resource Name: Each VM is configured with a publicly accessible IP address. This field allows you to specify the resource name for those IP addresses, and whether they are static or dynamic. The first public IP address resource is created exactly as entered, and associated with the VerticaManagement Console. Azure appends a number from 1 to 16 to the resource name for each additional Vertica cluster node created. This number associates each VM with a resource.
-
Domain Name Label for Management Console: Because each VM has a public IP address, each node requires a DNS name. Enter a prefix for the name. The first DNS name is created exactly as entered, and associated with the VerticaManagement Console. Azure appends a number from 1 to 16 to the DNS name for each Vertica cluster node created. That number associates each VM with a resource. Azure adds the remaining part of the fully qualified domain name based on the location where you created the cluster.
-
Select Next: Review + create >.
5. Verify on review + create
As the Review + create page loads, Azure validates your settings. After it passes validation, review your settings. When you are satisfied with your selections, select Create.
Access the MC after deployment
After your resources are successfully deployed, you are brought to the Overview page on Home > resources-name > Deployments. You must retrieve your Management Console IP address and username to log in.
-
From the Overview page, select Outputs in the left navigation.
-
Copy the Vertica Management Console URL and Vertica Management Console user name*.
-
Paste the Vertica Management Console URL in the browser address bar and press Enter.
-
Depending on your browser, you might receive a warning of a security risk. If you receive the warning, select the Advanced button and follow the browsers instructions to proceed to the Management Console.
-
On the VerticaManagement Console log in page, paste the Vertica Management Console user name, and enter the Password for MC Access that you entered on Basics > Project details when you were deploying your MC instance.
Delete a resource group
For details about the Azure Resource Manager and deleting a resource group, see the Azure documentation.