From 3ec7c4c5e0294e348f4dfb9cf6c3a38c5e73c2ea Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 14 Nov 2024 14:00:26 +0100 Subject: [PATCH 1/3] fix(ins): update instructions for scaleway-ecosystem --- .../instances/how-to/migrate-routed-ips.mdx | 26 +++++++++++++++---- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 5beaed7229..1d78150de3 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to move your Instance to routed flexible IPs tags: instance flexible ip routed dates: - validation: 2024-00-16 + validation: 2024-11-14 posted: 2023-10-11 categories: - compute @@ -33,19 +33,35 @@ Using a routed flexible IP is recommended for all compatible Instance types, as ## Updating the required packages -To update the `scaleway-ecosystem` and `cloud-init` packages, [log into your Instance using SSH](/compute/instances/how-to/connect-to-instance/) and run the following command. + + To ensure optimal compatibility and security, especially when working with flexible IPs, we recommend to upgrade your Instance to OS versions that have not reached their end of life. + + +Before proceeding with the migration, consider the following guidelines regarding `scaleway-ecosystem` and `cloud-init`: + +- **Necessity of `scaleway-ecosystem` and `cloud-init`:** These packages are not strictly required for routed IPs. However, if they are installed, it is recommended to update them to the latest version. +- Package availability on older Instances: + - `scaleway-ecosystem`: Older Instances may not have this package installed. In such cases, no action is required. + - `cloud-init`: This package is commonly pre-installed on Instances due to its inclusion in upstream cloud images. For older Instances, a legacy version of `cloud-init` may not impact IPv4 functionality, but IPv6 functionality could be inconsistent with outdated versions. + +To check if `scaleway-ecosystem` and `cloud-init` are installed and to update them if needed, [log into your Instance using SSH](/compute/instances/how-to/connect-to-instance/) and run the following commands: -* For Ubuntu and Debian Instances, you can use the following command: +* For **Ubuntu and Debian** Instances: ```bash + dpkg -l | grep scaleway-ecosystem || echo "scaleway-ecosystem is not installed" apt upgrade scaleway-ecosystem cloud-init -y ``` -* For CentOS and Fedora Instances, you can use the following command: +* For **CentOS and Fedora** Instances: ```bash + rpm -qa | grep scaleway-ecosystem || echo "scaleway-ecosystem is not installed" dnf update scaleway-ecosystem cloud-init -y ``` - + +If `scaleway-ecosystem` is not installed, no additional steps are needed for this package. However, it is still recommended to ensure that `cloud-init` is up-to-date to support IPv6 functionality. + ## Moving the Instance to routed IPs + 1. Select **Instances** from the **Compute** category in the sidebar menu. This will show a list of your Instances. Those eligible to transition to routed IPs are identified with an exclamation mark icon. 2. Click **Move IP** next to the Instance you wish to move to routed flexible IPs. A pop-up displays. From e95e7e2d0f4bc5305d3209dfd41af1d68664e0e3 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 14 Nov 2024 14:02:19 +0100 Subject: [PATCH 2/3] fix(ins): wording --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 1d78150de3..8e52253685 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -39,7 +39,7 @@ Using a routed flexible IP is recommended for all compatible Instance types, as Before proceeding with the migration, consider the following guidelines regarding `scaleway-ecosystem` and `cloud-init`: -- **Necessity of `scaleway-ecosystem` and `cloud-init`:** These packages are not strictly required for routed IPs. However, if they are installed, it is recommended to update them to the latest version. +- `scaleway-ecosystem` and `cloud-init`: These packages are not strictly required for routed IPs. However, if they are installed, it is recommended to update them to the latest version. - Package availability on older Instances: - `scaleway-ecosystem`: Older Instances may not have this package installed. In such cases, no action is required. - `cloud-init`: This package is commonly pre-installed on Instances due to its inclusion in upstream cloud images. For older Instances, a legacy version of `cloud-init` may not impact IPv4 functionality, but IPv6 functionality could be inconsistent with outdated versions. From fbe95debe6b643fcaf5368c1b7a0b0eff784f693 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 14 Nov 2024 14:44:19 +0100 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: Fabien Malfoy --- compute/instances/how-to/migrate-routed-ips.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 8e52253685..ba61d95fe0 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -48,13 +48,13 @@ To check if `scaleway-ecosystem` and `cloud-init` are installed and to update th * For **Ubuntu and Debian** Instances: ```bash - dpkg -l | grep scaleway-ecosystem || echo "scaleway-ecosystem is not installed" + dpkg-query -W scaleway-ecosystem || echo "scaleway-ecosystem is not installed" apt upgrade scaleway-ecosystem cloud-init -y ``` * For **CentOS and Fedora** Instances: ```bash - rpm -qa | grep scaleway-ecosystem || echo "scaleway-ecosystem is not installed" + rpm -q scaleway-ecosystem || echo "scaleway-ecosystem is not installed" dnf update scaleway-ecosystem cloud-init -y ```