Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For reference, your result will look something like this: 

...

Sign in again using the <customers_tenant_id>

  1. Sign in again using the service principal for the Azure account using the <app_ID>, the <app_registration_password>, and this time using the <customers_tenant_id>.
    Note: <customers_tenant_id> is the same tenant ID that you provided to your Luminoso CSM as part of the image build request.  It is included in the information provided by your Luminoso CSM.
    Enter the commands like this: 

az login --service-principal -u '<app_ID>' -p '<app_registration_password>' --tenant '<customers_tenant_id>'


az account get-access-token

  1. Use the Azure CLI to deploy a VM using a command like the following template. Make sure that you have the <image_version_object_id> that your Luminoso CSM shared with you. At minimum, We recommend 4vCPUs and 16 GiB of RAM as minimum requirements for a machine running Luminoso products. This minimum is for relatively low workloads. Please upgrade your instance size based on workload and performance expectations if needed. If you select a virtual machine type below this level, Luminoso functionality does not run properly.
    az vm create --name <VM_NAME> --resource-group <YOUR_RESOURCE_GROUP> --image <image_version_object_id> --size <VM_SIZE> --data-disk-sizes-gb <DATA_DISK_SIZE_IN_GB> --storage-sku <STORAGE_TYPE> --subnet <YOUR_SUBNET_OBJECT_ID_FOR_DEPLOYMENT> --subscription <YOUR_AZURE_SUBSCRIPTION_ID>

    • Note: to find the SUBNET_OBJECT_ID use the following command.

az network vnet list

  1. Filled out, your command might look like this:

    Image Modified
    • When the command finishes running, a message appears that displays relevant setup information, such as:

  2. SSH to your newly created Luminoso Daylight on-site VM. 

...