This page contains a guide to install Lakehouse Monitor using cloud resources that were created previously by the client.
Step 1) Required Resources
Lakehouse Monitor requires the following resources to already be created:
Step 2) Configuration Prerequisites
The Azure KeyVault needs to contain the following secrets:
msft-provider-auth-secret
- This is the SP client secretmssql-password
- The DB passwordstorage-account-key
- The access key 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.
Step 3) Installation procedure
SSH into the BPLM VM and download the install archive
wget https://bplmdemoappstg.blob.core.windows.net/deployment/vm-azure/bplm-install.zipExtract the archive contents
unzip archive.zip
In the destination directory you should see the following files:
.env docker-compose.yml setup.sh start.sh
Before you start the setup you need to fill the
.env
file with the needed information (url of the app, keyvault url, etc). Open the file in your editor of choice and fill in the values.Please find a brief explanation of the .env values below
APPSERVICE_URL= #default is https://<vm dns> AZURE_KEYVAULT_TENANTID= # Azure Active Directory tenant ID AZURE_KEYVAULT_URI= # can be found in keyvault properties page in azure portal AZURE_MANAGED_IDENTITY_ID= # VM system assigned identity objcet ID AZURE_MANAGED_IDENTITY_APP_ID= # app id of VM system assigned identity. Can be found under the vm name in Enterprise application directory SERVICE_PRINCIPAL_CLIENTID= # Service principal tied to app registration client (also called app) id SERVICE_PRINCIPAL_OBJECTID= # Service principal tied to app registration object ID SERVICE_PRINCIPAL_TENANTID= # Azure Active Directory tenant ID SQL_SERVER_HOST= # can be found in sql server properties SQL_USER= # username of sql server STORAGE_AZURE_ACCOUNT= # storage account name STORAGE_AZURE_CONTAINER= # container name created for lakehouse
Run the
setup.sh
.bash setup.sh
Note: when prompted if you want to use the Service Principal to access the storage account please keep in mind that if you choose Yes, the keyvault should not contain the
storage-account-key
secret and if you choose No you will have to have that secret in the keyvault.If the setup executed successfully you can run the
start.sh
script to start the system.bash start.sh
Add Comment