proofreading - index & yaml update

Author: benchbzh

pages/index.md

@@ -729,6 +729,7 @@
             + [Forensics: How to deal with Public Cloud instances](public_cloud/compute/forensics)
             + [Local Zone VPN-as-a-Service (VPNaaS) with Tailscale Integration](public_cloud/compute/local-zones-vpn-tailscale-integration)
             + [Migration of instances between different regions](public_cloud/compute/migration_between_regions)
+            + [How to connect a Public Cloud instance to an EFS volume via vRack](storage_and_backup/file_storage/enterprise_file_storage/netapp_pci_connection_via_vrack)
     + [Storage and Backup](products/public-cloud-storage)
         + [Object Storage](products/public-cloud-storage-object-storage)
             + [General information](public-cloud-storage-object-storage-general-information)
@@ -1965,6 +1966,7 @@
             + [Enterprise File Storage - NFS Client considerations](storage_and_backup/file_storage/enterprise_file_storage/netapp_nfs_client_considerations)
             + [Enterprise File Storage - FAQ](storage_and_backup/file_storage/enterprise_file_storage/netapp_faq)
             + [Enterprise File Storage - Private network configuration](storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config)
+            + [Enterprise File Storage - Connect a Public Cloud instance to an EFS volume via vRack](storage_and_backup/file_storage/enterprise_file_storage/netapp_pci_connection_via_vrack)
             + [File Storage services - Responsibility model](account_and_service_management/responsibility_sharing/file-storage)
             + [File Storage reversibility policy](account_and_service_management/reversibility/08-file-storage-reversibility-policy)
         + [HA-NAS](storage-file-storage-ha-nas)

pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_pci_connection_via_vrack/guide.en-gb.md

@@ -1,5 +1,5 @@
 ---
-title: "Enterprise File Storage - Connect a Public Cloud Instance to an EFS Volume via vRack Private Network"
+title: "Enterprise File Storage - Connect a Public Cloud instance to an EFS Volume via vRack Private Network"
 excerpt: "Find out how to connect a Public Cloud instance to an Enterprise File Storage (EFS) volume using a vRack private network."
 updated: 2025-10-23
 ---
@@ -31,10 +31,10 @@ This ensures that all data traffic remains on the private network, with no Inter
 
 ## Requirements
 
-- An [Enterprise File Storage](/links/storage/enterprise-file-storage) service in your OVHcloud account
-- An [OVHcloud Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) in the same region
-- An active [vRack Private Network](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack) in the same region
-- Access to the [OVHcloud Control Panel](/links/manager) or the [Openstack CLI](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables)
+- An [Enterprise File Storage](/links/storage/enterprise-file-storage) service in your OVHcloud account.
+- An [OVHcloud Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) in the same region.
+- An active [vRack Private Network](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack) in the same region.
+- Access to the [OVHcloud Control Panel](/links/manager) or the [Openstack CLI](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables).
 
 ## Overview
 
@@ -44,23 +44,23 @@ The diagram below illustrates how an Enterprise File Storage (EFS) volume connec
 
 1. Critical Match — VLAN ID
 
-The VLAN ID (e.g., `1900`) must be identical in both the Public Cloud Private Network and the vRack Services configuration.
+    The VLAN ID (e.g. `1900`) must be identical in both the Public Cloud private network and the vRack services configuration.
 
 2. Critical Match — Subnet CIDR
 
-The Subnet CIDR (e.g., `10.235.0.0/24`) must also match across both services to ensure they operate within the same logical network in the vRack.
+    The subnet CIDR (e.g. `10.235.0.0/24`) must also match across both services to ensure they operate within the same logical network in the vRack.
 
-3. Info — Service Address Range
+3. Info — Service address range
 
-The Service Address Range (e.g., `10.235.0.240/28`) is a reserved subset of the main subnet. These IPs are exclusively used by EFS service endpoints (e.g., `10.235.0.241`) and must not be assigned to instances.
+    The service address range (e.g. `10.235.0.240/28`) is a reserved subset of the main subnet. These IPs are exclusively used by EFS service endpoints (e.g. `10.235.0.241`) and must not be assigned to instances.
 
 4. Security — ACL Rule
 
-The EFS volume’s Access Control List (ACL) must explicitly authorize the private IP of any instance requiring access (e.g., `10.235.0.15`).
+    The EFS volume’s Access Control List (ACL) must explicitly authorize the private IP of any instance requiring access (e.g. `10.235.0.15`).
 
 5. Concept — vRack Services
 
-vRack Services acts as a secure network bridge, allowing managed services such as EFS outside your Public Cloud project to connect seamlessly to your private vRack network.
+    vRack Services acts as a secure network bridge, allowing managed services such as EFS outside your Public Cloud project to connect seamlessly to your private vRack network.
 
 ## Instructions
 
@@ -70,109 +70,109 @@ Before deploying your Enterprise File Storage (EFS) volume through a private vRa
 
 This association enables private networking between your Public Cloud instances and OVHcloud managed services such as EFS.
 
-Follow the procedure described in [Step 1: Activating and managing a vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
+Follow the procedure described in the **step 1: activating and managing a vRack** in our guide "[Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)".
 
 ### Step 2 - Create a Private Network in Your Public Cloud Project <a name="step2"></a>
 
 To connect your Public Cloud instance to an EFS volume via vRack, first provision a dedicated private network within your project. 
 
 This isolated network enables secure communication between your instances and OVHcloud storage resources through the vRack architecture. 
 
-Follow the procedure described in [Step 2: Creating a private network in the vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
+Follow the procedure described in the **step 2: creating a private network in the vRack** in our guide "[Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)".
 
 ### Step 3 — Launch the Instance on the Private Network
 
 Deploy your Public Cloud instance within the private network you created. Ensure it is connected to the correct subnet to enable secure communication over the vRack. 
 
-Follow the procedure described in [Step 3: Integrating an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
+Follow the procedure described in the **step 3: integrating an instance into vRack** in our guide "[Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)".
 
 ![instance creation on the Private Network](images/instance-in-private-net.png){.thumbnail}
 
-Ensure the instance is assigned an IP address within the selected subnet (e.g., `10.235.0.15`).
-
-Both methods achieve the same goal: securely connecting your EFS service to your vRack and Public Cloud instances.
+Ensure that an IP address is assigned to the instance in the selected subnet (e.g. `10.235.0.15`).
 
 ### Step 4 - Create a vRack Service resource for EFS
 
 There are two ways to create a vRack Service resource for your EFS volume.
 
-/// details | a. Create via vRack Services
+Both methods achieve the same goal: securely connecting your EFS service to your vRack and Public Cloud instances.
+
+/// details | First method: creating via vRack Services
 
 A vRack Service resource acts as a network adapter, connecting managed services like EFS to your vRack and its private subnet.
 
-For detailed guidance, see OVHcloud’s official documentation: [vRack Services - Exposing a Managed Service on your vRack](/pages/network/vrack_services/global)
+For detailed guidance, see OVHcloud’s official documentation: [vRack Services - Exposing a Managed Service on your vRack](/pages/network/vrack_services/global).
 
-1. In the [OVHcloud Control Panel](/links/manager), navigate to `Network`{.action} section, go to `vRack Services`{.action}. 
+1. In the [OVHcloud Control Panel](/links/manager), navigate to `Network`{.action} section, then click on `vRack Services`{.action}. 
 
 2. Then click `Activate vRack Services`{.action}.
 
-3. Select the same region as your vRack, Public Cloud instance, and EFS service. <span id="step4-a-region-selection"></span>
-
-![vrack activation popup](images/vrack_activation.png){.thumbnail}
+3. Select the same region as your vRack, Public Cloud instance and EFS service. Then click `Activate vRack Services`{.action}. <span id="step4-a-region-selection"></span>
 
 4. Select `No thanks, i already have a vRack`{.action} and accept the terms and conditions to confirm. 
 
-5. Then, locate your newly created vRack Service in the list and click it.
+    ![vrack activation popup](images/vrack_activation.png){.thumbnail}
+
+5. Then, locate your newly created vRack Service in the list and click its name.
 
-![vrack list](images/vrack_list.png){.thumbnail}
+    ![vrack list](images/vrack_list.png){.thumbnail}
 
 6. Edit the vRack Service with the following configuration:
 
-- Private Network: Select the same vRack used for your Public Cloud project.
+    - Private Network: Select the same vRack used for your Public Cloud project.
 
-![vrack - selection of the private network](images/vrack_selection_private_net.png){.thumbnail}
+    ![vrack - selection of the private network](images/vrack_selection_private_net.png){.thumbnail}
 
-- Create a subnet:
+    - Create a subnet:
 
-![vrack - creation of the subnet](images/vrack_selection_subnet.png){.thumbnail}
+        ![vrack - creation of the subnet](images/vrack_selection_subnet.png){.thumbnail}
 
-> [!primary] 
-> 
-> Ensure the CIDR matches your Public Cloud private network.
->
+        > [!primary] 
+        > 
+        > Ensure the CIDR matches your Public Cloud private network.
+        >
 
-1. Subnet CIDR: e.g., `10.235.0.0/24`
-2. Service Address Range: e.g., `10.235.0.240/28`
-    - Reserved subset of the private subnet for assigning IPs to managed EFS services within the vRack.
-3. VLAN: Use the same VLAN number as your Public Cloud private network (see [Step 2](#step2)).
-4. Create
+        - Subnet address Range: e.g. `10.235.0.0/24`.
+        - Service address Range: e.g. `10.235.0.240/28`.
+            - Reserved subset of the private subnet for assigning IPs to managed EFS services within the vRack.
+        - VLAN: Use the same VLAN number as your Public Cloud private network (see [Step 2](#step2)).
+        - Click `Create subnet`{.action}.
 
-- Create a Service endpoint:
+    - Create a Service Endpoint:
 
-![vrack - creation of the endpoint service](images/vrack_selection_endpoint.png){.thumbnail}
+    ![vrack - creation of the endpoint service](images/vrack_selection_endpoint.png){.thumbnail}
 
 ///
 
-/// details | b. Create via Enterprise File Storage section
+/// details | Second method: creating via Enterprise File Storage section
 
-1. In the [OVHcloud Control Panel](/links/manager), navigate to the `Bare Metal Cloud`{.action} section. Go to `Strorage and backups`{.action}, `Enterprise File Storage`{.action}, then select your EFS service.
+1. In the [OVHcloud Control Panel](/links/manager), navigate to the `Bare Metal Cloud`{.action} section. Click `Enterprise File Storage`{.action} under the heading **Storage and backups**, then select your EFS service.
 
-2. Under Network Configuration, click `Configure Network Settings`{.action}.
+2. In the `Network Configuration` box, click `Configure Network Settings`{.action}.
 
-![efs - configure network settings](images/efs_configure_network.png){.thumbnail}
+    ![efs - configure network settings](images/efs_configure_network.png){.thumbnail}
 
-3. Select your vRack 
+3. Select your vRack.
 
-4. If no vRack Service has been created yet, activate the vRack services and follow the [step 4a-3. Create via vRack Services](step4-a-region-selection)
+4. If no vRack Services have been created yet, activate the vRack Services and follow the [first method: creation via vRack services](step4-a-region-selection) from the third point.
 
-5. If you already created a vRack services, Select your dedicated service.
+5. If you have already created a vRack service, select your dedicated service.
 
 ///
 
 ### Step 5 — Connect the EFS Volume to the vRack
 
 Once the previous steps are completed successfully, all volumes created in your EFS service will automatically reside within your vRack and its dedicated subnet, making them immediately accessible to your Public Cloud instances.
 
-### Step 6 — Configure Access Control (ACLs)
+### Step 6 — Configure access control (ACLs)
 
-In the Access Control tab of your EFS volume:
+In the `Access Control List (ACL)`{.action} tab of your EFS volume:
 
 - Add the IPs or CIDR ranges authorized to mount the volume:
 
-  - To allow a single instance: `10.235.0.15`
-  - To allow all instances within the subnet: `10.235.0.0/24`
+    - To allow a single instance, enter the instance's IP address, for example: `10.235.0.15`.
+    - To allow all instances within the subnet, enter the subnet address, for example: `10.235.0.0/24`.
 
-- Set the desired Access Level: Read/Write or Read-only.
+- Set the desired Access Level: **Read and write** or **Read-only**.
 
 > [!primary]
 >
@@ -189,21 +189,21 @@ ping <YOUR-EFS-SERVICE-IP>
 
 1. Install the NFS client on your Public Cloud instance:
 
-```bash
-sudo apt install -y nfs-common
-```
+    ```bash
+    sudo apt install -y nfs-common
+    ```
 
 2. Mount the EFS volume:
 
-```bash
-sudo mkdir -p /mnt/efs
-sudo mount -t nfs -o vers=3,timeo=600,retrans=2 <YOUR-EFS-SERVICE-IP>:/share_<ID> /mnt/efs
-df -h /mnt/efs
-```
+    ```bash
+    sudo mkdir -p /mnt/efs
+    sudo mount -t nfs -o vers=3,timeo=600,retrans=2 <YOUR-EFS-SERVICE-IP>:/share_<ID> /mnt/efs
+    df -h /mnt/efs
+    ```
 
-### Step 8 — (Optional) Enable Automatic Mount on Boot
+### Step 8 — Enable Automatic Mount on Boot (optional)
 
-To ensure your EFS volume mounts automatically at startup, add the following entry to your `/etc/fstab` file:
+To ensure your EFS volume mounts automatically at startup, add the following entry to the `/etc/fstab` file:
 
 ```bash
 <YOUR-EFS-SERVICE-IP>:/share_<ID> /mnt/efs nfs vers=3,timeo=600,retrans=2 0 0
@@ -228,12 +228,12 @@ If no errors occur, the EFS volume will now automatically mount on boot.
 
 | Symptom                            | Likely Cause                                              | Resolution                                                                                                                                     |
 | ---------------------------------- | --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| mount.nfs: No route to host        | Instance and EFS not in the same region, or wrong VLAN ID | Ensure the instance, EFS, and vRack Services are in the same region. Recreate the vRack Service using the same VLAN ID as the private network. |
-| mount.nfs: access denied by server | EFS ACL missing or incorrect                              | Add the instance IP (e.g., `10.235.0.x`) or subnet (e.g., `10.235.0.0/24`) with protocol NFSv3 and Read/Write access.                          |
-| mount command hangs indefinitely   | Wrong NFS version or unresponsive endpoint                | Use: `-o vers=3,timeo=600,retrans=2` to force NFSv3 and define timeouts.                                                                       |
-| mount succeeds but no read/write   | ACLs or POSIX permissions too strict                      | Adjust ACLs or update volume-level permissions.                                                                                               |
-| mount works, but not after reboot  | Missing `/etc/fstab` entry                                  | Add: `<YOUR-EFS-SERVICE-IP>:/share_<ID> /mnt/efs nfs vers=3,timeo=600,retrans=2 0 0`                                                           | 
-| vRack Services shows “Inactive”    | Service not yet provisioned                               | Wait for provisioning to complete, or reattach the service from the EFS Private Network tab.                                                   |
+| mount.nfs: No route to host        | Instance and EFS not in the same region, or wrong VLAN ID. | Ensure the instance, EFS, and vRack Services are in the same region. Recreate the vRack Service using the same VLAN ID as the private network. |
+| mount.nfs: access denied by server | EFS ACL missing or incorrect.                              | Add the instance IP (e.g. `10.235.0.x`) or subnet (e.g. `10.235.0.0/24`) with protocol NFSv3 and Read/Write access.                          |
+| mount command hangs indefinitely   | Wrong NFS version or unresponsive endpoint.                | Use: `-o vers=3,timeo=600,retrans=2` to force NFSv3 and define timeouts.                                                                       |
+| mount succeeds but no read/write   | ACLs or POSIX permissions too strict.                      | Adjust ACLs or update volume-level permissions.                                                                                               |
+| mount works, but not after reboot  | Missing `/etc/fstab` entry.                                  | Add: `<YOUR-EFS-SERVICE-IP>:/share_<ID> /mnt/efs nfs vers=3,timeo=600,retrans=2 0 0`.                                                           | 
+| vRack Services shows “Inactive”    | Service not yet provisioned.                               | Wait for provisioning to complete, or reattach the service from the EFS Private Network tab.                                                   |
 
 ## Go further
 
@@ -249,4 +249,4 @@ If no errors occur, the EFS volume will now automatically mount on boot.
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).