Skip to content

fix(ins): update instructions for scaleway-ecosystem #3978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 14, 2024
Merged

fix(ins): update instructions for scaleway-ecosystem #3978

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3ec7c4c
fix(ins): update instructions for scaleway-ecosystem
bene2k1 Nov 14, 2024
e95e7e2
fix(ins): wording
bene2k1 Nov 14, 2024
fbe95de
Apply suggestions from code review
bene2k1 Nov 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 21 additions & 5 deletions compute/instances/how-to/migrate-routed-ips.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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.
<Message type="tip">
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.
<Message>

Before proceeding with the migration, consider the following guidelines regarding `scaleway-ecosystem` and `cloud-init`:

- `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-query -W 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 -q 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.
<Lightbox src="scaleway-instance-routedip-transition.webp" alt="" />
2. Click **Move IP** next to the Instance you wish to move to routed flexible IPs. A pop-up displays.
Expand Down
Loading