Cluster Name

Provide a unique cluster name.

License

Upload your Kyvos license file.

Installation Path

Provide the installation path for Kyvos.

Username

Enter your username.

Authentication Type

• Password: Provide your credentials. Ensure that the permissions listed here are available on all the EC2 instances for Linux user deploying the cluster

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

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 a custom hostname for the selected Analytical Server, Query Engine, and Kyvos Manager/repository node.
    NOTE:  Ensure that the instances have been configured for using Custom hostnames.

• Resource By:

  • Select Stack or Account as needed.

  • For Stack:

    1. Select the stack from the list.

    2. Click Refresh Stack resources to view and modify any resources. The resources configured in the stack, such as EC2 instance(s) for Analytical Server, EC2 instance(s) for Query Engine, EC2 instance(s) for Web Portal, and so on are displayed. Click the Modify link corresponding to the Identified Resources to edit them. You can also select the Repository here.
       NOTE: If you want to use your own resources, select the Account option, and provide the details in the displayed fields. Here, if you have the requisite permissions, your AWS resources will be displayed in the lists. Otherwise, you will have to manually provide the details.

  • For Account:

    1. Select the Deploy BI Server, Query Engine, and Web Portal services on ip-<>.ec2 internal instance checkbox. This checkbox is displayed only when you select the Account (node mapping Manually) option. Selecting this checkbox will deploy Kyvos services on the same instance. 
       NOTE: By default, the option to deploy EC2 instance(s) for Analytical Server, EC2 instance(s) for Query Engine, and EC2 instance(s) for Web Portal will be disabled.

• Virtual IP/Hostname: This is enabled only when multiple Web Portal based deployment is opted.

• Enable Kyvos Manager for High Availability: Select this checkbox to deploy Kyvos Manager High Availability (HA) enabled cluster. This is enabled only when multiple Web Portal based deployment is opted.

• Load Balancer Configuration: Select the Configuration for Web Portal and Configuration for Kyvos Manager checkboxes.

  • Configuration for Web Portal: Select the ARN or Target Group Name from the Resource Identified by list. The options will vary based on your selection.

    • Enter the ARN or Target Group Name.

  • Configuration for Kyvos Manager: Select the ARN or Target Group Name from the Resource Identified by list. The options will vary based on your selection.

    • Enter the ARN or Target Group Name.

  • Validate: Click this option to verify the details. The system will check for the details. If all the provided details are correct, you can continue with deployment. Else, you must re-verify the details.

Compute Cluster

• Compute Cluster Type: Select the EMR option.

• Use Hive as data source: Select if your data is stored on Hive. Please uncheck if using S3, Glue, or Snowflake as a data source.

SSH Preferences

Select the Use SSH for connecting with EMR Cluster Master Node checkbox to enable SSH.

1. User Name: Enter your username,

2. Use different private key for EMR nodes authentication: Select this option to use a different private key for the EMR node.

3. Private Key: Upload the private key for the EMR node.

Livy

• Enable Livy: Select the checkbox to use the Livy server for spark job submission, monitoring, and cancellation.

• Livy URL: Provide the URL of the Livy server to be used.

Common

Kyvos Setup Package

Select the Kyvos bundle to be installed. Kyvos Manager contains compatible Kyvos bundles. To use any other Kyvos version, click the Upload button

Semantic Model Local Path

Enter the semantic model local path where cuboids will be copied. For multiple paths, enter a semicolon-separated list.

NOTE: The deployment user must have full permission on the parent of the local semantic model path.

Automatically restart Kyvos services when down

Select this option to enable high availability mode for the Kyvos service. This will ensure Kyvos services are always up and running. The Kyvos Manager will automatically restart the Analytical Server, query engine, repository, and web portal services, in case any of these services go down

BI Server

Listener Port

Enter the listener port for Analytical Server.

JMX Port

Enter the JMX port for Analytical Server health monitoring.

Work Directory

Enter the directory location on HDFS, where Analytical Server has access permissions.

Memory Configuration Mode

By default, the Auto mode is selected. In Auto Mode, calculations are performed automatically by the system internally.
In Manual Mode, you can manually provide memory values as needed.
NOTE: The Maximum Heap Memory and Analytical Store Max Memory options are enabled only when you set the memory configuration in the Manual mode.

Maximum Heap Memory

Enter the maximum memory available for Analytical Server.

Analytical Store Max Memory

Specify analytical store max memory for querying in GB.

Additional Java Options

Use this to define custom Java properties for your Analytical Server.

Query Engine

Thrift Listener Port

Enter the thrift listener port for Query Engine.

JMX Port

Enter the port for Query Engine health monitoring.

Memory Configuration Mode

By default, the Auto mode is selected. In Auto Mode, calculations are performed automatically by the system internally. In the Manual Mode, you can manually provide memory values as needed.

NOTE:

• The Maximum Heap Memory, Analytical Store Max Memory for Querying, Analytical Store Max Memory for Processing, and Configure Concurrent Processing Task options are enabled only when you set the memory configuration in the Manual mode.

• If you set the memory configuration in the Manual mode, the Configure Concurrent Processing Task option can be enabled as Auto or Manual as needed.

Maximum Heap Memory

Enter the maximum memory for Query Engine.

Analytical Store Max Memory for Querying

Specify analytical store max memory for querying in GB.

Analytical Store Max Memory for Processing

Specify analytical store max memory for processing in GB.

Configure Concurrent Processing Task Count

By default, the Auto mode is selected. If you select the Manual mode, specify the number of nodes to be used for concurrent processing task count.

Additional Java Options

Use this to define custom Java properties for your Query Engine.

Web Portal

UI Port

Enter the port on which Kyvos Web client will run.

JMX Port 

Enter the port for Web portal health monitoring.

Shut-down Port 

Enter the port to be used for shutting the Tomcat server.

AJP Port 

Enter the port on which the AJP connector creates a socket and awaits an incoming connection.

Maximum Heap Memory

Enter the maximum memory for the Web portal.

Additional Java Options

Use this to define custom Java properties for the Web portal.

Network Protocol Configuration 

Enable TLS 

Select the checkbox to enable TLS for the cluster.

NOTE: Before enabling TLS, if you are using your own script for resource creation instead of the Kyvos shared scripts, you must rename the OpenSSL configuration file on the Kyvos Manager and the node where the Postgres Service is running. The OpenSSL configuration file in the /etc/pki/tls/openssl.cnf folder.

To accomplish this, you will need to have sudo access.

HTTP Protocol Version 

Select the HTTP Protocol Version for use with TLS.

Kyvos Web Portal on HTTPS 

Select the checkbox to use HTTPS for connecting to Kyvos Web Portal.

Kyvos Web Portal Configuration

NOTE: This is displayed only if Kyvos Web Portal on HTTPS checkbox is selected

• Certification Mode: Select the Use Path or Upload File option.

• Keystore: Provide the path or upload the Keystore file for the certificate.

• Keystore Private Key: Provide the Keystore Private Key for the certificate.

• Custom Attributes for Connectors: If needed, provide attributes to be used for the HTTPS connector.