This topic describes the steps required to deploy a BMC Discovery virtual appliance (VA) into the Microsoft Azure cloud. It contains the following sections:
To deploy a BMC Discovery VA into Microsoft Azure
Convert the Discovery VMDK file to VHD
Microsoft Azure requires the disk image to be in VHD format, rather than the VMDK format in which the BMC Discovery VA is supplied. This procedure assumes you have downloaded a BMC Discovery VA from https://www.bmc.com/available/epd.html
- Download the Microsoft Virtual Machine Converter from:
and install it on a Windows computer.
- Extract the BMC Discovery virtual appliance zip file to a temporary location.
Open a PowerShell prompt as administrator and run:
Convert the VMDK file to VHD. In this command you should replace the file locations and names appropriate to the computer you are using and the version of BMC Discovery that you have downloaded. Enter:
Upload the VHD file to Microsoft Azure
This procedure uploads the VHD file to a new Storage Account and Resource Group in Microsoft Azure.
- Open a PowerShell prompt as administrator.
Install the PowerShell modules for Microsoft Azure. At the PowerShell prompt, run:
For more information, see https://docs.microsoft.com/en-us/powershell/azure/install-azurerm-ps. Depending on the version of Windows that you are using, you might need to install an updated version of PowerShell.
Log in to your Microsoft Azure account. Enter:
Set some variables to be used in the following commands, changing the region as required. The Storage Account name must be unique in Azure. Enter:
Create a new Resource Group. Enter:
Create a new Storage Account. Enter:
Set a variable for the upload destination. Replace the version number in the
.vhdfile name to match the version of BMC Discovery that you are uploading. Enter:
Upload the VHD file. Replace the path to the
.vhdfile as required. Enter:
Create an Azure image from the uploaded VHD
The following steps create an Azure Image that can be used to deploy BMC Discovery VM instances.
Create a new image configuration. Enter:
Configure the OS disk for the image. Enter:
Create the Image. Replace the Image name and Resource Group name values as required.
Create a new VM from the Azure image
The following steps create an Azure Virtual Machine from the image.
- In the Azure Portal, navigate to the upload Resource Group
DiscoveryUploadand locate the image created in the previous steps.
- Click through to the image and click Create VM.
- Set values as required for the VM. Specify a username and use password authentication. The username and password are required by Microsoft Azure for the deployment, but the user is not created. Any valid values for the username and password can be used.
- Set a size for the VM according to your requirements.
Set the Networking values for the VM.
It is safest to not configure a Public IP address at this point.
However, If you do choose to have a Public IP address for the machine, you should modify the default inbound security rule to restrict SSH access appropriately, for example, restricted to the IP address from which you plan to access it.
- Set any other options as required. The storage for the VM is set as Managed Disk and cannot be changed.
Proceed to create the VM.
The deployment job shows as failed unless the Azure Virtual Machine Agent is installed on the BMC Discovery VM before the deployment timeout period (approximately 30 minutes). This failure is not a problem, and after installing the agent in the following section the VM is reported to be "Running OK".
Install the Azure Virtual Machine Agent
The following steps install the Azure Virtual Machine Agent.
- Determine the public or private IP address for the VM by viewing it in the Azure Portal. The type of IP you use depends on how you configured networking for the VM. If you are using the private IP, you must use another machine on the same network to connect to the VM using SSH.
- Using SSH, connect to the Discovery appliance as the tideway user and log in with the default password
tidewayuser. On the first login, you are forced to change the password. Reconnect after you have changed the password.
Change to the root user and specify a login shell.
Ensure that you make the root user's shell a login shell. The login shell prevents the root user inheriting the tideway user's environment. If you do not use a login shell, the Azure Virtual Machine Agent is installed in the wrong location and will fail to start.
and enter the default root password
tidewayroot. You are prompted to set a new password for the root user.
Run the following commands to install pip, which is required for the agent installation:
Run the following commands to download and install the Azure agent:
Configure the agent to start at boot by running this command:
Start the agent:
Ensure the agent service is running:
To enable Azure diagnostics to capture the console output, the console should be set to serial. Edit
/boot/grub/menu.lstand add the following to the line that starts
If the VM deployment job failed because the agent was not installed within the timeout period, and the VM still shows as failed after some time has passed, restart the VM from the Azure Portal. This should clear the failed state, and show it as running.