Deploying LogLogic EVA on Microsoft Azure

To deploy LogLogic EVA on Microsoft Azure, create a Microsoft Azure image. Then create a virtual machine and connect to it via SSH and access LogLogic EVA.

For characteristics and limitations of LogLogic EVA on Microsoft Azure, see Introduction to TIBCO LogLogic® Enterprise Virtual Appliance.

Prerequisites

Ensure that you meet the following requirements:
  • On LogLogic EVA, enable the feature to expand storage by running the following CLI command: 
    > system storage_growth enable
    While deploying LogLogic EVA, if you select a storage type with additional storage, only the primary storage is accessible after deployment is complete. The additional storage is accessible on the instance only if the feature to expand local storage is enabled.
  • Download the archive file TIB_logeva_<EVA-version>_azure_vm_vhd.zip from the TIBCO eDelivery website and extract its contents: eva_azure_vm-vhd-<EVA-version>.vhd
  • Ensure that you have access to the following on Azure:
    • A Microsoft Azure account
    • A subscription
    • A resource group and storage account
    • A container with access level as private
    • A virtual network and subnet
    • A network security group

    See Microsoft Azure documentation for steps to create these components: resource groups, storage accounts, and containers.

  • Ensure that Microsoft Azure CLI is in working state by running a simple command, for example, find out the CLI version: 
    az --version
    For more information, see Azure CLI documentation.
  • (Optional) For GUI access to Microsoft Azure storage accounts, download Storage Explorer from the Microsoft Azure website.
    Note: When you obtain third-party software or services, it is your responsibility to ensure you understand the license terms associated with such third-party software or services and comply with such terms.
In the following procedure, you can choose to follow either the GUI or the CLI procedure as per your setup and requirements.

Procedure

  1. Upload the .vhd file to an Azure storage blob container:
    • Using the GUI: See Upload VHD using Storage Explorer in the Microsoft documentation.
    • Using the CLI: Run the following command. 
      az storage blob upload -c <container_name> \
--file <vhd_file_name> --type page -n <vhd_file_name_in_container> \
--account-name <storage_account_name> --account-key <storage_account_key>
    The result is displayed in JSON format. 
    Finished[#############################################################]  100.0000%
    {
      "etag": "\"0x8D74B70F3AB32FE\"",
      "lastModified": "2019-10-07T21:54:39+00:00"
    }
  2. Create an image using the .vhd file:
    • Using the GUI: In the Images section, click Add and enter the following parameters:
      Parameter Value
      Resource Group name Enter the resource group name that includes the storage account
      OS type Linux
      VM Generation Gen 1
    • Using the CLI: Run the following command. 
      az image create --name <name_for_image> \
--resource-group <resource_group_name> \
--source <URL_of_VHD_file> --os-type Linux
  3. Create a virtual machine by using the GUI or CLI.
    • Using the GUI: See Create a Linux virtual machine in the Azure portal in the Microsoft documentation.
    • Using the CLI: Run the following command. 
      az vm create -n <VM_name> -g <resource_group_name> \
--image <image_name> --size Standard_D16s_v3 \
--admin-username azureuser --generate-ssh-keys \
--storage-sku Standard_LRS \
--vnet-name <vnet_name> --subnet <subnet_name> \
--public-ip-address-allocation dynamic \
--nsg <network_security_gateway_name> \
--tags 'CreatedBy=<your_name>'
      Note: To use a key other than the default one in the .ssh folder, use the --ssh-key-values option and provide a space-separated list of SSH public keys or public key file paths.
    By default, a 60 GB disk is available in LogLogic EVA on Microsoft Azure. To meet the minimum requirement of 500 GB, you must attach an additional storage of at least 440 GB either while creating a virtual machine or after deploying LogLogic EVA. To use the additional storage, you must enable the storage growth feature in LogLogic EVA after deployment. Otherwise, you can see and use only the primary disk storage through LogLogic EVA, and not the additional storage.
  4. Establish an SSH connection to the virtual machine by running the following command: 
    $ ssh azureuser@<IP_address> -i <path_to_SSH_key>
    where <IP_address> is the IP address of the virtual machine where you deployed LogLogic EVA. It is displayed in the Public IP address field in the following section:

    Virtual Machines > <virtual_machine_name> > Overview

What to do next

After deploying log in to LogLogic EVA on Microsoft Azure from the GUI or the CLI:
  • From the CLI: Switch to the toor user by running the following command: 
    > sudo -u toor -s
  • From the GUI: Open https://<IP_address> in a browser, where <IP_address> is the IP address of the virtual machine where you deployed LogLogic EVA.
    Attention: On the Administration > Network Settings page, keep all settings as is. Changing some settings might cause the instance to be inaccessible.
Then perform the following additional configurations:
  • While deploying LogLogic EVA, if you selected a machine type that has multiple storage disks, or if you want to further expand the local storage after deployment, then you must enable the storage growth feature in LogLogic EVA. Otherwise, you can see and use only the primary disk through LogLogic EVA, and not the additional disks. Perform the steps at Expanding the Local Storage of LogLogic EVA.
  • (Optional) To connect LogLogic EVA to a large number of devices, perform the steps at Configuring LogLogic EVA for Large Number of Devices.