CloudLens vLM on Azure

Build the Keysight CloudLens Virtual License Manager (vLM) as an Azure managed image and deploy it in Azure Commercial or Azure Government, with one interactive command. The vLM is the network license server that standalone Virtual Packet Brokers (vPBs) pull their capacity licenses from.

🌐 Docs (web): https://keysight-tech.github.io/cloudlens-vlm-azure/ 📘 Runbook: PDF · DOCX

---

Quick start

git clone https://github.com/Keysight-Tech/cloudlens-vlm-azure.git
cd cloudlens-vlm-azure
chmod +x *.sh

# Download the official CloudLens vLM image from the Keysight portal
#   https://software.keysight.com   (vhd or qcow2)

az login
./deploy-cloudlens-vlm-azure.sh

The wizard asks a few friendly questions (Azure Commercial or Government, location, resource group, reuse or build the managed image, VM size, count, admin user, subnet, who can access), builds the image if needed, creates the vLM, then waits until the vLM is live and verifies the login before finishing.

Azure Government

Same script. Switch cloud, sign in, run:

az cloud set --name AzureUSGovernment && az login
./deploy-cloudlens-vlm-azure.sh --location usgovvirginia

What is here

File	Purpose
deploy-cloudlens-vlm-azure.sh	Interactive wizard: build the managed image and create vLM VMs (Commercial or Government)
create-cloudlens-vlm-image-azure.sh	Non-interactive engine: builds only the managed image
docs/	Full deployment runbook (DOCX + PDF) and the web page

How it works

Keysight vLM image (vhd/qcow2)  ->  convert to fixed VHD  ->  storage blob
   ->  managed disk  ->  managed image  ->  VM  ->  license the vPBs

Requirements

• Azure CLI (az), signed in to the target subscription
• qemu-img (only if the source is qcow2 and needs converting to a fixed VHD)
• The official CloudLens vLM image from software.keysight.com (do not use an unofficial image)