Differences

This shows you the differences between two versions of the page.

--- en:services:server_services:virtual_server:intel_cluster [2022/11/22 15:20] – [Objection to or Rescheduling of the Migration] trippin
+++ en:services:server_services:virtual_server:intel_cluster [2023/02/14 10:48] (current) – removed trippin
@@ Line 1: / Line 1: @@
-====== Information: Migration of VMs from Intel clusters ======
-This page is only a documentation of the migration of VMs from Intel clusters to AMD cluster and is not relevant for the regular VM operation.
-Following clusters are affected:
-  * Silber-2
-  * SilberAlt
-  * SilberHP
-  * SilberIntel
-===== Determine VM Cluster =====
-If VMs are located in the above clusters, identifying them is quite simple:
-  - open the vCenter
-  - select the "Hosts and Clusters" view (the first icon above the inventory list)
-  - expand the object "vcenter2.vm.gwdg.de" and below it the object "GWDG
-  - collapse all clusters not mentioned above and open the clusters mentioned above (if visible)
-  - all VMs you see now are affected by the migration with downtime
-If none of the above mentioned clusters are visible, make sure that the view "Hosts and Clusters" is really selected, if you see one or more clusters but none of the above mentioned is there, all your VMs are already on a cluster with AMD hosts or in another cluster and are not affected or will be affected in another phase.
-^ Select Host und Cluster View ^ Expand / Collapse Cluster ^
-| {{ :en:services:server_services:virtual_server:selecthostsandclusters_en.png?nolink&450 |}} | {{ :en:services:server_services:virtual_server:listintelvms_en.png?nolink&450 |}} |
-==== Alternatives Procedure ====
-Alternatively, you can check each VM individually.
-  - open the vCenter
-  - select the VM you want to check
-  - select the "Overview" tab in the VM view
-  - look for the tile "Related Objects"
-  - expand the tile using the arrow to the right of the title if necessary
-  - check if the VM is located in an affected cluster
-^ Kachel "Verwandte Objekte" auf VM Übersichtsseite ^
-| {{ :en:services:server_services:virtual_server:singleintelvm_en.png?nolink&650 |}} |
-===== Objection to or Rescheduling of the Migration =====
-A general objection is not possible, the existing Intel hosts are mostly decommissioned soon.
-If for urgent reasons a migration of certain VMs is not possible on the date specified in the email or if certain VMs are critical systems, please contact **__as soon as possible__** and **__only__** via mail to [[vmware@gwdg.de?subject=VM-Migration&body=For%20the%20following%20reason%20I%20ask%20to%20move%20the%20migration%20of%20the%20VMs%20listed%20in%20the%20attached%20.txt%20file%20to the%20....%0A-%20...%0A%0A | vmware@gwdg.de]].
-  * Please create one .txt file for each alternate date.
-  * Specify the desired date of migration in the file name in the format yymmdd.txt (for 12/15/2022 e.g.: 221215.txt).
-  * Please list the full VM names exactly as in the vCenter inventory.
-  * Please use a separate line for each VM.
-  * If VMs that are not to be migrated on the regular date are pinned to a location, please point this out in the email.
-===== Exceptions from Migration =====
-VMs that have at least one of the following requirements are exempt:
-  * Software on the VM needs access to SSE and/or AVX instructions.
-    * If these instructions have to be used, this is known to the VM admins in most cases.
-  * Software on the VM necessarily requires an Intel CPU.
-  * VMs that use CARP.
-    * This is known to the VM admins in all cases.