fix(ipam): modify attach mode for custom resources

pages/elastic-metal/how-to/use-private-networks.mdx

@@ -52,7 +52,7 @@ You can choose to enable the Private Networks feature during the [creation of yo
 
 You can attach/detach Elastic Metal servers to a Private Network from either the Elastic Metal section of the console, or the VPC section.
 
-You can also reserve IP addresses with IPAM and attach them to specific MAC addresses, to facilitate the attachment of virtual machines hosted on your server, to Private Networks. See the IPAM documentation on [reserving a private IP with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address) for more information.
+You can also attach custom resources, such as virtual machines hosted on your Elastic Metal server, to Private Networks, by specifying their MAC addresses upon attachment. Follow the instructions for attaching such a resource in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn/).
 
 ### From the Elastic Metal section of the console
 

pages/ipam/faq.mdx

@@ -26,4 +26,4 @@ Currently, the Scaleway console only supports attachment with a reserved IP for
 
 ## Can I use a reserved private IP with a virtual machine hosted on my Elastic Metal server?
 
-Yes, this functionality is now available via the Scaleway console and API. See [how to reserve a private IP address with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address).
+Yes, this functionality is now available via the Scaleway console and API. Simply reserve an IP with IPAM, then select it when [attaching a custom resource to a Private Network](/vpc/how-to/attach-resources-to-pn/).

pages/ipam/how-to/reserve-ip.mdx

@@ -31,6 +31,8 @@ This page sets out the steps necessary to reserve an IP address with IPAM.
 
 ## How to reserve a private IP address
 
+The procedure is the same, whether you want to use the IP to attach a Scaleway-managed resource (Instance, Elastic Metal server etc.), or a custom resource (such as a VM hosted on an Elastic Metal server).
+
 1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
 
 2. Click **Reserve private IP**. The following screen displays:
@@ -50,37 +52,11 @@ This page sets out the steps necessary to reserve an IP address with IPAM.
     Four IP addresses from each CIDR block are unavailable for reservation: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.255`.
     </Message>
 
-5. Define whether you want to attach a MAC address to the reserved IP. **Only do this for custom resources** e.g. virtual machines hosted on a Proxmox cluster on an Elastic Metal server. 
-
-    <Message type="important">
-    Do **not** attach a MAC address for reserved IPs you want to use with standard Scaleway resources such as Instances, Load Balancers or Elastic Metal servers themselves.
-    </Message>
-
-    For more help with attaching MAC addresses, [see below](#how-to-reserve-a-private-ip-address-with-an-attached-mac-address).
-
-6. Click **Reserve** to reserve the IP.
+5. Click **Reserve** to reserve the IP.
 
     The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](#how-to-release-a-reserved-private-ip-address) it.
 
-## How to reserve a private IP address with an attached MAC address
-
-When you reserve a private IP, you have the option to attach a MAC address to it. This allows you to use the IP with a custom resource e.g. virtual machines hosted on a Proxmox cluster on an Elastic Metal server. This functionality marks the final stage of replacing the now-deprecated static DHCP reservations via the Public Gateway.
-
-It is only possible to attach a MAC address during the IP reservation. You cannot edit an existing reserved IP to attach a MAC address.
-
-1. Follow the steps above to [reserve a private IP](#how-to-reserve-a-private-ip-address), and at step 5, check the box to attach a MAC address.
-
-2. Enter the MAC address of the custom resource you want to attach, e.g. `00:1B:44:11:3A:B7`.
-
-3. Enter the name of the resource. This will be used for DNS resolution on the Private Network.
-
-4. Click **Reserve**.
-
-    The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. 
-
-    If you later attach this reserved IP address to a standard Scaleway resource e.g. an Instance, the attached MAC address and resource name will be erased.
-
-## How to attach a resource to a Private Network using a reserved IP address
+## How to attach a managed resource to a Private Network using a reserved IP address
 
 You can currently attach **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** to Private Networks using a reserved IP address. Support for Managed Databases will be coming soon.
 
@@ -92,6 +68,12 @@ The option to use a reserved IP displays when you attach the resource to a Priva
 - Attach a Load Balancer to a Private Network from the [Load Balancer](/load-balancer/how-to/use-with-private-network/) product dashboard
 - Attach a Public Gateway to a Private Network from the [Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) product dashboard
 
+## How to attach a custom resource to a Private Network using a reserved IP address
+
+You can use reserved IP addresses to attach custom resources, such as VMs hosted on Elastic Metal servers, to Scaleway Private Networks. In doing so, you are prompted to specify the MAC address of the custom resource.
+
+Attach the custom resource from the Private Network's dashboard in the Scaleway console, by following the procedure detailed in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn/).
+
 ## How to release a reserved private IP address
 
 You can release a reserved IP address, as long as it is not attached to a resource. Releasing the IP means it goes back into the general pool of available IP addresses for that Private Network, and could potentially be auto-allocated to a new resource joining the network.

pages/ipam/quickstart.mdx

@@ -61,6 +61,8 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre
 
 ## How to reserve a private IP address
 
+The procedure is the same, whether you want to use the IP to attach a Scaleway-managed resource (Instance, Elastic Metal server etc.), or a custom resource (such as a VM hosted on an Elastic Metal server).
+
 1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
 
 2. Click **Reserve private IP**. The following screen displays:
@@ -80,4 +82,6 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre
     Four IP addresses from each CIDR block are unavailable for reservation: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.255`.
     </Message>
 
-    The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address) it.
+5. Click **Reserve** to reserve the IP.
+
+    The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](#how-to-release-a-reserved-private-ip-address) it.

pages/ipam/reference-content/ipv6.mdx

@@ -71,7 +71,7 @@ In addition to the possibility of attaching and detaching flexible IP addresses,
 
 When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network.  You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use.
 
-You can also use IPAM's [reserve a private IP](https://www.scaleway.com/en/developers/api/ipam/#path-ips-reserve-a-new-ip) and [attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-ip-to-custom-resource) feature to attach an IPv6 address to a named resource via its MAC address. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
+To attach resources such as virtual machines hosted Elastic Metal servers to Private Networks, use the [attach custom resource](/vpc/how-to/attach-resources-to-pn/) feature, specifying the MAC address of the custom resource. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
 
 #### Going further
 

pages/vpc/faq.mdx

@@ -119,4 +119,6 @@ Nonetheless, you can also reserve specific IPs from a Private Network's CIDR blo
 
 ### How can I attach my VMs on a Proxmox cluster on Elastic Metal to a Private Network?
 
-We recommend that you use our IPAM product for this purpose. See [how to reserve a private IP address with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address).
+For this purpose use the option of attaching a **custom resource** to a Private Network, specifying its MAC address. Full instructions for attaching custom resources are in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn#how-can-i-manage-ip-addresses-for-my-proxmox-virtual-machines-vms-on-elastic-metal-servers).
+
+You can also [reserve a private IP address](/ipam/how-to/reserve-ip/) with IPAM, and use this reserved address to attach a custom resource.

pages/vpc/how-to/attach-resources-to-pn.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to attach resources to a Private Network in a Scaleway VPC
 tags: regional-private-network private-network vpc virtual-private-cloud attach detach resources regional
 dates:
-  validation: 2024-10-21
+  validation: 2025-02-20
   posted: 2023-03-21
 categories:
   - network
@@ -20,16 +20,21 @@ Private Networks also have built-in **D**ynamic **H**ost **C**onfiguration **P**
 Up to 512 resources can be attached to each Private Network, and each resource can be attached to up to eight Private Networks.
 
 The following resource types can be attached to a Private Network:
-- Instances
-- Elastic Metal servers
-- Apple silicon (Mac mini)
-- Load Balancers
-- Public Gateways
-- Managed Databases for PostgreSQL and MySQL
-
-<Message type="note">
- Kubernetes Kapsules and Managed Databases for Redis™ are also compatible with Private Networks, but they can only be attached to a Private Network at the time of creating the resource. It is not possible to attach a cluster or Redis™ database to a Private Network after its creation, or change the attached Private Network.
-</Message>
+
+**Scaleway-managed resources**:
+    - Instances
+    - Elastic Metal servers
+    - Apple silicon (Mac mini)
+    - Load Balancers
+    - Public Gateways
+    - Managed Databases for PostgreSQL and MySQL
+
+    <Message type="note">
+    Kubernetes Kapsule clusters and Managed Databases for Redis™ are also compatible with Private Networks, but they can only be attached to a Private Network at the time of creating the resource. It is not possible to attach a cluster or Redis™ database to a Private Network after its creation, or change the attached Private Network.
+    </Message>
+
+**Custom resources**
+    - Custom resources with a MAC address, e.g. a VM hosted on an Elastic Metal server
 
 <Macro id="requirements" />
 
@@ -54,27 +59,53 @@ The following resource types can be attached to a Private Network:
 
 4. Click the **Attached resources** tab.
 
-    If you already have resources attached to the Private Network, a list of these displays. Otherwise, you see a welcome screen.
+    <Lightbox src="scaleway-pn-attached-resources.webp" alt="" />
 
-5. Click **+ Attach resource**. The following screen displays.
+5. Use the toggle to select the type of resource you want to attach:
 
-    <Lightbox src="scaleway-attach-resource.webp" alt="" />
+    - **Managed** resources are created and managed via Scaleway, e.g. Instances, Elastic Metal servers, Load Balancers, Managed Databases, Kubernetes Kapsules, Public Gateways, Apple silicon etc.
+    - **Custom** resources are created and managed by yourself, e.g. virtual machines you are hosting on a Proxmox cluster on an Elastic Metal server. 
 
-6. Select the type of resource (Instance, Elastic Metal server etc.) that you want to attach. Then select the specific resource to attach. Only resources within the same region (or one of its Availability Zones) as the Private Network will be displayed.
+6. Click **+ Attach resource**. A pop-up displays.
 
-    <Message type="tip">
-    When attaching Instances, Load Balancers, Public Gateways, and Elastic Metal servers, you have the option to either auto-allocate an available IP from the pool of addresses for the Private Network or specify an IP that you have already [reserved via IPAM](/ipam/how-to/reserve-ip/). For Instances, which support both IPv4 and IPv6 for private IP addresses, you can also choose to auto-allocate or specify a reserved IP for each address type.
+7. Complete the required information about the resource to attach. This depends on whether you are attaching a managed or custom resource.
+
+    <Tabs id="attach-resource">
+
+        <TabsTab label="Managed resource">
 
-    Support for using reserved IPs to attach Managed Databases to Private Networks will be coming soon.
-    </Message>
+        <Lightbox src="scaleway-attach-resource.webp" alt="" />
+
+        - From the first drop-down, select the **type** of managed resource (Instance, Elastic Metal server etc.) to attach.
+        - From the second drop-down, select the **specific resource** of this type to attach. Only resources within the same region as the Private Network will be displayed.
+        - Select whether to **auto-allocate an available IP** from the pool of addresses for the Private Network or **specify an IP** that you have already [reserved via IPAM](/ipam/how-to/reserve-ip/). 
+
+        <Message type="note">
+        Only Instances, Load Balancers, Public Gateways, and Elastic Metal servers are compatible with reserved IPs. Support for Managed Databases and Apple silicon will be coming soon. In the meantime, you must auto-allocate IPs for these products.
+        </Message>
+        </TabsTab>
 
-7. Click **Attach resource** to finish.
+        <TabsTab label="Custom resource">
+
+        <Lightbox src="scaleway-attach-custom.webp" alt="" />
+
+        <Message type="important">
+        This method is intended for custom resources such as VMs hosted on Elastic Metal. Do **not** attempt to attach a managed resource, such as an Instance, via this method - use the **Managed resource** attachment instead.
+        </Message>
+
+        - Select **Custom resource** from the **Type of resource** dropdown.
+        - Enter the MAC address of the custom resource you want to attach, e.g. `00:1B:44:11:3A:B7`.
+        - Enter the name of the resource. This will be used for DNS resolution on the Private Network.
+        </TabsTab>
+    </Tabs>
+
+8. Click **Attach to Private Network** to finish.
 
     You are returned to the list of attached resources, where the newly-attached resource now displays.
 
 <Message type="tip">
 
-You can also attach a resource to a Private Network from the resource's own section of the console. Follow the relevant steps below:
+You can also attach a managed resource to a Private Network from the resource's own section of the console. Follow the relevant steps below:
 - [Instance](/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network)
 - [Elastic Metal server](/elastic-metal/how-to/use-private-networks/#from-the-elastic-metal-section-of-the-console)
 - [Apple silicon](/apple-silicon/how-to/use-private-networks/)
@@ -85,7 +116,7 @@ You can also attach a resource to a Private Network from the resource's own sect
 Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself.
 </Message>
 
-For Elastic Metal servers and Apple silicon Mac minis, manual configuration of the network interface is required. This is not required for Instances or other types of resources. See the relevant documentation for [Elastic Metal](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) or [Apple silicon](/apple-silicon/how-to/use-private-networks/) for full instructions.
+For Elastic Metal servers and Apple silicon Mac minis, manual configuration of the network interface is required. This is not required for Instances or other types of managed resource. See the relevant documentation for [Elastic Metal](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) or [Apple silicon](/apple-silicon/how-to/use-private-networks/) for full instructions.
 
 ## How to view the resource's IP address
 
@@ -135,14 +166,19 @@ For full information on Scaleway internal DNS and hostname formats, including tr
 
 4. Click the **Attached resources** tab.
 
-    A list of resources attached to the Private Network displays.
+    The Private Network's dashboard displays.
 
-    <Lightbox src="scaleway-attached-resources.webp" alt="" />
+5. Click the **Attached resources** tab.
+
+6. Use the toggle to select the type of resource you want to detach:
+
+    - **Managed** resources are created and managed via Scaleway, e.g. Instances, Elastic Metal servers, Load Balancers, Managed Databases, Kubernetes Kapsules, Public Gateways, Apple silicon etc.
+    - **Custom** resources are created and managed by yourself, e.g. virtual machines you are hosting on a Proxmox cluster on an Elastic Metal server. 
 
-5. Click the <Icon name="unlink" /> icon next to the resource you want to detach.
+7. Click the <Icon name="unlink" /> icon next to the resource you want to detach.
 
-6. Click **Detach resource** when prompted to confirm.
+8. Click **Detach resource** when prompted to confirm.
 
 <Message type="tip">
-You can also detach a resource to a Private Network from the resource's own section of the console.
+You can also detach a managed resource to a Private Network from the resource's own section of the console.
 </Message>