Microsoft Azure in MC

• 1: Creating an Eon Mode cluster and database in Azure in MC
• 2: Eon Mode volume configuration defaults for Azure

1 - Creating an Eon Mode cluster and database in Azure in MC

After you deploy a Management Console instance on Azure, you can provision a cluster and create an Eon Mode database.

Prerequisites

Before you begin, complete or obtain the following:

• Complete Deploying Vertica from the Azure Marketplace

• Complete the cluster and storage requirements described in Eon Mode on Azure prerequisites

• SSH public key used when deploying the MC instance

• Review Recommended Azure VM types

• Vertica credentials

• Vertica Management Console credentials

Creating the database

Complete the following steps from the Management Console:

1. Log in to the Vertica Management Console.

2. On the Management Console home page, click Eon Mode.

3. On Vertica License, select one of the following license mode options:

   • Community Edition: A free Vertica license to preview Vertica functionality. This license provides limited features. If you use a Community Edition license for your deployment, you can upgrade the license later to expand your cluster load. See Managing licenses form more information.

   • Premium Edition: Use your Vertica license. After you select this option, click Browse to locate and upload your Vertica license key file, or manually enter it in the field.

4. Click Next. On Azure Environment, supply the following information:

   • SSH Public Key: Paste the same public key used when you deployed the MC instance in the Azure Marketplace.

   • Azure Subnet: The subnet for your cluster. Select the same subnet used when you deployed the MC instance in the Azure Marketplace. If your organization requires multiple subnets for security purposes, see the Azure documentation for additional information.

   • CIDR Range: The range of IP addresses for client and SSH access. Azure requires that the last octet is 0 and the prefix is 24. For example, 10.20.30.0/24.

   • Node IP Setting: Choose Public IP - Dynamic, Public IP - Static, or Private IP. For details, see the Azure documentation.

   • Communal Storage URL: The path to a new subfolder in your existing Azure Blob storage account and container. The subfolder must not already exist.

   • Tag Azure Resources: Optional. Assign distinct, searchable metadata tags to the instances in this cluster. Many organizations use labels to organize, track responsibility, and assign costs for instances.
     To add a tag, click the slider to the right to display the Tag Name and Tag Value fields. Click Add to create the tag. Added tags are displayed below the fields. Vertica recommends that you use lowercase characters in tag fields.

5. Click Next. Database Parameters accepts identifying information about your database and OS version:

   • Database Name: The name for your new database. See Creating a database name and password for database name requirements.

   • Administrator Username: The name of the database superuser.

   • Administrator Password: The password for the database administrator user account. For details, see Password guidelines.

   • Confirm Password: Reenter the Administrator Password.

   • Vertica Version: Select the desired Vertica database version. You can select from the latest hotfix of recent Vertica releases. For each database version, you can also select the operating system. For available OS and major version options, see Supported Azure operating systems.

   • Load Sample Data: Optional. Click the slider to the right to preload your database with example clickstream data. This option is useful if you are testing features and want some preloaded data in the database to query.

6. Click Next. On Azure configuration, supply the following information:

   • Number of Nodes: The initial number of nodes for your database.

   • Number of Vertica Database Shards: Sets the number of shards in your database. Vertica suggests a number of shards automatically, based on your node count. After you set this value, you cannot change it later. The shard count must be greater than or equal to the maximum subcluster count. Be sure to allow for node growth. See Configuring your Vertica cluster for Eon Mode for recommendations.
     

   • Virtual machine (VM) size: The instance types used for the nodes. For a list of recommended instances, see Recommended Azure VM types.

   • Local Storage per Node: Customize your cluster according to your storage needs. For the Vertica default settings for each supported instance, see Eon Mode volume configuration defaults for Azure.

7. Click Next. On Review, confirm your selections. Click Edit to return to a previous section and make changes.

8. When you are satisfied with your selections, click the I accept the terms and conditions checkbox.

9. Click Create Cluster to create a Eon Mode cluster on Azure.

After creating the database

After you create the database, click Get Started to view the Fast Tasks page. To view your database, select Manage and View Your Vertica Database to go to the database Overview.

You can also view your database from the Recent Databases section of the MC home page.

For additionalinformation about managing your cluster, instances, and database using Management Console, see Managing database clusters .

2 - Eon Mode volume configuration defaults for Azure

When you provision an Eon Mode database cluster, Management Console (MC) configures separate volumes for the depot, catalog, and temp directories. The specific volumes and sizes that Management Console configures vary depending on the Azure instance type that you select when provisioning the cluster.

MC follows these rules when allocating resources for these directories for an Eon Mode database cluster:

• Depot: Use Standard or Premium LRS to ensure the data is durable.

• Catalog: Use Standard or Premium LRS to ensure the data is durable.

• Temp: Allocate instance store if available with the selected instance type. Otherwise, allocate Standard or Premium LRS volumes.

If NVMe or Local SSD are displayed as volume types for an instance, there are no other choices. You must choose a different VM to change the volume type.

For details about each disk type, see the Azure documentation.

Storage optimized

Memory optimized