An error occurred while using the Shift Toolkit, and I am unable to migrate the VM. Problem Summary: I installed the Shift Toolkit on a Windows environment. After logging in, I followed the steps outlined in the documentation and successfully completed Step 1, "Register Source and Destination," and Step 2, "Create Resource Group." However, when I attempted to execute Step 3, "Create Blueprint," the "Configure Cluster and Host Mappings" screen did not display the "Source Resources" or "Destination Resources" options that require selection. Clicking "Continue" triggers an error, and I cannot proceed to the next step. What are the possible causes of this issue? The tested environment is as follows: Source: VMware vSphere (vCenter Server 8.0.3, VMware ESXi 8.0.3) Destination: PROXMOX Virtual Environment 9.1.1 ONTAP: ONTAP 9.17.1P6 (AFF A20) – Source VM deployed on an NFSv3 storage pool configured as a qtree We are using Shift Toolkit 7.1. We tested this in both the virtual environment and an on-premises Windows environment, and the results were the same. Thank you for your assistance. ... View more

Hi All,   We are trying to run some test migrations from VMW to OCP.   However our efforts fail.   Specifically, we have TBC configured in our OCP cluster and configured both source (VMW) and destination (OCP).   Toolkit, recognizes 1 TBC in the destination (OCP) but zero storage.   When we try to create a resource group towards a blueprint, we get the following error   Failed to get TBC information Show less Failed to get TBC information: ESSRGMTV003: Unsupported volume "vm_tst_data001" for migration. No supporting Trident backend configuration found.     We have the following questions: Does Shift Toolkit requires direct API access to the NetApp storage itself? What is counted as "storage" for OCP in the Toolkit? It looks to us that TBC is the OCP storage and that should be fine. What does the above error message actually mean? Is it a problem of the source (VMW) or of the destination (OCP) and what is the problem? Attaching some related screenshots.   Best regards,   Theo   ... View more

Hi Team, In our Kubernetes (K8s) environment, each application team is assigned their own namespace, and they deploy their own pods within it. While testing the NetApp Trident integration, we observed the following and would appreciate your feedback on how we can address these concerns: Tenant A provisions a PersistentVolumeClaim (PVC) named pvc1. How does the system ensure that Tenant B cannot access pvc1 or its underlying PersistentVolume (PV)? What security mechanisms are in place (e.g., namespace isolation, RBAC, storage-level encryption, etc.) to enforce tenant isolation and prevent unauthorized access? Are there any best practices to enhance security in a multi-tenant Kubernetes environment using NetApp Trident?   In our current setup, PVCs are namespace-scoped, and each application team has access only to their respective namespace. Looking forward to your input. Thanks ... View more

VDI and PC Cloud need to be storage on super speed and strong storage system. How we can speed the adoption to use super fast Virtual Machine to deploy a Desktop on premise and Cloud Services. ... View more