Versions Compared

Key

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

...

Area

Parameter/Field

Remarks/Description

Cluster Name

Provide a unique cluster name

License

Upload your Kyvos license file, and click UPLOAD.

Installation Path

Provide the installation path for Kyvos

Authentication

User Name

Enter your username for authentication.

Authentication Type

  • Private Key: Choose and Upload the Private Key file.

  • Password: Provide your credentials.

    NOTE: To use password authentication for instances while deployment, ensure that the instances have been configured for using Password-based authentication.

Configure Kyvos Services on Cloud

Select Instance by

  • IP Address: Select this option for IP Address-based deployment.

  • Hostname:  Select this option for hostname-based deployment. In this case, you can deploy the cluster using custom hostnames for nodes to be used for Kyvos services. 

    • Click the Use custom hostname for selected nodes link to specify or map custom hostname for selected BI Server, Query Engine, and Kyvos Manager/repository node.
      NOTE: Ensure that the instances have been configured for using Custom hostnames.

Deployment

Select the deployment that you created on the Azure portal.

Click Fetch resources to view and modify any resources. 

Virtual machines for Bl Server

Provide a comma-separated list of IP Addresses/Hostname (depending on the type selected above) for the Virtual machines to be used as BI Server instances.

Virtual machines for Query Engine

Provide a comma-separated list of IP Address/Hostname (depending on the type selected above) for the Virtual machines to be used as Query Engine instances.

Virtual machines for Web Portal

Provide a comma-separated list of IP Addresses/Hostname (depending on the type selected above) for the Virtual machines to be used as Web Portal instances.

Repository

Provide IP Address/Hostname (depending on the type selected above) for the Virtual machines to be used as a repository for Kyvos.

Repository Password

Provide the Postgres repository password.

Storage

ABFS Account Name

Provide the ABFS Account Name to be used for storage.

File System Type

Select file type as ABFS or ABFSS

Container Name

Provide the ABFS Account Name to be used for storage.

Key Vault

Vault URL

Enter the key vault URL.

Compute Cluster

Compute Cluster Type

Select the Kubernetes or Shared Query Engines option.

NOTE: When you select Kubernetes from the Compute Cluster list, the Kubernetes Details section is displayed.

Kubernetes Details

Enter the following Kubernetes details:

  • Kubernetes Cluster Name: Select the Kubernetes cluster name from the list. Click Fetch Details. The Kubernetes cluster details will be fetched.

  • System Node Pool Name: Select the system Node Pool name from the list.

  • User Node Pool Name: Select the User Node Pool name from the list.

  • Validate Kubernetes Cluster Details: Click this link to validate Kubernetes cluster details.

Enable Compute Server Scaling

Select this checkbox to enable maximum or minimum compute server for scaling. When you select this checkbox, the following options will be displayed.

  • Minimum Compute Server Count: Select the minimum compute Server count that will be started initially.

  • Maximum Compute Server Count: Select the maximum compute Server count up to which you want to scale.

  • Fetch Parameters: Clicking this will open a new dialog box where you need to provide the following details:

    • fs.azure.account.auth.type: The OAuth input is displayed by default.

    • fs.azure.account.oauth.provider.type: The input for this field is displayed by default.

    • fs.azure.account.oauth2clientID: Enter the managed identity client ID.

    • fs.azure.account.oauth2clientID: Enter the tenant ID.

NOTE: If you do not select this checkbox, the Compute Server Count field is displayed. Compute server scaling will be disabled if this checkbox is not selected.

Function

Function Deployment

Optionally, provide the name of the deployment where your Azure Functions are deployed.
NOTE: This is displayed only if the stack that was created, contains functions.

...