From 2b3cfb20b3f6351d6726d0d233757c89593d7baf Mon Sep 17 00:00:00 2001 From: Sanketh I Date: Thu, 25 Jul 2024 10:48:56 -0700 Subject: [PATCH 1/5] Update upgrade-nodes-csp.md --- .../yugabyte-platform/manage-deployments/upgrade-nodes-csp.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md b/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md index 4807903ce726..9a4d7749b0bb 100644 --- a/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md +++ b/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md @@ -49,6 +49,8 @@ If your universe uses a Linux version managed by YugabyteDB Anywhere, updated im If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to [Create cloud provider configuration](../../configure-yugabyte-platform/aws/). +It is recommended to verify that the selected cloud provider image can boot successfully on a standalone VM with the same instance type as the universe before initiating the upgrade. + ## Upgrade Linux version To apply operating system patch or upgrade, do the following: From 1b5a4059e05bf7c1ae857da033c0c5d206b27d30 Mon Sep 17 00:00:00 2001 From: Sanketh I Date: Thu, 25 Jul 2024 10:52:53 -0700 Subject: [PATCH 2/5] Update upgrade-nodes-csp.md --- .../yugabyte-platform/manage-deployments/upgrade-nodes-csp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md b/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md index 9a4d7749b0bb..c83c194e057f 100644 --- a/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md +++ b/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md @@ -49,7 +49,7 @@ If your universe uses a Linux version managed by YugabyteDB Anywhere, updated im If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to [Create cloud provider configuration](../../configure-yugabyte-platform/aws/). -It is recommended to verify that the selected cloud provider image can boot successfully on a standalone VM with the same instance type as the universe before initiating the upgrade. +Before upgrading the universe, it is recommended to verify that the selected cloud provider image can successfully boot on a standalone virtual machine (VM) with the same instance type as the universe. Create a new VM with the same instance type as the universe and the selected cloud provider image for the boot disk and verify that the VM can boot succesfully. ## Upgrade Linux version From 96aee73df33fe25db424af6bdf859c428c880b68 Mon Sep 17 00:00:00 2001 From: Sanketh I Date: Thu, 25 Jul 2024 10:53:10 -0700 Subject: [PATCH 3/5] Update upgrade-nodes-csp.md --- .../yugabyte-platform/manage-deployments/upgrade-nodes-csp.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md b/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md index c721132c8843..75cc7f3a1b14 100644 --- a/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md +++ b/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md @@ -49,6 +49,9 @@ If your universe uses a Linux version managed by YugabyteDB Anywhere, updated im If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to [Create cloud provider configuration](../../configure-yugabyte-platform/aws/). + +Before upgrading the universe, it is recommended to verify that the selected cloud provider image can successfully boot on a standalone virtual machine (VM) with the same instance type as the universe. Create a new VM with the same instance type as the universe and the selected cloud provider image for the boot disk and verify that the VM can boot succesfully. + ## Upgrade Linux version To apply operating system patch or upgrade, do the following: From 0f42efa0a7c4ba1e45931addc21fa611bb6f087c Mon Sep 17 00:00:00 2001 From: Sanketh I Date: Wed, 28 Aug 2024 11:47:15 -0700 Subject: [PATCH 4/5] Apply suggestions from code review Co-authored-by: Dwight Hodge <79169168+ddhodge@users.noreply.github.com> --- .../yugabyte-platform/manage-deployments/upgrade-nodes-csp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md b/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md index 75cc7f3a1b14..a4e766690334 100644 --- a/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md +++ b/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md @@ -50,7 +50,7 @@ If your universe uses a Linux version managed by YugabyteDB Anywhere, updated im If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to [Create cloud provider configuration](../../configure-yugabyte-platform/aws/). -Before upgrading the universe, it is recommended to verify that the selected cloud provider image can successfully boot on a standalone virtual machine (VM) with the same instance type as the universe. Create a new VM with the same instance type as the universe and the selected cloud provider image for the boot disk and verify that the VM can boot succesfully. +Before patching or upgrading the operating system, verify that the Linux version image that you intend to use can successfully run on a standalone virtual machine (VM) with the same instance type as the nodes you are patching. You can do this by creating a new VM with the same instance type as your universe and using the selected Linux version for the boot disk and verifying that the VM boots succesfully. ## Upgrade Linux version From 1503a04b7d2707d6abc3a7a1a5a0ffbedba563d7 Mon Sep 17 00:00:00 2001 From: Dwight Hodge Date: Wed, 28 Aug 2024 15:49:57 -0400 Subject: [PATCH 5/5] backport edits --- .../yugabyte-platform/manage-deployments/upgrade-nodes-csp.md | 3 +-- .../yugabyte-platform/manage-deployments/upgrade-nodes-csp.md | 2 +- .../yugabyte-platform/manage-deployments/upgrade-nodes-csp.md | 2 ++ 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md b/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md index a4e766690334..e377d4c5a657 100644 --- a/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md +++ b/docs/content/preview/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md @@ -49,8 +49,7 @@ If your universe uses a Linux version managed by YugabyteDB Anywhere, updated im If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to [Create cloud provider configuration](../../configure-yugabyte-platform/aws/). - -Before patching or upgrading the operating system, verify that the Linux version image that you intend to use can successfully run on a standalone virtual machine (VM) with the same instance type as the nodes you are patching. You can do this by creating a new VM with the same instance type as your universe and using the selected Linux version for the boot disk and verifying that the VM boots succesfully. +Before patching or upgrading the operating system, verify that the Linux version image that you intend to use can successfully run on a standalone virtual machine (VM) with the same instance type as the nodes you are patching. You can do this by creating a new VM with the same instance type as your universe and using the selected Linux version for the boot disk and verifying that the VM boots successfully. ## Upgrade Linux version diff --git a/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md b/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md index c83c194e057f..39feb049fc75 100644 --- a/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md +++ b/docs/content/stable/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md @@ -49,7 +49,7 @@ If your universe uses a Linux version managed by YugabyteDB Anywhere, updated im If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to [Create cloud provider configuration](../../configure-yugabyte-platform/aws/). -Before upgrading the universe, it is recommended to verify that the selected cloud provider image can successfully boot on a standalone virtual machine (VM) with the same instance type as the universe. Create a new VM with the same instance type as the universe and the selected cloud provider image for the boot disk and verify that the VM can boot succesfully. +Before patching or upgrading the operating system, verify that the Linux version image that you intend to use can successfully run on a standalone virtual machine (VM) with the same instance type as the nodes you are patching. You can do this by creating a new VM with the same instance type as your universe and using the selected Linux version for the boot disk and verifying that the VM boots successfully. ## Upgrade Linux version diff --git a/docs/content/v2.20/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md b/docs/content/v2.20/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md index 8f776cc4c2d4..8865a5be4144 100644 --- a/docs/content/v2.20/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md +++ b/docs/content/v2.20/yugabyte-platform/manage-deployments/upgrade-nodes-csp.md @@ -49,6 +49,8 @@ If your universe uses a Linux version managed by YugabyteDB Anywhere, updated im If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to [Create cloud provider configuration](../../configure-yugabyte-platform/set-up-cloud-provider/aws/). +Before patching or upgrading the operating system, verify that the Linux version image that you intend to use can successfully run on a standalone virtual machine (VM) with the same instance type as the nodes you are patching. You can do this by creating a new VM with the same instance type as your universe and using the selected Linux version for the boot disk and verifying that the VM boots successfully. + ## Upgrade Linux version To apply operating system patch or upgrade, do the following: