Page tree
Skip to end of metadata
Go to start of metadata

Following is the procedure to deploy a Lumeta Enterprise Command Center or Cloud Scout to Microsoft Azure.

An overview of the process is as follows:

  1. Upload a *.vhd (Virtual Hard Disk) file.
  2. Create a managed disk from it.
  3. Extend the  size of the managed disk to 500GB for a Command Center or 100GB for a Cloud Scout.
  4. Create a virutal machine (VM) on your Azure cloud and then attach the managed disk to it.
  5. Log in to the VM machine as admin, initialize the Lumeta configuration.
  6. Make the new disk space available for use.

The step-by-step procedure follows:

Prerequisite

The Lumeta Command Center or Cloud Scout  Hyper-V machine image for the latest release has has already been uploaded to Azure.

Open Azure & Browse to Lumeta VHD File

Here's how. An example with representative file names follows. Swap in the actual filenames used in your environment.

  1. Browse to Microsoft Azure. 
  2. Enter your login credentials.
  3. Select the "lumetademostorage" storage account.
    1. Browse to Storage Accounts
    2. Click lumetademostorage
  4. Select the "lumetademodisks" container.
    1. Browse to Containers
    2. Click lumetademodisks

Select the Lumeta-3.3.5.0-CmdCntr.vhd file that had been uploaded.

Create a New Managed Disk Resource

The new managed disk resource on Azure will house the Lumeta Command Center virtual machine (VM). 

  1. Click Create a Resource.
  2. Search for "Managed Disks" in the Azure Marketplace Search field. 
  3. Apply a resource group such as "Support-CmndCntr-3350-RG"
  4. Give the managed disk a name such as "Demo-CmndCntr-3350"
  5. Select the region associated with your account such as "(US) East US"
  6. Set the source type as Storage Blob
  7. Browse to and select a storage account such as "lumetademostaorage"
  8. Browse to and select your source blob.
    1. Select the "lumetademodisks" container. 
    2. Your VHD file, Lumeta-3.3.5.0-CmndCntry.vhd file displays.
  9. Set the OS type to Linux.
  10. Set the VM generation to Gen 1.
  11. Set the size to 500GiB. Lumeta recommends 100GB for Cloud Scouts and 500GB for Command Centers. 
  12. Click Review + Create. 
  13. Click Create.
  14. Managed Disk resource begins to deploy. 
  15. Once it successfully deploys, click Go to Resource
  16. The attributes of the newly created Demo-CmndCntr-3350-MD displays and its Disk State status displays as "unattached."

Create the Lumeta VM

To create a Lumeta system:

  1. If you are not there already, browse to your Demo-CmndCntr-3350-MD managed disk resource by clicking Go to Resource.
  2. Select Create VM.
  3. In the Basics tab, some of which is pre-populated . . .
    1. Name your VM (e.g., LumetaDemoVM)
    2. In Size, select B4ms for a Cloud Scout, or B8ms for Command Center
    3. For Inbound Ports, allow HTTPS and SSH
  4. In the Management tab . . .
    1. Lumeta recommends that you power on Boot Diagnostics to allow for the use of a local console
  5. In the Advanced and Tag tabs . . .
    1. Set the options as needed by your organization
  6. On the Review + Create tab . . .
    1. Click Create to generate the VM
      The LumetaDemoVM Command Center deploys in Azure and its overview page displays. If you browse to the Home > Virtual Machines page, you will see your new system listed.
      Notice your new system's public and private IP addresses listed on the right-hand side of the overview page.

Configure Your Lumeta System

Next, configure your Command Center and Cloud Scout systems.

  1. Configure your Lumeta Enterprise Command Center


  2. Configure your Lumeta Cloud Scout

    Note: The Lumeta CloudVisibility configuration GUI has been updated to allow a connection to a Cloud Scout in either AWS or Azure. See Release Notes to Lumeta 3.3.5 for an overview of the changes. 

Next Step

The next step is to configure the Linux OS to recognize the new managed disk resource you just set up on Azure. See Increasing Disk Space for the procedure.

 



  • No labels
Write a comment...