Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Applies to: (tick) Kyvos Enterprise  (error) Kyvos Cloud (SaaS on AWS) (error) Kyvos AWS Marketplace

(error) Kyvos Azure Marketplace   (error) Kyvos GCP Marketplace (error) Kyvos Single Node Installation (Kyvos SNI)


To create Kyvos resources for creating an ARM template for use in automated deployment, perform the following steps.

Note

To create a Kyvos Manager node, go to metadata.json file in the <install dir>/kyvosmanager/cloud/azure/templates folder and set the value for showKMNode as true.

The Managed Identity attached to the Kyvos Manager node must have reader rights on the Resource Group to create an ARM template for Azure automated deployment.

  1. Access the Kyvos Installer using the URL and credentials provided by the Kyvos Support Team or use the default credentials admin | admin. If you do not have the URL, click here to contact support.

  2. To create resources for installing Kyvos services like BI Server and Query Engine on the Azure environment, select the I want to create resources option on the Kyvos Installer page.

  3. Click Create Resources. This displays the Create Resources wizard.

  4. Here, select the services for which you want to create resources and provide information as:

    NOTE: Resources will be created only for selected services. If you have pre-created resources for any of the services, you can uncheck them and configure them while installing Kyvos.

Parameter/Field

Remarks/Description

Create VNET

Select this checkbox to create a new virtual network with the deployment. 
NOTE: All the required network resources, such as Virtual Network, Subnets, and Network Security Group will be created. 

Create Security Group

Select this checkbox to create a new Network Security Group with the deployment. 

Virtual machine(s) for BI Server

You cannot clear this check box. Here define:

  • Number of Node(s)

  • Instance Type

Virtual machine(s) for Query Engine

Select this option to create virtual machines for Kyvos query engines, and define:

  • Number of Node(s)

  • Instance Type

  • Storage Disk

  • Disk Type

Web portal high availability

Select to enable Kyvos web portal high availability.
If you select this, you need to provide the following:

  • Number of nodes

  • Instance Type

  • Subnet for Load Balancer - Currently, only Public is supported.

Virtual machine for Kyvos Manager

Select this option to launch a virtual machine for Kyvos Manager, and select the Instance Type from the list. 
NOTE: This option will be displayed only in the case of automated deployment.

  • When using a multi-tenant environment, you can use the  Deploy as Tenant checkbox to define a tenant instance for Kyvos Manager. Enable this option to deploy the cluster as a tenant. If enabled, you will see an input for the Management Console URL in the Template parameters, which manages all the tenants.

  • Select any one of the following Repository: 

    • Bundled Postgres : To select bundled Postgres as a repository for Kyvos Manager. 

    • Create New Azure Postgres : To create a new external Azure Postgres repository for Kyvos Manager. 

    • Use Existing Azure Postgres : To use the existing external Azure Postgres repository for Kyvos Manager. 

External Repository for Kyvos

Select to create a PostgreSQL-based repository using Azure. Otherwise, the pre-bundled PostgreSQL-based Kyvos repository will be used.

  • Select any one of the following Repository: 

    • Bundled Postgres : To select bundled Postgres as a repository for Kyvos Manager. 

    • Create New Azure Postgres : To create a new external Azure Postgres repository for Kyvos Manager. 

    • Use Existing Azure Postgres : To use the existing external Azure Postgres repository for Kyvos Manager. 

Create Storage Account

Select this option to create ABFS Account and Container for storing Kyvos output, and define:

  • Storage Name Prefix

  • Container Name Prefix

Compute Cluster

Select the Kyvos Native option from the list.

Kyvos Native Type

Select one of the following options from the list.

  • Shared Query Engines

  • Kubernetes (K8S)

NOTE: A new Kubernetes cluster will be used as a compute server to process semantic models.

Enhance Storage Account High Availability

Select this checkbox to create Zone-Redundant Storage (ZRS).

Kyvos Cluster Deployment with Load Balancer 

The checkbox is selected by default if Web Portal high availability is enabled, or if a non-peered network exists between Kyvos and Databricks, the Kyvos cluster will be deployed with a load balancer.

NOTE: If Web Portal high availability is not enabled, or if a peered network exists between Kyvos and Databricks, the Kyvos cluster will not be deployed with a load balancer. In this case, the checkbox is selected, but you can also clear it as per the requirement. 

Use Custom Image

Select this option to use a custom image of your environment for deploying the Kyvos cluster. Custom images can be used to bootstrap deployment tasks like preloading applications, application configurations, and other configurations. 
You will have to provide information for Gallery Name, Gallery Image Definition Name, and Gallery Image Version Name at the time of deploying the cluster through the ARM template.

NOTE:

  • To use your custom image, templates named bi_custom.json, qe_custom.json, and km_custom.json must exist at $KYVOS_MANAGER_HOME/cloud/azure/templates/ location.

  • For using Custom Image, Kyvos supports using only customer-provided Images for CentOS 7, RHEL 7, and RHEL 8.   

    • Python 2 is required as a prerequisite for CentOS 7 and RedHat 7 Images  

    • Python 3 is required as a prerequisite for RedHat 8 AMIs and CentOS 8 Images  

  • To ensure proper functionality of Kyvos Manager and Kyvos, all required operating system commands must be present in the Custom Image machine.
    See the  OS commands  section for more details.

Deploy with Enhanced Security

Enhanced security enables advanced security for Storage Accounts, Key Vaults, and Virtual machines.

Credit based deployment

Select this option if you want to use credit-based licensing and your environment does not have pre-created credit information-related resources.

Release Type Preferences

Select Kyvos Release as General Availability (GA) and Alpha.

  1. Click Next. The Review and Download Template dialog box is displayed with details of all the settings that you selected.

  2. Review all the settings, and click the BACK button if you want to make any changes.

Note

Function Deployment will always be created with the cluster resources being created to enable scheduling feature in the cluster.

  1. To continue, click the Download Template button to download the Azure resources template.

  2. Click the Open Azure Resource Manager link to access the Azure portal to upload this template to your Azure environment to create resources.

  3. Sign in to your Azure account having requisite permissions, as mentioned in the prerequisites.

  4. On the Custom Deployment page, click the Process your own template in the editor option.

  5. On the Edit Template page, click Load File, and upload your template. The Template is loaded.

  6. Click Save.

  7. The Deployment page is loaded with parameters required for deployment.

    Fields marked * are mandatory.

Parameter 

Description 

Subscription* 

Your account subscription. 

Resource Group* 

Enter the name of your resource group. The resource group is a collection of resources that share the same lifecycle, permissions, and policies. 

Virtual Network Name* 

Name of Virtual Network in which your VMs will run. 

VM Subnet Name* 

Name of Subnet in which your VMs will run. This Subnet should be part of the above Virtual Network. 

ApplicationGatewaySubnetName *  

Name of the Subnet in which Application Gateway will be created. The Subnet should be part of the above Virtual Network. 

NOTE: This parameter will display only if an existing VPC is used for deployment.

Flexible Server Subnet Name

Name of the Subnet in which Flexible Server will be created. The Subnet should be a part of above Virtual Network.
NOTE: A seperate subnet is required for Flexible Server.

Virtual Network Resource Group Name* 

Name of Resource Group in which Virtual Network and Subnet are deployed. 

Security Group Name*

Name of the Security group that can be used to access the VMs.

Security Group Resource Group Name* 

Name of the Resource Group in which the Security Group is deployed. 

Enable Managed Identity Creation 

Select True to create a new managed identity for Kyvos. 
Select False to use an already existing managed identity. 

Managed Identity Name* 

Enter the name of the User-Managed Identity to be attached to all Kyvos VMs. 

Managed Identity Resource Group Name 

Name of the Resource Group in which Managed Identity is deployed. 

Kyvos Work Directory 

Enter the path for the Kyvos work directory. 

SSH Public Key* 

Provide an RSA public key in the single-line format (starting with "ssh-rsa") or the multi-line PEM format. 
You can generate SSH keys using ssh-keygen on Linux and OS X, or PuTTYGen on Windows. 

Additional Tags 

Enter the additional tags to put on all resources. 
Use the syntax as: {"Key1": "Value1", "Key2" : "Value2"} 

Storage Account Name 

Enter the name of the Storage Account to be used for Kyvos. 

Storage Account Container Name 

Enter the name of the Container in the Storage Account which will be used for Kyvos. 

CustomPrefixVirtualMachines

Enter a custom prefix that you want to append before the name of the virtual machines to be used for Kyvos.

CustomPrefixVPC

Enter the custom prefix you want to append before the name of VPC in case a new VPC is created for use with Kyvos.

CustomPrefixNSG

Enter the custom prefix you want to append before the name of the Network Security Group in case a new group is created for use with Kyvos.

CustomPrefixKeyVault

Enter the custom prefix you want to append before the name of Key Vault in case a new Key Vault is created for use with Kyvos.

CustomPrefixScaleSet

Enter the custom prefix you want to append before the name of Scaleset that will be created for use with Kyvos.

Vault URL 

Provide the URL for your existing Azure Key vault. If the Key Vault is not provided, Kyvos will create a new Key Vault named kyvosvault<XXXXX>. Here, XXXXX is a unique five-digit identity generated as a suffix to the Kyvos vault. 

Vault Resource Group 

Name of Resource group in which the Key Vault is deployed. 

Log Analytics Workspace Resource ID

Resource ID of the existing Log Analytics Workspace.

NOTE: If you want to create a new Log Analytics Workspace, leave the value blank.

Azure Function Crontab

Crontab entry to call Azure functions for use with cluster scheduling.

Default value: [utcNow('u')]

Custom Prefix Scale Set

Enter the prefix to be append before Scale Set. The name can be up to 60 characters long. It must begin with a word character, and it must end with a word character.

Storage Account Resource Group 

Enter the name of the Resource Group in which the Storage Account is deployed. 

Virtual Machine Type for Kyvos Postgres

Virtual Machine Type which will be launched

Enable HA For Kyvos Postgres

Enable High Availability for Kyvos PostgreSQL pricing tier.

Backup Retention for Kyvos Postgres

Number of days the backup should be kept for Kyvos PostgreSQL. The value can be between 7 to 35.

SSH Private Key* 

Provide the RSA private key in the single-line format. 

Kyvos Cluster Name 

Provide a name for your Kyvos cluster. 

Kyvos Installation Path 

 

Provide the installation path to be used for deploying the Kyvos cluster. 

Postgres Password* 

Provide the value of the password used for Postgres 

License File Value* 

Enter a valid Kyvos License. 

Secret Key For Kyvos Bundle Download* 

Enter the Secret key to access the Kyvos bundle. 

Firewall Ip White List 

Provide a comma-separated list of the IP rules to be set for the Key Vault and Azure Storage Account. 
NOTE: This field is displayed only if you had selected the Deploy with Enhanced Security checkbox at the time of creating the template. 

Dns Label Prefix 

Unique DNS Name for the Public IP used to access the Virtual Machine. 

Perform Env Validation

Select True to perform environment validation before cluster deployment to ensure all the resources are created correctly.

Host Name Based Deployment

Select True to use hostnames instead of IP Addresses for instances during cluster deployment. 

KM Repository Password

Specifies the value of the password used for Postgres. Note: Password must contain 8 to 128 characters from three of the following categories: English uppercase letters or English lowercase letters, numbers (0 through 9), and non-alphanumeric characters (for example, !, $, #, %).

Km Repo Username

Specifies the value of user used for Kyvos Manager Repository.

Km Repo Database

Specifies the value of database used for Kyvos Manager Repository.

Virtual Machine Type for Kyvos Manager Postgres

Virtual Machine Type which will be launched for Kyvos Manager PostgreSQL

Enable HA for Kyvos Manager Postgres

Enable High Availability for Kyvos Manager PostgreSQL pricing tier.

Backup Retention for Kyvos Manager Postgres

Number of days the backup should be kept for Kyvos PostgreSQL. The value can be between 7 to 35.

Worker Instance Type

Enter Worker Instance Type

Min Pod Count

Enter required number of Pod count.

Max Worker Node Count

Enter maximum number of worker nodes.

Private Dns Zone Resource ID

Resource ID of existing Private DNS Zone which will be used with Flexible Server. If you want to create new Private DNS Zone, leave the value blank.

Object Id of Service Principal* 

The Object ID assigned to the Service principal. This maps to the ID inside the Active Directory. 

Azure Postgres Server Sku Tier 

Azure Database for PostgreSQL pricing tier. 

SSH public key source

Select the required option from the SSH public key source list. 
NOTE: If you select the Use Existing public key option from the list, the SSH Public Key field is displayed. 

Enable Public IP 

Select True to enable Public IP for the Kyvos Web portal. 

Type of Public IP

Type of Public IP address for Kyvos Web portal from Dynamic or Static.

  1. Click Review + Create

  2. The system validates your inputs and displays a summary of the provided inputs. To continue with deployment, click Create.

    This creates all the resources and services required for deploying the Kyvos cluster. 

Next: Cluster installation using resources created for Azure through stack

  • No labels