Applies to: 
Kyvos Enterprise Kyvos Cloud (SaaS on AWS) 
Kyvos AWS Marketplace
...
| Aura tab collection |
|---|
| params | JTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCU3RCU3RA== |
|---|
|
| Aura tab |
|---|
| summary | AWS |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q= |
|---|
|
NOTE: For AWS, upgrade the latest IAM role with the required permissions when upgrading the Kyvos cluster to the latest release. On the Kyvos Manager, click Update Kyvos Version > Upgrade. The Kyvos Upgrade page is displayed with the details of the current Kyvos bundle and the Kyvos option is selected for the Upgrade field. Click the Select Bundle link to choose the Kyvos bundle from a list of compatible versions. Or, click the Upload New Bundle link to provide your bundle. To view upgrade options, click the Show Upgrade Options link, and configure the following options as needed.
Parameter/Field | Description |
|---|
Create cube semantic model data backup | Select this option to create a backup of the existing cube semantic model data in your Kyvos environment. This may slow down the deployment for taking the backup of cube semantic model data. | Create logs backup | Select this option to create a backup of the existing logs of your Kyvos environment | Backup Path | Shows the backup path. The backup path should be consistent across all the available systems. To edit the path, use the Modify Backup Path option from the use three-dots menu | Configuration | Use these options to preserve or override the existing configurations (cluster's property files or connections). Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix.
| Template | Use these options to preserve or override the existing templates in your Kyvos environment. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
| Repository Data | Use these options to preserve or override the existing Repository Data in your Kyvos environment. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
| License | Use these options to preserve or override the existing Kyvos license. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
|
Click the Upgrade Now button on the top-right of the page.  On the displayed confirmation message box, select the Start Kyvos Service checkbox to start the service automatically after the upgrade. Enter your Kyvos Manager Password to confirm upgrade deployment.
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
| Important You need to manually restore the files uploaded from the Configuration Files page (if any), after upgrading Kyvos. Before the upgrade, a backup will be created and saved at /data/kyvos/app/ location automatically. Before applying the Kyvos upgrade ensure that the IAM role attached to the Kyvos Manager node has the lambda:UpdateFunctionCode permission required for updating Lambda.
|
| Aura tab |
|---|
| summary | Azure |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA== |
|---|
|
For Azure, if you have created a deployment using the Deploy with Enhanced Security option, provide the managed identity permission Microsoft.Network/virtualNetworks/subnets/joinViaServiceEndpoint/action on the virtual network. You can easily upgrade both Kyvos and Kyvos Manager applications to a newer version by simply selecting the required version from the Kyvos Manager portal. To upgrade Kyvos and Kyvos Manager, perform the following steps. On the navigation bar, click Application Update > Upgrade. The Upgrade page is displayed with the current version details of Kyvos and Kyvos Manager. Select the one of the following components from the Upgrade list to which you want to upgrade. Kyvos Manager and Kyvos: To upgrade both Kyvos Manager and Kyvos. Kyvos: To upgrade only Kyvos. Kyvos Manager: To upgrade only Kyvos Manager.
In the Locate Bundle By list, select one of the following: Path: Provide the Kyvos bundle path on the node on which Kyvos Manager is running. File: Click the Select Bundle link to choose the Kyvos bundle from a list of compatible versions. Or, click the Upload New Bundle link to provide your bundle. Version: Provide Client Secret key and click Fetch Versions. All the compatible versions for upgrade is displayed in the Version list.
To view upgrade options, click the Show Upgrade Options link, and configure the following options as needed.
Parameter/Field | Description |
|---|
Overwrite | Select this option to override the existing templates in your Kyvos environment.
NOTE: If the option is selected, a template will be generated. If the option is not selected, the old template will be copied with _backup as a suffix.
| Backup Path | Shows the backup path. The backup path should be consistent across all the available systems. To edit the path, use the Modify Backup Path option from the use three-dots menu | Backup | Semantic Model: Select this option to create a backup of the existing semantic model data in your Kyvos environment. This may slow down the deployment for taking the backup of semantic model data. Log: Select this option to create a backup of the existing logs of your Kyvos environment.
|
Click the Upgrade Now button on the top-right of the page.  On the displayed confirmation message box, select the Start Kyvos Service checkbox to start the service automatically after the upgrade. Enter your Kyvos Manager Password to confirm upgrade deployment.
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
| Important You need to manually restore the files uploaded from the Configuration Files page (if any), after upgrading Kyvos. Before the upgrade, a backup will be created and saved at /data/kyvos/app/ location automatically. Before applying the Kyvos upgrade ensure that the Service account attached to the Kyvos Manager node has the permission required for updating Functions.
|
| Panel |
|---|
| panelIconId | atlassian-note |
|---|
| panelIcon | :note: |
|---|
| bgColor | #DEEBFF |
|---|
| Note Following steps are applicable when migrating from Single Server to Flexible Server. |
| Aura tab |
|---|
| summary | GCP |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q= |
|---|
|
On the Kyvos Manager, click Update Kyvos Version > Upgrade. The Kyvos Upgrade page is displayed with the details of the current Kyvos bundle and the Kyvos option is selected for the Upgrade field. Click the Select Bundle link to choose the Kyvos bundle from a list of compatible versions. Or, click the Upload New Bundle link to provide your bundle. To view upgrade options, click the Show Upgrade Options link, and configure the following options as needed.
Parameter/Field | Description |
|---|
Create cube semantic model data backup | Select this option to create a backup of the existing cube data semantic modeldata in your Kyvos environment. This may slow down the deployment for taking the backup of cube datasemantic modeldata. | Create logs backup | Select this option to create a backup of the existing logs of your Kyvos environment | Backup Path | Shows the backup path. The backup path should be consistent across all the available systems. To edit the path, use the Modify Backup Path option from the use three-dots menu | Configuration | Use these options to preserve or override the existing configurations (cluster's property files or connections). Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix.
| Template | Use these options to preserve or override the existing templates in your Kyvos environment. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
| Repository Data | Use these options to preserve or override the existing Repository Data in your Kyvos environment. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
| License | Use these options to preserve or override the existing Kyvos license. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
|
Click the Upgrade Now button on the top-right of the page. On the displayed confirmation message box, select the Start Kyvos Service checkbox to start the service automatically after the upgrade. Enter your Kyvos Manager Password to confirm upgrade deployment.
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
| Important You need to manually restore the files uploaded from the Configuration Files page (if any), after upgrading Kyvos. Before the upgrade, a backup will be created and saved at /data/kyvos/app/ location automatically. Before applying the Kyvos upgrade ensure that the Service account attached to the Kyvos Manager node has Cloudfunctions.functions.update permission required for updating Functions.
|
| Aura tab |
|---|
| summary | On-Prem |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJPbi1QcmVtJTIyJTdE |
|---|
|
On the Kyvos Manager, click Update Kyvos Version > Upgrade. The Kyvos Upgrade page is displayed with the details of the current Kyvos bundle and the Kyvos option is selected for the Upgrade field. Click the Select Bundle link to choose the Kyvos bundle from a list of compatible versions. Or, click the Upload New Bundle link to provide your bundle. To view upgrade options, click the Show Upgrade Options link, and configure the following options as needed.
Parameter/Field | Description |
|---|
Create cube semantic model data backup | Select this option to create a backup of the existing cube semantic model data in your Kyvos environment. This may slow down the deployment for taking the backup of cube semantic model data. | Create logs backup | Select this option to create a backup of the existing logs of your Kyvos environment | Backup Path | Shows the backup path. The backup path should be consistent across all the available systems. To edit the path, use the Modify Backup Path option from the use three-dots menu | Configuration | Use these options to preserve or override the existing configurations (cluster's property files or connections). Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix.
| Template | Use these options to preserve or override the existing templates in your Kyvos environment. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
| Repository Data | Use these options to preserve or override the existing Repository Data in your Kyvos environment. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
| License | Use these options to preserve or override the existing Kyvos license. Keep existing: Preserve the old configuration from the old state. The new configuration will be renamed with _setup as a suffix. Replace: Generates new configuration. The old configuration will be copied with _backup as a suffix
|
Click the Upgrade Now button on the top-right of the page. On the displayed confirmation message box, select the Start Kyvos Service checkbox to start the service automatically after the upgrade. Enter your Kyvos Manager Password to confirm upgrade deployment.
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
| Important You need to manually restore the files uploaded from the Configuration Files page (if any), after upgrading Kyvos. Before the upgrade, a backup will be created and saved at /data/hdisk1/app/ location automatically.
|
|
...
Post upgrade steps for upgrading to 2023.2 from 2023.1.x
...
Redeploying Zookeeper
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
|
Important To upgrade to the latest version of Zookeeper, switching to managed Zookeeper is mandatory. After redeploying Managed Zookeeper, you must restart Kyvos services. If you are upgrading both Kyvos Manager and Kyvos using either the single click upgrade or the All components upgrade, you must redeploy Zookeeper after upgrading Kyvos Manager.
|
...
When upgrading to a release across which the Managed Zookeeper supported version is changing, post-upgrade, the activity of Managed Zookeeper undeploy/deploy will be required.
...
This is a one-time activity that is required only when upgrading from a prior release using older Managed ZooKeeper version to a Kyvos release which is using the newer version of Managed Zookeeper. For example, if you upgrade from release prior to Kyvos 2023.2 to a release up to Kyvos 2024.1.2 (i.e., when Zookeeper version 3.6.1 was in use and now 3.7.1 is supported).
You must redeploy the Zookeeper using the Zookeeper configuration page in Kyvos Manager to switch to the latest version of Zookeeper. This is necessary for cloud deployments (AWS, GCP, and Azure) and on-prem deployments to remove the previous version of Zookeeperredeploy the Zookeeper using the Zookeeper configuration page in Kyvos Manager to switch to the latest version of Zookeeper. This is necessary for cloud deployments (AWS, GCP, and Azure) and on-prem deployments to remove the previous version of Zookeeper.
Upgrading Zookeeper version
Log onto the Kyvos Manager and navigate to Kyvos and Ecosystem > Zookeeper.
Here, select the External option and click the Save It will undeploy Zookeeper.
Once Zookeeper undeployment is complete, select the Managed by Kyvos option and click the Save This will trigger the deploy Zookeeper operation.
Once Zookeeper deployment is complete, restart all Kyvos services from the Dashboard.
Switching to the previous version of Zookeeper
To access the previous version of the Zookeeper, perform the following steps.
Add the previous Zookeeper version bundle to the Kyvos Manager repository at kyvosmanagerdata/server/repo/ .
Take a backup of the new version 3.7.1 bundle of Zookeeper at a different location outside the Kyvos Manager repo. This bundle will be necessary for switching to the new version 3.7.1 of Zookeeper.
Update the previous version bundle name in the supportedBundles present in the kyvosmanagerdata/server/repo/metadata.Kyvos/zookeeper.json file by deleting the new zookeeper version bundle name and then redeploy the Zookeeper to restore managed Zookeeper to version 3.6.1.
For example, to switch to Zookeeper version 3.6.1, before uninstalling the Zookeeper, a key having a value like supportedBundles : [zookeeper-3.7.1.tar.gz] must be updated with supportedBundles : [zookeeper-3.6.1.tar.gz]
Switching to the default non-managed version of Zookeeper
To restore the default non-managed version of Zookeeper on the Kyvos Manager node, which was removed during the uninstallation of Managed Zookeeper, you will need to manually install Zookeeper on the Kyvos Manager node.
Upgrade Graviton JRE for AWS cluster
To upgrade Kyvos, perform the following post-upgrade steps.
...
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
|
Important From Kyvos 2023.2 onwards, for AWS, the restoration process for the external repository RDS has been automated, eliminating the need for manual intervention. From Kyvos 2023.2 onwards, for AWS, if Kyvos is using an external repository RDS as its repository, before initiating a Kyvos rollback, ensure that the 'UsedBy' tag with a value of 'Kyvos' is added to the RDS subnet/security group used for creating the database instance, if it has not already been added. In case of a Rollback, the previous state of Kyvos is restored. In case you made any entity-specific modifications like changes to the semantic model design, registered files, users, etc., Kyvos recommends the designers/Admins create a cab as a backup before rollback and import the cab file to the rolled-back version. Process operations cannot be persisted. From Kyvos 2023.1 release onwards, if you roll back to a Kyvos Manager process that supports Derby as its repository, any operations, such as audits, events, or other activities (like users add, import, delete, and update) performed using Kyvos Manager build 2023.1 and onwards will NOT be available when you rollback to a Kyvos Manager release previous to 2023.1. The rollback operation will take some time to initiate. If you roll back the 2023.2 Kyvos Manager build to a version prior to 2023.2, a warning message will display, indicating that the spark distribution update has failed. The spark distribution bundle is only available in the Kyvos 2023.2 release and cannot be accessed in any previous versions. Kyvos rollback to earlier releases not supporting Flexible server: Post Kyvos rollback, configure the single server in Kyvos through the switch repository of Kyvos Manager. The application automatically handles the single server being configured. It must have the same compatible state of the database with the Kyvos release to which rollback is performed. A change in the user name will be required while configuring a single server in the system as it requires appending the server name to the username.
|
...
Create a manual backup of your existing cluster using the steps explained in the Upgrading Kyvos Manager and Kyvos section.
On the navigation pane, click Application Update > Rollback.
The Rollback page is displayed.
Click the Select rollback state link. From the displayed dialog box, choose the state to which you want to roll back. You can use the search box to Search for a specific version, or view Operation Details using the corresponding link.
The Backup Path path shows the path used for creating/restoring a backup of Kyvos states in case of Deploy Upgrade and Deploy Patch/Rollback operations. The backup path should be consistent across all the available systems. You can edit this path using the Modify Backup Path option from the three-dots menu. A ny backup created prior to changing the path remains unaffected and will continue to be available at the same location.
Click the Rollback Now button from the top-right of the page.
On the displayed confirmation message box, select the Start Kyvos Service checkbox to start the service automatically after rollback.
Enter your Kyvos Manager Password to confirm the rollback. Kyvos takes you to the Operations page followed by the Rollback Logs details page.
...
From Kyvos 2023.3 onwards, during Kyvos upgrade and patch processes, the oldest backup bundle will be deleted automatically to retain the newest bundles within the specified limit. Suppose you choose to preserve 6 bundles out of 10 available. In this case, only the 6 most recent bundles will be saved, and the remaining 4 bundles will be deleted. The oldest of these 4 bundles, based on the date they were created, will be deleted first.
To delete a previous state of rollback, use the Manage Backup Bundles option from the three-dots menu.
...
In the Preserve Backup Bundles list, set the count to retain the bundles.
Points to know
If the number of bundles present exceeds the preserved count, the remaining bundle will be automatically selected, indicating that it will be deleted.
If the number of bundles equals the retention count, no bundles will be deleted.
Bundles can only be deleted by changing the preserve count. Selecting them for deletion is disabled and unsupported.
If the latest backup bundle is a Patch, then the most recent Kyvos bundle will also be preserved.
The backup bundles which are created for failed Kyvos upgrade or failed Patch operations will also be there in the list to delete.
...
| Panel |
|---|
| panelIconId | atlassian-note |
|---|
| panelIcon | :note: |
|---|
| bgColor | #DEEBFF |
|---|
|
Info If you restore a previous version of Kyvos Manager or Kyvos, any data that was added or performed in Kyvos Manager after switching to Postgres (starting with Kyvos 2023.1) - such as audits, operations, users, and alerts - will be lost. |
You must perform the following manual steps to perform a Kyvos, or Kyvos Manager process rollback:
Change the JDBC URL in the jdbc.properties to a Derby-specific URL. To do this, you must rename the existing jdbc.properties (using Postgres as a repository) to the jdbc.properties.postgres and then rename the existing jdbc.properties.derby to jdbc. properties.
NOTE: The files are located at: kyvosmanagerdata/server/db/
In addition, if the bundled Postgres is used as the Kyvos Manager repository, it is necessary to move the Postgres folder inside Kyvos on each node of the cluster from its current location parallel to Kyvos.
To switch back to the old Derby-compatible version of Kyvos Manager, first stop the current Postgres, which is supported as the Kyvos Manager process repository.
If a Kyvos rollback is also required, then perform it using the Derby-compatible Kyvos Manager only. Also, ensure that you perform Step 3.
Deploy Patch
To deploy a patch on an existing Kyvos version, perform the following steps.
| Aura tab collection |
|---|
| params | JTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCU3RCU3RA== |
|---|
|
| Aura tab |
|---|
| summary | AWS |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q= |
|---|
|
On the Kyvos Manager, click Update Kyvos Version > Upgrade. The Kyvos Upgrade page is displayed with the details of the current Kyvos bundle and the Kyvos option is selected for the Upgrade field. Click the Select Bundle link to choose the Kyvos bundle from a list of compatible versions. Or, click the Upload New Bundle link to provide your bundle. To view upgrade options, click the Show Upgrade Options link, and configure the following options as needed.
Parameter/Field | Description |
|---|
Create backup | Select this option to create a backup of the existing Kyvos environment before deploying the patch. Selecting this option will speed up patch deployment as no data backup will be performed. However, the currently deployed version can not be
restored using rollback | Create cube semantic model data backup | Select this option to create a backup of the existing cube semantic model data in your Kyvos environment. This may slow down the deployment for taking the backup of cube semantic model data. | Create logs backup | Select this option to create a backup of the existing logs of your Kyvos environment | Backup Path | Shows the backup path. The backup path should be consistent across all the available systems. To edit the path, use the Modify Backup Path option from the use three-dots menu. |
Click the Deploy Now button on the top-right of the page. On the displayed confirmation message box, enter your Kyvos Manager Password to confirm upgrade deployment.
You need to manually restore the files uploaded from the Configuration Files page (if any), after upgrading Kyvos. Before applying the Kyvos upgrade ensure that the IAM role attached to the Kyvos Manager node has the lambda:UpdateFunctionCode permission required for updating Lambda.
|
| Aura tab |
|---|
| summary | Azure |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA== |
|---|
|
On the Kyvos Manager, click Update Kyvos Version > Upgrade. The Kyvos Upgrade page is displayed with the details of the current Kyvos bundle and the Kyvos option is selected for the Upgrade field. Click the Select Bundle link to choose the Kyvos bundle from a list of compatible versions. Or, click the Upload New Bundle link to provide your bundle. To view upgrade options, click the Show Upgrade Options link, and configure the following options as needed.
Parameter/Field | Description |
|---|
Create backup | Select this option to create a backup of the existing Kyvos environment before deploying the patch. Selecting this option will speed up patch deployment as no data backup will be performed. However, the currently deployed version can not be
restored using rollback | Create cube semantic model data backup | Select this option to create a backup of the existing cube semantic model data in your Kyvos environment. This may slow down the deployment for taking the backup of cube semantic model data. | Create logs backup | Select this option to create a backup of the existing logs of your Kyvos environment | Backup Path | Shows the backup path. The backup path should be consistent across all the available systems. To edit the path, use the Modify Backup Path option from the use three-dots menu. |
Click the Deploy Now button on the top-right of the page. On the displayed confirmation message box, enter your Kyvos Manager Password to confirm upgrade deployment.
| Aura tab |
|---|
| summary | GCP |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjAlMjIlN0Q= |
|---|
|
On the Kyvos Manager, click Update Kyvos Version > Upgrade. The Kyvos Upgrade page is displayed with the details of the current Kyvos bundle and the Kyvos option is selected for the Upgrade field. Click the Select Bundle link to choose the Kyvos bundle from a list of compatible versions. Or, click the Upload New Bundle link to provide your bundle. To view upgrade options, click the Show Upgrade Options link, and configure the following options as needed.
Parameter/Field | Description |
|---|
Create backup | Select this option to create a backup of the existing Kyvos environment before deploying the patch. Selecting this option will speed up patch deployment as no data backup will be performed. However, the currently deployed version can not be
restored using rollback | Create cube semantic model data backup | Select this option to create a backup of the existing cube semantic model data in your Kyvos environment. This may slow down the deployment for taking the backup of cube semantic model data. | Create logs backup | Select this option to create a backup of the existing logs of your Kyvos environment | Backup Path | Shows the backup path. The backup path should be consistent across all the available systems. To edit the path, use the Modify Backup Path option from the use three-dots menu. |
Click the Deploy Now button on the top-right of the page. On the displayed confirmation message box, enter your Kyvos Manager Password to confirm upgrade deployment.
|
.png?version=1&modificationDate=1703155876565&cacheVersion=1&api=v2&width=350)