F OpenNebula/one#7563: Second update to Installation documentation (#631)

This PR includes updates to the Installation documentation including the direction of the OneDeploy docs to the OneDeploy repository wiki, refinement of the overviews and installation documentation flow.

Author: mattrowe-opennebula

content/getting_started/understand_opennebula/opennebula_concepts/comparison.md

@@ -54,7 +54,7 @@ Thousands of organizations worldwide already rely on OpenNebula as an open alter
 | **Cluster and Federation Support** | Multi-cluster and multi-zone federation with centralized governance and distributed scheduling. |
 | **Scalability** | Proven scalability in production environments with over 2,500 hypervisor nodes managed within a single OpenNebula instance. |
 | **HA and Disaster Recovery** | HA for front-end and host nodes; redundant database and failover mechanisms for service continuity across data centers. |
-| **Hybrid & Edge Cloud** | Automatic provisioning on AWS, Equinix Metal, Scaleway and remote OpenNebula zones; optimized for edge deployments. |
+| **Hybrid & Edge Cloud** | Automatic provisioning on AWS, Scaleway and remote OpenNebula zones; optimized for edge deployments. |
 | **Enhanced Platform Awareness (EPA) Integration** | Support for NUMA\-aware CPU pinning, SR-IOV, and HugePages to provide precise hardware-level optimization and secure, performance-aware orchestration of virtualized workloads.  |
 | **AI and Accelerated Computing** | Support for NVIDIA GPUs, MIG scheduling, NVLink, Infiniband, Spectrum-X, and DPU offloading for accelerated networking, storage, and AI workloads. |
 | **Networking Models** | Comprehensive networking support, including software-defined networking (SDN), virtual, and physical appliances, including Linux Bridge, 802.1Q VLAN, VXLAN, Open vSwitch; SDN integration with BlueField DPUs and Spectrum-X fabrics. |

content/product/cluster_provisioning/cluster_operations/provider_operations.md

@@ -12,7 +12,7 @@ weight: "2"
 
 <!--# Managing Providers -->
 
-In OneForm, Providers are created using Provider drivers for on-premise hardware or 3rd-party cloud/bare-metal services such as AWS, Scaleway and Equinix. Use the `oneform` CLI tool to manage your cloud infrastructure instance and configuration.
+In OneForm, Providers are created using Provider drivers for on-premise hardware or 3rd-party cloud/bare-metal services such as AWS, Scaleway and i3Dnet. Use the `oneform` CLI tool to manage your cloud infrastructure instance and configuration.
 
 With this guide, you will understand how the drivers and Providers and Provisions relate by: 
 
@@ -35,7 +35,7 @@ After running the command, you will see that all the driver templates are create
 
 ## Additional Drivers
 
-Only the **onprem** driver is included by default in a fresh OpenNebula installation with OneForm. To install and enable other drivers, such as **aws**, **equinix** and **scaleway**, you need to clone the [OneForm Registry repository](https://github.com/OpenNebula/oneform-registry) onto the OpenNebula Front-end with the following commands as the `oneadmin` user:
+Only the **onprem** driver is included by default in a fresh OpenNebula installation with OneForm. To install and enable other drivers, such as **aws**, **i3dnet** and **scaleway**, you need to clone the [OneForm Registry repository](https://github.com/OpenNebula/oneform-registry) onto the OpenNebula Front-end with the following commands as the `oneadmin` user:
 
 ```bash
 git -C /var/lib/one/oneform/drivers clone https://github.com/OpenNebula/oneform-registry.git

content/product/cluster_provisioning/cluster_operations/provision_operations.md

@@ -123,7 +123,7 @@ In the Sunstone interface, go to **Infrastructure -> Clusters** and select the C
 {{% /tab %}}
 
 {{% tab header="CLI"%}}
-For Provisions that support public networking like AWS and Equinix, dynamically manage Elastic IPs through the following commands:
+For Provisions that support public networking like AWS and i3Dnet, dynamically manage Elastic IPs through the following commands:
 
 * Add Public IPs
 

content/product/cluster_provisioning/cluster_providers/cloud_providers.md

@@ -11,7 +11,7 @@ weight: "3"
 
 <a id="cloud-providers"></a>
 
-Cloud Providers define how OneForm interacts with 3rd-party IaaS cloud or bare-metal infrastructure providers such as AWS, Scaleway or Equinix. Providers for cloud-based service providers handle the credentials and API keys needed to connect with the service and automatically manage physical or virtual computing resources through OneForm. You only need to set up a Provider once for a cloud-based service, then it can be used repeatedly to provision Clusters without the need to recall credentials or configuration.  
+Cloud Providers define how OneForm interacts with 3rd-party IaaS cloud or bare-metal infrastructure providers such as AWS, Scaleway or i3Dnet. Providers for cloud-based service providers handle the credentials and API keys needed to connect with the service and automatically manage physical or virtual computing resources through OneForm. You only need to set up a Provider once for a cloud-based service, then it can be used repeatedly to provision Clusters without the need to recall credentials or configuration.  
 
 ## Creating Providers for 3rd-party Cloud or Bare-metal Services
 
@@ -21,7 +21,7 @@ To create Providers for 3rd-party services, you need to install a Provider drive
 
 * After installing the drivers follow the instructions for creating Providers for the following services:
     * [Amazon AWS Provider](https://github.com/OpenNebula/oneform-registry/wiki/Amazon-Web-Services-Provider)
-    * [Equinix Provider](https://github.com/OpenNebula/oneform-registry/wiki/Equinix-Provider)
+    * [i3Dnet Provider](https://github.com/OpenNebula/oneform-registry/wiki/i3Dnet-Provider)
     * [Scaleway Provider](https://github.com/OpenNebula/oneform-registry/wiki/Scaleway-Provider)
 
 ## Developing Provider Drivers
@@ -33,5 +33,5 @@ If a driver does not currently exist for your preferred cloud service, you can d
 Once you have created Providers for your preferred cloud or bare-metal service, you can provision Clusters using those services through OneForm. Please refer to the relevant Provisioning guide in the OneForm Registry Wiki for your preferred service provider:
 
 * [AWS](https://github.com/OpenNebula/oneform-registry/wiki/Amazon-Web-Services-Cluster)
-* [Equinix](https://github.com/OpenNebula/oneform-registry/wiki/Equinix-Cluster)
+* [i3Dnet](https://github.com/OpenNebula/oneform-registry/wiki/i3Dnet-Cluster)
 * [Scaleway](https://github.com/OpenNebula/oneform-registry/wiki/Scaleway-Cluster)

content/product/cluster_provisioning/cluster_providers/overview.md

@@ -10,7 +10,7 @@ weight: "1"
 ---
 
 <!--# Overview -->
-A **Provider** is an abstraction layer that defines the credentials, endpoints, and specific locations (such as a region or zone) within a target infrastructure. It acts as the "source of authority" that OneForm uses to authenticate and communicate with external resources — whether they are public cloud APIs (like AWS), bare-metal edge locations (like Equinix), or on-premises resources — to prepare the ground for a Cluster deployment.
+A **Provider** is an abstraction layer that defines the credentials, endpoints, and specific locations (such as a region or zone) within a target infrastructure. It acts as the "source of authority" that OneForm uses to authenticate and communicate with external resources — whether they are public cloud APIs (like AWS), bare-metal edge locations (like i3Dnet), or on-premises resources — to prepare the ground for a Cluster deployment.
 
 ## Basic Outline
 
@@ -24,7 +24,7 @@ An on-premises Provider is installed by default with OpenNebula, refer to the [O
 Provider drivers for 3rd-party IaaS cloud providers can be installed in your OpenNebula deployment. The Provider drivers are available in the [OneForm Registry Repository](https://github.com/OpenNebula/oneform-registry) in the [OpenNebula GitHub Project](https://github.com/OpenNebula). Instructions for installing and synchronizing the 3rd-party Provider drivers can be found in the [OneForm Registry Wiki](https://github.com/OpenNebula/oneform-registry/wiki). After installing the drivers, you can find additional guides in the Wiki to create Providers for the following cloud/bare-metal services:
 
 - [Amazon AWS Provider](https://github.com/OpenNebula/oneform-registry/wiki/Amazon-Web-Services-Provider)
-- [Equinix Provider](https://github.com/OpenNebula/oneform-registry/wiki/Equinix-Provider)
+- [i3Dnet Provider](https://github.com/OpenNebula/oneform-registry/wiki/i3Dnet-Provider)
 - [Scaleway Provider](https://github.com/OpenNebula/oneform-registry/wiki/Scaleway-Provider)
 
 ## Logical Model of a Provider
@@ -84,7 +84,7 @@ For more detailed information about Provider datamodels and configuration, refer
 
 ## Provider Drivers
 
-Each Provider in OpenNebula is associated with a **Provider driver** that defines the underlying automation logic for infrastructure provisioning and configuration. A driver defines the logic for communicating with a specific cloud IaaS API or bare-metal hardware resource while the Provider defines the credentials, location and metadata. Therefore, a single driver is associated with a specific IaaS service (e.g. AWS, Equinix, Scaleway) while multiple Providers may use the same driver. For example, if you wish to use resources in multiple AWS regions, you must create a separate Provider for each AWS region, using the same AWS driver.  
+Each Provider in OpenNebula is associated with a **Provider driver** that defines the underlying automation logic for infrastructure provisioning and configuration. A driver defines the logic for communicating with a specific cloud IaaS API or bare-metal hardware resource while the Provider defines the credentials, location and metadata. Therefore, a single driver is associated with a specific IaaS service (e.g. AWS, i3Dnet, Scaleway) while multiple Providers may use the same driver. For example, if you wish to use resources in multiple AWS regions, you must create a separate Provider for each AWS region, using the same AWS driver.  
 
 ### Driver Structure
 

content/product/cluster_provisioning/cluster_providers/scaleway_provider.md

@@ -164,7 +164,7 @@ curl -X POST "https://oneform.example.server/api/v1/providers" \
   -u "username:password" \
   -H "Content-Type: application/json" \
   -d '{
-    "driver": "equinix",
+    "driver": "scaleway",
     "connection_values": {
       "region": "fr-par",
       "zone": "fr-par-2",

content/product/cluster_provisioning/cluster_provisions/_index.md

@@ -1,7 +1,7 @@
 ---
 title: "Provisions"
 date: "2025-02-17"
-description: "Automatically provision Edge Clusters on-premises or on AWS, Equinix and Scaleway."
+description: "Automatically provision Edge Clusters on-premises or on AWS, i3Dnet and Scaleway."
 categories:
 pageintoc: "209"
 tags:

content/product/cluster_provisioning/overview.md

@@ -32,7 +32,7 @@ Each of the guides in this Cluster provisioning documentation demonstrates how t
 
 ## [Cluster Providers]({{% relref "product/cluster_provisioning/cluster_providers/" %}})
 
-* **Definition**: Providers represent your credentials and endpoints for third-party cloud services (e.g., AWS, Equinix, Scaleway) or on-premises environments.
+* **Definition**: Providers represent your credentials and endpoints for third-party cloud services (e.g., AWS, i3Dnet, Scaleway) or on-premises environments.
 
 * **Key Function**: Acts as an abstraction layer. Instead of managing complex API keys and connection strings every time you need a new Host, you define a Provider only once.
 

content/product/virtual_machines_operation/virtual_machines/vm_templates.md

@@ -375,7 +375,7 @@ Also, there will be a tab called MYSQL with two groups, CONFIG and ADDITIONAL:
 
 ![sunstone_user_inputs_convention_mysql_1](/images/sunstone_user_inputs_convention_mysql_1.png)
 
-To see the user inputs in the ADDITONAL group, the user must turn on the Define additional parameters user input:
+To set the user inputs in the ADDITIONAL group, activate the **Define additional parameters** option:
 
 ![sunstone_user_inputs_convention_mysql_2](/images/sunstone_user_inputs_convention_mysql_2.png)
 

content/software/installation_process/_index.md

@@ -11,4 +11,4 @@ weight: "3"
 
 <a id="package-installation-references"></a>
 
-This section contains details for deploying an OpenNebula-managed cloud. Installation starts with the deployment of an OpenNebula **Front-end**. Once the OpenNebula Front-end is deployed, **Clusters** can be installed manually or deployed automatically with OneForm to handle cloud workloads. OneDeploy can be used for advanced installation requirements.
+This section contains details for deploying an OpenNebula-managed cloud. Installation starts with the deployment of an OpenNebula **Front-end**. Once the OpenNebula Front-end is deployed, **Clusters** can be installed manually or deployed automatically with OneForm to handle cloud workloads. **OneDeploy** can be used for advanced, automated installation of both the Front-end and Clusters. Please read the [Installation Overview]({{% relref "software/installation_process/overview/" %}}) for details on each of the installation options prior to starting.