Upgrading Cloudera AI Registry

When you upgrade a Cloudera AI Registry, you create a new version of the registry. You can roll back to the old version, or delete the old registry if it is no longer needed.

The Cloudera AI Registry upgrade process involves provisioning a new cluster, so the process can take some time, on the order of 40 to 60 minutes. The upgrade operation shall be performed during a maintenance window, when new models are not being added or updated in Cloudera AI. The window shall be available approximately 3 hours long at a minimum.

In AI Registries, choose a registry to upgrade.
Copy the CRN (Creator) shown in the AI Registries.
In the Cloudera CLI, enter cdp ml upgrade-model-registry --crn <crn>
In the AI Registries UI, the Status of the AI registry changes to Backup Initiated. The process starts provisioning a new registry (Status: Creating) and then performs a backup operation to restore the state.
When the new registry shows Ready, then in Actions, click Synchronize. Check the contents of the new registry to verify that all of the models have transferred.
Finally, after verifying the contents of the new registry, you can delete the old registry (check the Created at timestamp) in the Action menu. This action is irreversible.

To verify the data, go to a workbench. Check that all of the models are there. Deleting the old Cloudera AI registry cannot be reversed.

You should also check the event logs to see if any errors occurred during the upgrade. Can also be used real time to see that the process is running. If there is a need for an escalation ticket, make sure to include the logs.

If you upgrade a Cloudera AI registry, then synchronize, then rollback, any models that were added through synchronizing will not be present. The process does not transfer the data backwards to the old registry.

Upgrading a Cloudera AI Registry on an Azure UDR Private Cluster

When upgrading your Cloudera AI Registry in an Azure User-Defined Routing (UDR) setup, you must provide a different UDR-enabled subnet than the one used to create the Cloudera AI Registry. The system will not automatically reuse the original subnet that was configured for the pre-upgrade registry.

Upgrade Prerequisites for UDR-enabled AI Registries

For registries on version 1.10.0-b12 or higher: The upgrade functionality for UDR-enabled registries will work as described below. You can proceed with UI or CLI-based upgrade.
For registries on a version lower than 1.10.0-b12: You must first open a Cloudera support case.

Performing the Upgrade with a New Subnet

You can upgrade an Azure registry with a UDR-enabled subnet using either the UI or the CDP CLI.

Using the UI: When upgrading a registry using the UI, you must provide a UDR-enabled subnet that is not currently in use by the pre-upgrade registry or any other service.
Using the CLI: The same upgrade can be performed using the CDP CLI with a JSON input payload. This method also requires you to specify a new, unused UDR-enabled subnet.
Sample JSON payload for CLI upgrades:
Use the following template and replace the crn and subnets values with your own information.
```
{
    "crn": "crn:cdp:model_registry:us-west-1:c8dbde4b-ccce-4f8d-a581-830970ba4908:model_registry:e3f407cf-e4b3-45f1-bc5b-d471b5026058",
    "azureOptions": {
        "udrNetwork": {
            "topology": {
                "subnets": [
                    "mlx-dev-22"
                ]
            }
        }
    }
}
```
note
The crn must be the CRN of the registry you are upgrading. The mlx-dev-22 is the new subnet that must be distinct from the subnet used when you initially created the Cloudera AI Registry.