|
| 1 | +--- |
| 2 | +meta: |
| 3 | + title: Understanding automatic network hot-reconfiguration for Scaleway Instances |
| 4 | + description: Find out how to configure automatic network hot-reconfiguration for Scaleway Instances. |
| 5 | +content: |
| 6 | + h1: Understanding automatic network hot-reconfiguration for Scaleway Instances |
| 7 | + paragraph: Find out how to configure automatic network hot-reconfiguration for Scaleway Instances. |
| 8 | +categories: |
| 9 | + - compute |
| 10 | +dates: |
| 11 | + validation: 2024-10-29 |
| 12 | + posted: 2024-10-29 |
| 13 | +tags: instance network hot-reconfiguration |
| 14 | +--- |
| 15 | + |
| 16 | +The Scaleway Instances product includes a feature called **automatic network hot-reconfiguration**. |
| 17 | + |
| 18 | +This mechanism automatically configures or deconfigures a [flexible IP address](/compute/instances/concepts/#flexible-ip) in the guest operating system when it is attached to or detached from an Instance. |
| 19 | + |
| 20 | +This guide explains how to enable or disable the automatic network hot-reconfiguration mechanism on your Instance. |
| 21 | + |
| 22 | +<Message type="note"> |
| 23 | + This documentation page does not apply to Instances running the Microsoft Windows operating system. |
| 24 | +</Message> |
| 25 | + |
| 26 | +## Supported configurations |
| 27 | + |
| 28 | +Before proceeding, ensure that your operating system supports the target network configuration: refer to Scaleway’s compatibility guidelines on [OS images and flexible IP type combinations](/compute/instances/reference-content/comaptibility-scw-os-images-flexible-ip/). |
| 29 | + |
| 30 | +Starting from **October 10th, 2024**, all GNU/Linux-based operating systems and InstantApp images for Scaleway Instances have automatic network hot-reconfiguration enabled by default. |
| 31 | + |
| 32 | +To verify that the feature is active on your Instance, use the following command: |
| 33 | + |
| 34 | +```bash |
| 35 | +# systemctl is-active scw-net-reconfig.path |
| 36 | +``` |
| 37 | + |
| 38 | +If the output is `active`, the feature is enabled and ready to use. If the output is `inactive`, you have to enable it first. |
| 39 | + |
| 40 | + |
| 41 | +### Enabling network hot-reconfiguration |
| 42 | + |
| 43 | +Follow these steps to enable automatic network hot-reconfiguration on a Scaleway Instance where the feature is currently inactive. |
| 44 | + |
| 45 | +1. Enable the QEMU Guest Agent. Refer to Scaleway’s documentation on [enabling the QEMU Guest Agent (GQA)](compute/instances/reference-content/understanding-qemu-guest-agent/#opting-in) for further details. |
| 46 | + |
| 47 | +2. Install the latest Scaleway Ecosystem package. |
| 48 | + |
| 49 | + - **Fedora / AlmaLinux / RockyLinux / CentOS** |
| 50 | + ```bash |
| 51 | + # yum -y --best install scaleway-ecosystem |
| 52 | + ``` |
| 53 | + |
| 54 | + - **Debian / Ubuntu** |
| 55 | + ```bash |
| 56 | + # apt-get update |
| 57 | + # apt-get -y install scaleway-ecosystem |
| 58 | + ``` |
| 59 | + |
| 60 | + <Message type="note"> |
| 61 | + Ensure you install version `0.0.7-1` or higher of the `scaleway-ecosystem` package. |
| 62 | + </Message> |
| 63 | + |
| 64 | +3. Enable the Automatic Network Reconfiguration Mechanism. |
| 65 | + |
| 66 | + |
| 67 | + On Debian and Ubuntu systems, the mechanism typically activates automatically after installing or upgrading the `scaleway-ecosystem` package. However, RedHat-based distributions may require a manual start: |
| 68 | + |
| 69 | + ```bash |
| 70 | + # systemctl enable --now scw-net-reconfig.path |
| 71 | + ``` |
| 72 | + |
| 73 | + <Message type="note"> |
| 74 | + Rebooting your Instance will also activate the mechanism during boot. |
| 75 | + </Message> |
| 76 | + |
| 77 | +--- |
| 78 | + |
| 79 | +### Disabling network hot-reconfiguration |
| 80 | + |
| 81 | +If you prefer to prevent automatic network reconfiguration when a flexible IP is attached or detached, follow these steps: |
| 82 | + |
| 83 | +1. Run the following command to disable the feature: |
| 84 | + |
| 85 | + ```bash |
| 86 | + # systemctl disable --now scw-net-reconfig.path |
| 87 | + ``` |
0 commit comments