Fix DRS link bad title

ovh · Jul 25, 2024 · 845a90b · 845a90b
1 parent 9562f9c
commit 845a90b
Show file tree

Hide file tree

Showing 15 changed files with 15 additions and 15 deletions.
diff --git a/...d/hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.de-de.md b/...d/hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.de-de.md
@@ -61,7 +61,7 @@ The table below lists each of the migration bottlenecks and criticality levels t
 |-------------|--------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | **Step 1** | ⚠️ ⚠️ ⚠️ | **Multi-vDC** | Migrate VMs, vApp to a single datacentre. | - Can only be migrated if it has only one data centre in a vSphere managed on OVHcloud. If not, make sure to migrate your data in the datacenter that will be migrated. | [Migrating an infrastructure to a new vDC](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/service-migration-vdc) | 
 | **Step 2** | ⚠️⚠️ | **VMware vSphere FT (fault tolerance)** | Disable VMware vSphere FT from VMs. | | [VMware Fault Tolerance](/pages/bare_metal_cloud/managed_bare_metal/vmware_fault_tolerance) | 
-| **Step 3** | ️⚠️⚠️ | **DRS affinity/anti-affinity** | Reconstitution of affinity/anti-affinity rules in VCD. | - To be retained, DRS affinity/anti-affinity rules will have to be manually recreated by you in VCD on OVHcloud after migration. | [VMware DRS distributed resource scheduler](/pages/bare_metal_cloud/managed_bare_metal/vmware_drs_distributed_resource_scheduler) | 
+| **Step 3** | ️⚠️⚠️ | **DRS affinity/anti-affinity** | Reconstitution of affinity/anti-affinity rules in VCD. | - To be retained, DRS affinity/anti-affinity rules will have to be manually recreated by you in VCD on OVHcloud after migration. | [VMware DRS (Distributed Ressource Scheduler)](/pages/bare_metal_cloud/managed_bare_metal/vmware_drs_distributed_resource_scheduler) | 
 | **Step 4** | ⚠️⚠️ | **Special devices (CD, DVD etc..)** | Unplug all special devices. | - Nothing must be plugged into to migrated vSphere managed data centers. All special devices (CD, DVD etc..) must be removed before migration, otherwise they will be force-removed by the migration process and lost. | | 
 | **Step 5** | ⚠️⚠️ | **Datastore clusters** | Delete all clustering rules. | - Clustering rules will have to be deleted before migration because this notion do not exist on the VCD side. | | 
 | **Step 6** | ⚠️ | **Memory over-commitment** | Plan or scale your resource requirements in VCD (control panel VCD side). <br/> Or optimize your requirements before migrating (control panel vSphere side). | - Because you won't be able to over-commit resources on the VCD side, this concept does not exist. | [Modifying virtual machine resources](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/modify_hardware_configuration_of_vm) | 

diff --git a/...hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.en-asia.md b/...hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.en-asia.md
@@ -61,7 +61,7 @@ The table below lists each of the migration bottlenecks and criticality levels t
 |-------------|--------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | **Step 1** | ⚠️ ⚠️ ⚠️ | **Multi-vDC** | Migrate VMs, vApp to a single datacentre. | - Can only be migrated if it has only one data centre in a vSphere managed on OVHcloud. If not, make sure to migrate your data in the datacenter that will be migrated. | [Migrating an infrastructure to a new vDC](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/service-migration-vdc) | 
 | **Step 2** | ⚠️⚠️ | **VMware vSphere FT (fault tolerance)** | Disable VMware vSphere FT from VMs. | | [VMware Fault Tolerance](/pages/bare_metal_cloud/managed_bare_metal/vmware_fault_tolerance) | 
-| **Step 3** | ️⚠️⚠️ | **DRS affinity/anti-affinity** | Reconstitution of affinity/anti-affinity rules in VCD. | - To be retained, DRS affinity/anti-affinity rules will have to be manually recreated by you in VCD on OVHcloud after migration. | [VMware DRS distributed resource scheduler](/pages/bare_metal_cloud/managed_bare_metal/vmware_drs_distributed_resource_scheduler) | 
+| **Step 3** | ️⚠️⚠️ | **DRS affinity/anti-affinity** | Reconstitution of affinity/anti-affinity rules in VCD. | - To be retained, DRS affinity/anti-affinity rules will have to be manually recreated by you in VCD on OVHcloud after migration. | [VMware DRS (Distributed Ressource Scheduler)](/pages/bare_metal_cloud/managed_bare_metal/vmware_drs_distributed_resource_scheduler) | 
 | **Step 4** | ⚠️⚠️ | **Special devices (CD, DVD etc..)** | Unplug all special devices. | - Nothing must be plugged into to migrated vSphere managed data centers. All special devices (CD, DVD etc..) must be removed before migration, otherwise they will be force-removed by the migration process and lost. | | 
 | **Step 5** | ⚠️⚠️ | **Datastore clusters** | Delete all clustering rules. | - Clustering rules will have to be deleted before migration because this notion do not exist on the VCD side. | | 
 | **Step 6** | ⚠️ | **Memory over-commitment** | Plan or scale your resource requirements in VCD (control panel VCD side). <br/> Or optimize your requirements before migrating (control panel vSphere side). | - Because you won't be able to over-commit resources on the VCD side, this concept does not exist. | [Modifying virtual machine resources](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/modify_hardware_configuration_of_vm) |