From 76e54ad8b697f623930fbb41197e221c07a85eb7 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Fri, 8 Jan 2021 17:01:09 +0530 Subject: [PATCH 01/12] vm: fix display name, internal name notes Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index fd1bd1a752..93e24307ec 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -347,14 +347,14 @@ scenarios. .. cssclass:: table-striped table-bordered table-hover -============================= ======================= ==================== ===================================== ========================== -User-Provided Display Name vm.instancename.flag Hostname on the VM Name on vCenter Internal Name -============================= ======================= ==================== ===================================== ========================== -Yes True Display name i---displayName i---displayName -No True UUID i--- i--- -Yes False Display name i--- i--- -No False UUID i--- i--- -============================= ======================= ==================== ===================================== ========================== +============================= ======================= ====================== ====================== ====================== ===================================== ========================== +User-Provided Display Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name +============================= ======================= ====================== ====================== ====================== ===================================== ========================== +Yes True Name Display name Name i---name i---name +No True - - - i--- - +Yes False Name Display name Name i--- i--- +No False - - - i--- i--- +============================= ======================= ====================== ====================== ====================== ===================================== ========================== Changing the Service Offering for a VM From d6f41e3b1ba88c91d497a115e3c9ca73f5e945fa Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Wed, 13 Jan 2021 12:57:56 +0530 Subject: [PATCH 02/12] fix Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 26 ++++++-------------------- 1 file changed, 6 insertions(+), 20 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 93e24307ec..83713047e2 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -322,28 +322,14 @@ To access a VM through the CloudStack UI: #. Click Apply. -Appending a Display Name to the Guest VM’s Internal Name +Appending VM Name to the Guest VM’s Internal Name ---------------------------------------------------------- -Every guest VM has an internal name. The host uses the internal name to -identify the guest VMs. CloudStack gives you an option to provide a -guest VM with a display name. You can set this display name as the -internal name so that the vCenter can use it to identify the guest VM. A -new global parameter, vm.instancename.flag, has now been added to -achieve this functionality. - -The default format of the internal name is -i---, where instance.name is a global -parameter. However, If vm.instancename.flag is set to true, and if a -display name is provided during the creation of a guest VM, the display -name is appended to the internal name of the guest VM on the host. This -makes the internal name format as i---. -The default value of vm.instancename.flag is set to false. This feature -is intended to make the correlation between instance names and internal -names easier in large data center deployments. - -The following table explains how a VM name is displayed in different -scenarios. +Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a name. You can set this name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality. + +The default format of the internal name is i---, where instance.name is a global parameter. However, If vm.instancename.flag is set to true, and if a name is provided during the creation of a guest VM, the name is appended to the internal name of the guest VM on the host. This makes the internal name format as i---. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments. + +The following table explains how a VM name is displayed in different scenarios. .. cssclass:: table-striped table-bordered table-hover From 6688f7e910683b0f1e5214a69af16439794691f8 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Thu, 14 Jan 2021 12:06:44 +0530 Subject: [PATCH 03/12] revert heading Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 83713047e2..202ae0614c 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -322,7 +322,7 @@ To access a VM through the CloudStack UI: #. Click Apply. -Appending VM Name to the Guest VM’s Internal Name +Appending a Display Name to the Guest VM’s Internal Name ---------------------------------------------------------- Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a name. You can set this name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality. From b34382902b223d2f3aa9ec88c1dee58388062b9a Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Wed, 27 Jan 2021 14:14:24 +0530 Subject: [PATCH 04/12] use brackets Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 202ae0614c..2196dd5275 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -336,9 +336,9 @@ The following table explains how a VM name is displayed in different scenarios. ============================= ======================= ====================== ====================== ====================== ===================================== ========================== User-Provided Display Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name ============================= ======================= ====================== ====================== ====================== ===================================== ========================== -Yes True Name Display name Name i---name i---name +Yes True i--- i--- No True - - - i--- - -Yes False Name Display name Name i--- i--- +Yes False i--- i--- No False - - - i--- i--- ============================= ======================= ====================== ====================== ====================== ===================================== ========================== From 88f3d307919b491cde327735d592a93b7212f0d9 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Wed, 27 Jan 2021 14:19:45 +0530 Subject: [PATCH 05/12] change display name to name Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 2196dd5275..290cc56fdc 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -322,8 +322,8 @@ To access a VM through the CloudStack UI: #. Click Apply. -Appending a Display Name to the Guest VM’s Internal Name ----------------------------------------------------------- +Appending a Name to the Guest VM’s Internal Name +------------------------------------------------ Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a name. You can set this name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality. @@ -333,14 +333,14 @@ The following table explains how a VM name is displayed in different scenarios. .. cssclass:: table-striped table-bordered table-hover -============================= ======================= ====================== ====================== ====================== ===================================== ========================== -User-Provided Display Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name -============================= ======================= ====================== ====================== ====================== ===================================== ========================== -Yes True i--- i--- -No True - - - i--- - -Yes False i--- i--- -No False - - - i--- i--- -============================= ======================= ====================== ====================== ====================== ===================================== ========================== +===================== ======================= ====================== ====================== ====================== ===================================== ========================== +User-Provided Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name +===================== ======================= ====================== ====================== ====================== ===================================== ========================== +Yes True i--- i--- +No True - - - i--- - +Yes False i--- i--- +No False - - - i--- i--- +===================== ======================= ====================== ====================== ====================== ===================================== ========================== Changing the Service Offering for a VM From bdcd39e1b0440bffab54d9bfaf7a614757143fce Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Thu, 28 Jan 2021 14:05:27 +0530 Subject: [PATCH 06/12] fix Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 290cc56fdc..3aa466c291 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -337,7 +337,7 @@ The following table explains how a VM name is displayed in different scenarios. User-Provided Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name ===================== ======================= ====================== ====================== ====================== ===================================== ========================== Yes True i--- i--- -No True - - - i--- - +No True - - - - i--- Yes False i--- i--- No False - - - i--- i--- ===================== ======================= ====================== ====================== ====================== ===================================== ========================== From 0f1c1183458c313481de1e6bd3940138ad07fd4f Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Thu, 4 Feb 2021 13:52:08 +0530 Subject: [PATCH 07/12] table formatting Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 31 ++++++++++++++++++-------- 1 file changed, 22 insertions(+), 9 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 3aa466c291..9332c14580 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -327,20 +327,33 @@ Appending a Name to the Guest VM’s Internal Name Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a name. You can set this name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality. -The default format of the internal name is i---, where instance.name is a global parameter. However, If vm.instancename.flag is set to true, and if a name is provided during the creation of a guest VM, the name is appended to the internal name of the guest VM on the host. This makes the internal name format as i---. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments. +The default format of the internal name is i---, where i.n is the value global configuration - instance.name. However, If vm.instancename.flag is set to true, and if a name is provided during the creation of a guest VM, the name is appended to the internal name of the guest VM on the host. This makes the internal name format as i---. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments. The following table explains how a VM name is displayed in different scenarios. .. cssclass:: table-striped table-bordered table-hover -===================== ======================= ====================== ====================== ====================== ===================================== ========================== -User-Provided Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name -===================== ======================= ====================== ====================== ====================== ===================================== ========================== -Yes True i--- i--- -No True - - - - i--- -Yes False i--- i--- -No False - - - i--- i--- -===================== ======================= ====================== ====================== ====================== ===================================== ========================== +======================== ============================ =========================== =========================== =========================== +**User-Provided Name** Yes No Yes No +**vm.instancename.flag** True True False False +**Name** - - +**Display Name** - - +**Hostname on the VM** - - +**Name on vCenter** i--- - i--- i--- +**Internal Name** i--- i--- i--- i--- +======================== ============================ =========================== =========================== =========================== + +================== ==================== ============ ============== ================== ============================ ============================ +User-Provided Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name +================== ==================== ============ ============== ================== ============================ ============================ +Yes True i--- i--- +No True - - - - i--- +Yes False i--- i--- +No False - - - i--- i--- +================== ==================== ============ ============== ================== ============================ ============================ + + .. note:: + represents the value of global configuration - instance.name Changing the Service Offering for a VM From f68b48d5dd2a72a0397ead26fbac35b91eefb199 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Thu, 4 Feb 2021 14:06:02 +0530 Subject: [PATCH 08/12] fix Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 9332c14580..65c9964e08 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -344,7 +344,7 @@ The following table explains how a VM name is displayed in different scenarios. ======================== ============================ =========================== =========================== =========================== ================== ==================== ============ ============== ================== ============================ ============================ -User-Provided Name vm.instancename.flag User Display Name Hostname on the VM Name on vCenter Internal Name +User-Provided Name vm.instancename.flag Name Display Name Hostname on the VM Name on vCenter Internal Name ================== ==================== ============ ============== ================== ============================ ============================ Yes True i--- i--- No True - - - - i--- From af2eb068678c5fd4f05267f9f484051d10e9e8ce Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Thu, 4 Feb 2021 14:16:31 +0530 Subject: [PATCH 09/12] fix Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 65c9964e08..a807b062e8 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -38,8 +38,8 @@ names can be controlled by the user: .. note:: You can append the display name of a guest VM to its internal name. - For more information, see `“Appending a Display Name to the Guest VM’s - Internal Name” <#appending-a-display-name-to-the-guest-vms-internal-name>`_. + For more information, see `“Appending a Name to the Guest VM’s + Internal Name” <#appending-a-name-to-the-guest-vms-internal-name>`_. Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is monitored by the system. If the system detects that the VM is @@ -343,15 +343,6 @@ The following table explains how a VM name is displayed in different scenarios. **Internal Name** i--- i--- i--- i--- ======================== ============================ =========================== =========================== =========================== -================== ==================== ============ ============== ================== ============================ ============================ -User-Provided Name vm.instancename.flag Name Display Name Hostname on the VM Name on vCenter Internal Name -================== ==================== ============ ============== ================== ============================ ============================ -Yes True i--- i--- -No True - - - - i--- -Yes False i--- i--- -No False - - - i--- i--- -================== ==================== ============ ============== ================== ============================ ============================ - .. note:: represents the value of global configuration - instance.name From d758b7cd45b41c19bb368723da94955883feda81 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Fri, 5 Feb 2021 12:08:56 +0530 Subject: [PATCH 10/12] fix Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index a807b062e8..a4ca043838 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -323,11 +323,11 @@ To access a VM through the CloudStack UI: Appending a Name to the Guest VM’s Internal Name ------------------------------------------------- +-------------------------------------------------- Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a name. You can set this name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality. -The default format of the internal name is i---, where i.n is the value global configuration - instance.name. However, If vm.instancename.flag is set to true, and if a name is provided during the creation of a guest VM, the name is appended to the internal name of the guest VM on the host. This makes the internal name format as i---. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments. +The default format of the internal name is i---, where i.n is the value of the global configuration - instance.name. However, If vm.instancename.flag is set to true, and if a name is provided during the creation of a guest VM, the name is appended to the internal name of the guest VM on the host. This makes the internal name format as i---. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments. The following table explains how a VM name is displayed in different scenarios. From 5d7ff20d0387f9f8b3878e98d13406893295e3a8 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Fri, 5 Feb 2021 12:15:11 +0530 Subject: [PATCH 11/12] changes --- source/adminguide/virtual_machines.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index a4ca043838..e44b2bbe9d 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -38,7 +38,7 @@ names can be controlled by the user: .. note:: You can append the display name of a guest VM to its internal name. - For more information, see `“Appending a Name to the Guest VM’s + For more information, see `“Appending a Name to the Guest VM’s Internal Name” <#appending-a-name-to-the-guest-vms-internal-name>`_. Guest VMs can be configured to be Highly Available (HA). An HA-enabled @@ -344,7 +344,7 @@ The following table explains how a VM name is displayed in different scenarios. ======================== ============================ =========================== =========================== =========================== .. note:: - represents the value of global configuration - instance.name + represents the value of the global configuration - instance.name Changing the Service Offering for a VM From 1cb84c90415823c7fad59c7bfb3ab773a9937030 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Sat, 27 Mar 2021 11:24:50 +0530 Subject: [PATCH 12/12] fix Signed-off-by: Abhishek Kumar --- source/adminguide/virtual_machines.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index e44b2bbe9d..4879304540 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -327,21 +327,21 @@ Appending a Name to the Guest VM’s Internal Name Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a name. You can set this name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality. -The default format of the internal name is i---, where i.n is the value of the global configuration - instance.name. However, If vm.instancename.flag is set to true, and if a name is provided during the creation of a guest VM, the name is appended to the internal name of the guest VM on the host. This makes the internal name format as i---. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments. +The default format of the internal name is i---, where i.n is the value of the global configuration - instance.name. However, If vm.instancename.flag is set to true, and if a name is provided during the creation of a guest VM, the name is appended to the internal name of the guest VM on the host. This makes the internal name format as i---. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments. The following table explains how a VM name is displayed in different scenarios. .. cssclass:: table-striped table-bordered table-hover -======================== ============================ =========================== =========================== =========================== -**User-Provided Name** Yes No Yes No -**vm.instancename.flag** True True False False -**Name** - - -**Display Name** - - -**Hostname on the VM** - - -**Name on vCenter** i--- - i--- i--- -**Internal Name** i--- i--- i--- i--- -======================== ============================ =========================== =========================== =========================== +======================== =============================== ============================== ============================== =========================== +**User-Provided Name** Yes No Yes No +**vm.instancename.flag** True True False False +**Name** - - +**Display Name** - - +**Hostname on the VM** - - +**Name on vCenter** i--- - i--- i--- +**Internal Name** i--- i--- i--- i--- +======================== =============================== ============================== ============================== =========================== .. note:: represents the value of the global configuration - instance.name