Deploy LHO on Client Provided Resources (Azure)

Owned by Ciprian LUCACI
Last updated: Nov 20, 2024 by bkepler@bpcs.com
2 min read

This page contains a guide to install Lakehouse Optimizer using cloud resources that were created previously by the administrator.

 

Step 1) Required Resources

Lakehouse Optimizer requires the following resources to already be created:

 

Step 2) Configuration Prerequisites

  • Azure KeyVault needs to be preconfigured with the following secrets:

    • msft-provider-auth-secret - This is the Service Principal client secret

    • mssql-password - The SQL database password

    • storage-account-key - The access key used for the Azure storage account.
      Note: this is optional, needed only if you don’t want to access the storage account using the Service Principal.

    • application-encryption-secret - used for app encryption. This value is essentially a random string password, so generate accordingly.

More information about how these entries can be created can be found here:

 

Step 3) Installation procedure

  1. SSH into the BPLM VM configured at Step 1) Required Resources.

    1. download the install archive by running the following command:

RHEL:

wget https://bplmdemoappstg.blob.core.windows.net/deployment/vm-azure/lho_rhel.zip

Ubuntu:

wget https://bplmdemoappstg.blob.core.windows.net/deployment/vm-azure/bplm-install.zip

 

  1. Extract the archive contents
    unzip <archivename>.zip -d <destination folder>

  2. In the destination directory you should see the following files:

    .env docker-compose.yml setup.sh start.sh

    1. setup.sh will install Docker and other automation tools (e.g. OpenSSL)

  3. Before you start the setup you need to fill the .env file with the needed information (url of the app, Key Vault url, etc). Open the file in your editor of choice and fill in the values.

    1. Please find a brief explanation of the .env values below

  4. Run setup.sh.

    • cert_domain is Fully Qualified Domain Name of the application. Used to generate self-signed certificate

    • email_certbot email address notified when cert is pending expiration.

    • e.g. ./setup.sh -d=my-lhm-deployment.com -v=2.5.0

     

  5. If setup.sh executed successfully you can run start.sh to pull down the app container and start the application.

    1. Lakehouse Optimizer leverages a containerized application. This container is hosted in Blueprint’s Azure Container Registry (ACR). If you have not been provided an ACR token, please reach out to Blueprint support

  • where acr_username is the ACR token name provided by Blueprint

    • start.sh will prompt you for the token password

  • e.g./start.sh -u=lho-acr-ex