ZebClient
Zebware.comCustomer Portal
  • ZebClient Documentation
  • Product Overview
    • Introduction to ZebClient
    • Functional Overview
    • Product Components
    • Data Flows
    • Data Striping
  • USE CASES
    • ZebClient Analytics
      • Architecture
        • Data Pipeline
        • Data Storage
        • Consumption
      • Deploy a ZebClient Advanced Cluster
        • Step 0 - Setup
      • FAQ
  • Planning & Getting Started
    • How to Choose your Deployment Mode
    • Deployment Modes and Tuning
    • Performance
    • License
    • Order Your ZebClient License
    • Pricing
  • Installation
    • Types of Installations
    • Guided Installation
      • ZebClient with Azure Blob Storage
        • Defining Backend with Azure Blob Storage
        • Mounting ZebClient with Azure Blob Storage
      • ZebClient with AWS S3
        • Defining Backend with AWS S3
        • Mounting ZebClient with AWS S3
      • Mount Additional Agent Node
    • Kubernetes
      • Azure Quickstart Guide
      • ZebClient CSI
      • ZebClient Helm
      • ZebClient Terraform
    • Virtual Machines
      • Azure Installation Guide
        • Installing Using Terraform
        • Uninstalling Using Terraform
    • Checking Installation
    • Running First Test
  • Management HOW-TOS
    • Add a New Agent VM into an Existing Cluster
    • Retrieve Cluster Log Files
    • CloudFormation Deployments
      • Understanding our CloudFormation Template
      • Uninstalling Using CloudFormation
    • Command-line Interface
  • Operations & Monitoring
    • Importing Your Data
    • Inlets
      • Data from External S3 Bucket
    • System Recovery Guide
      • Restore KeyDB Backup from S3
    • Port a Deploy
    • Add Resources to a Cluster
      • Add Application Node to Existing Machine (Manually)
      • Add Application Node to Existing Machine (via zc-cli)
      • Add New Application Node
      • Add Jumpbox
    • Verifying License Validity
    • Monitoring Your ZebClient Cluster with Netdata
Powered by GitBook
On this page
  • Prerequisites
  • Clone our Terraform Repository
  • Prepare Deployment
  • Deploy
  • Post-Installation
  1. Installation
  2. Virtual Machines
  3. Azure Installation Guide

Installing Using Terraform

PreviousAzure Installation GuideNextUninstalling Using Terraform

Last updated 1 year ago

Prerequisites

  • Azure CLI: Instructions can be found .

  • Terraform: Instructions can be found .

  • Git: Instructions can be found .

Clone our Terraform Repository

Use git to clone our repository to a suitable location.

git clone https://gitlab.com/zebware/public/zebclient-vm-azure.git
cd $(pwd)/zebclient-vm-azure

Prepare Deployment

There are just a few steps to prepare for the deployment

Update Configuration

  • Copy an example tfvars of your choice from the example directory i.e. if you would like to deploy a ZebClient VM converged cluster, then copy the rhel-converged.tfvars.

cp examples/rhel-converged.tfvars terraform.tfvars
  • Update the following items:

    • prefix: Your cluster's name

    • zebclient_license_key: This can be found in the under Home -> View License Details (in license card) -> License Details

    • zebclient_mount_point (Optional): Sets the mount point name used by ZebClient when mounting in the agent nodes. Defaults to /fs/

    • ssh_source_address_prefixes: This should be set to the whitelisted IP address that can access the cluster once deployed. This can be refined later in the Azure portal

    • zebclient_cluster_mode: This variable value has already been preset according to the cluster mode. So, you shouldn't change this value. However, please refer to this to know more about available modes and their descriptions.

    • netdata_claim_token (Optional): We make use of internally. To automatically add your installation to Netdata, you can add your claim token here

    • netdata_claim_room (Optional): We make use of internally. To automatically add your installation to a Netdata war room, you can add your room claim token here

    • location: Azure region

Initialize Terraform

Run the following command to initialize Terraform

terraform init

Deploy

Run the following commands to plan and apply the deployment within the zebclient-azure directory.

terraform plan -out main.tfplan
terraform apply main.tfplan

The sample out below provides the public IP address of the management node. You can use the SSH keypair generated to SSH into this management node.

mgmt_node_public_ip_address = "20.1.170.248"
mgmt_node_admin_user = "zebclient"
mgmt_node_access_keypair = <sensitive>

In order to retrieve the SSH keypair, run the following command

terraform output -raw mgmt_node_access_keypair > keypair

Make sure to store your Key Pairs in a safe and secure location.

Post-Installation

From here you can either check the installation or jump straight to running your first tests.

You have to make sure Azure region that you choose supports availability zones, otherwise deployment will fail. Read more about Azure availability zones .

here
here
here
Zebware Customer Portal
page
Netdata
Netdata
here
Checking Installation
Running First Test