OpenNebula · mattrowe-opennebula · Apr 17, 2026
diff --git a/...tarted/try_opennebula/try_kubernetes_on_opennebula/managing_k8s_with_rancher.md b/...tarted/try_opennebula/try_kubernetes_on_opennebula/managing_k8s_with_rancher.md
@@ -519,7 +519,7 @@ Congratulations! You have successfully deployed a K3s Cluster with the Rancher m
 
 To learn about OpenNebula in depth, the next sections of the documentation include all of the information necessary for [configuration and administration]({{% relref "product/index" %}}), as well as software [life cycle, releases and installation details]({{% relref "software/index" %}}).
 
-If you are interested in installing OpenNebula by following further tutorials, you can head over to [Automatic Installation with OneDeploy]({{% relref "software/installation_process/automatic_installation_with_onedeploy/one_deploy_overview" %}}) to automatically install a production-ready OpenNebula cloud.
+If you are interested in installing OpenNebula by following further tutorials, you can head over to [Automatic Installation with OneDeploy]({{% relref "software/installation_process/advanced_installation_with_onedeploy/one_deploy_overview" %}}) to automatically install a production-ready OpenNebula cloud.
 
 ## Using SSH on Remote Hardware
 

diff --git a/...nderstand_opennebula/cloud_architecture_and_design/cloud_architecture_design.md b/...nderstand_opennebula/cloud_architecture_and_design/cloud_architecture_design.md
@@ -23,21 +23,21 @@ To familiarize yourself with deployment and daily operations, or if you want to
 
 As you follow the tutorials you will learn the basic usage and operation of your cloud. This trial of a real cloud deployment can help you to plan for the most suitable features for performance and scalability, to get the most out of your OpenNebula cloud.
 
-To install a production-ready OpenNebula cloud, we highly recommend using [OneDeploy]({{% relref "automatic_installation_with_onedeploy" %}}), a tool for automated installation. With OneDeploy you can install a complete cloud by defining your desired configuration and running a few simple commands. The tutorials provide step-by-step instructions with complete commands for sample deployment scenarios.
+To install a production-ready OpenNebula cloud, we highly recommend using [OneDeploy]({{% relref "advanced_installation_with_onedeploy" %}}), a tool for automated installation. With OneDeploy you can install a complete cloud by defining your desired configuration and running a few simple commands. The tutorials provide step-by-step instructions with complete commands for sample deployment scenarios.
 
 For a sequential outline of the tasks involved in designing an OpenNebula cloud, read on.
 
 ## Step 1. Install the Front-end
 
-The first step is the installation of the OpenNebula Front-end. The [installation process]({{% relref "front_end_installation" %}}) is based on operating system packages for the most widely-used Linux distributions and is the same for any underlying hypervisor or deployment model.
+The first step is the installation of the OpenNebula Front-end. The [installation process]({{% relref "software/installation_process/frontend_installation/manual/frontend_install.md" %}}) is based on operating system packages for the most widely-used Linux distributions and is the same for any underlying hypervisor or deployment model.
 
-If you are planning for a system with a very large number of hypervisors, don’t forget to read the [Large-scale Deployment]({{% relref "../../../product/control_plane_configuration/large-scale_deployment/overview#large-scale-deployment-overview" %}}) section of the documentation. The general recommendation is that each OpenNebula instance can handle up to 2500 servers and 10,000 VMs. Better performance and higher scalability can be achieved by tuning other components, such as the database where the state of the cloud is persisted. To grow the size of your cloud beyond the limits mentioned above, you can horizontally scale the cloud by adding new OpenNebula Zones within a federated deployment. The largest OpenNebula deployment consists of 16 data centers and 300,000 cores.
+If you are planning for a system with a very large number of hypervisors, don’t forget to read the [Large-scale Deployment]({{% relref "product/control_plane_configuration/large-scale_deployment/overview#large-scale-deployment-overview" %}}) section of the documentation. The general recommendation is that each OpenNebula instance can handle up to 2500 servers and 10,000 VMs. Better performance and higher scalability can be achieved by tuning other components, such as the database where the state of the cloud is persisted. To grow the size of your cloud beyond the limits mentioned above, you can horizontally scale the cloud by adding new OpenNebula Zones within a federated deployment. The largest OpenNebula deployment consists of 16 data centers and 300,000 cores.
 
-To reduce downtime of core OpenNebula services, you can optionally set up a [High-availability Cluster]({{% relref "../../../product/control_plane_configuration/high_availability/frontend_ha#frontend-ha-setup" %}}). If planning for a large-scale infrastructure, you can [configure a MySQL/MariaDB backend]({{% relref "../../../software/installation_process/manual_installation/database.md#mysql" %}}) as an alternative to the default SQLite backend.
+To reduce downtime of core OpenNebula services, you can optionally set up a [High-availability Cluster]({{% relref "/product/control_plane_configuration/high_availability/frontend_ha#frontend-ha-setup" %}}). If planning for a large-scale infrastructure, you can [configure a MySQL/MariaDB backend]({{% relref "software/installation_process/frontend_installation/manual/database.md#mysql" %}}) as an alternative to the default SQLite backend.
 
-A single OpenNebula Front-end can manage multiple Clusters geographically distributed across several data centers and cloud providers. However, you can choose a multi-Zone deployment with [data center federation]({{% relref "../../../product/control_plane_configuration/data_center_federation/overview#introf" %}}) if data centers belong to different administrative domains or if connectivity between them does not meet latency and bandwidth requirements. Multiple OpenNebula Zones can be configured as a federation, where they will share the same user accounts, groups, and permissions across data centers.
+A single OpenNebula Front-end can manage multiple Clusters geographically distributed across several data centers and cloud providers. However, you can choose a multi-Zone deployment with [data center federation]({{% relref "product/control_plane_configuration/data_center_federation/overview#introf" %}}) if data centers belong to different administrative domains or if connectivity between them does not meet latency and bandwidth requirements. Multiple OpenNebula Zones can be configured as a federation, where they will share the same user accounts, groups, and permissions across data centers.
 
-Besides connecting your cloud to the public [OpenNebula Marketplace and other third-party Marketplaces]({{% relref "../../../product/apps-marketplace/public_marketplaces/index#public-marketplaces" %}}), you can build your own [private Marketplace]({{% relref "../../../product/apps-marketplace/private_marketplaces/overview#private-marketplace-overview" %}}) to provide your users with an easy way of privately publishing, downloading, and sharing your own custom appliances.
+Besides connecting your cloud to the public [OpenNebula Marketplace and other third-party Marketplaces]({{% relref "product/apps-marketplace/public_marketplaces/index#public-marketplaces" %}}), you can build your own [private Marketplace]({{% relref "product/apps-marketplace/private_marketplaces/overview#private-marketplace-overview" %}}) to provide your users with an easy way of privately publishing, downloading, and sharing your own custom appliances.
 
 ## Step 2. Deploy Edge Clusters
 

diff --git a/...etting_started/understand_opennebula/opennebula_concepts/opennebula_overview.md b/...etting_started/understand_opennebula/opennebula_concepts/opennebula_overview.md
@@ -147,6 +147,6 @@ The Getting Started Guide is by far the fastest way to familiarize yourself with
 
 If you are interested in building a production environment, then [Cloud Architecture Design]({{% relref "../cloud_architecture_and_design/cloud_architecture_design#intro" %}}) is a good resource to explore and consider the available options and choices.
 
-If you are interested in automatic, DevOps-like deployment of a production-ready OpenNebula cloud, please refer to the [Automatic Deployment]({{% relref "../../../software/installation_process/automatic_installation_with_onedeploy/index#automatic-deployment" %}}) section of the Installation Guide.
+If you are interested in automatic, DevOps-like deployment of a production-ready OpenNebula cloud, please refer to the [Automatic Deployment]({{% relref "../../../software/installation_process/advanced_installation_with_onedeploy/index#automatic-deployment" %}}) section of the Installation Guide.
 
 Remember that if you need our support at any time, or access to our professional services or to the **Enterprise Edition**, you can always [contact us](https://opennebula.io/enterprise).
diff --git a/content/product/cloud_system_administration/prometheus/install.md b/content/product/cloud_system_administration/prometheus/install.md
@@ -12,11 +12,11 @@ weight: "2"
 
 <!--# Installation and Configuration -->
 
-This page describes how to install the OpenNebula Prometheus integration packages available in the [OpenNebula software repositories]({{% relref "../../../software/installation_process/manual_installation/opennebula_repository_configuration#repositories" %}}).
+This page describes how to install the OpenNebula Prometheus integration packages available in the [OpenNebula software repositories]({{% relref "software/installation_process/frontend_installation/manual/opennebula_repository_configuration" %}}).
 
 ## Step 1. OpenNebula Repositories [Front-end, Hosts]
 
-At this point OpenNebula software repositories should already be configured in your Front-end and Hosts. Double check this is the case before proceeding, more information can be found in the [OpenNebula Repositories]({{% relref "../../../software/installation_process/manual_installation/opennebula_repository_configuration#repositories" %}}) guide.
+At this point OpenNebula software repositories should already be configured in your Front-end and Hosts. Double check this is the case before proceeding, more information can be found in the [OpenNebula Repositories]({{% relref "software/installation_process/frontend_installation/manual/opennebula_repository_configuration" %}}) guide.
 
 ## Step 2. Install Front-end Packages [Front-end]
 

diff --git a/content/product/cloud_system_administration/prometheus/overview.md b/content/product/cloud_system_administration/prometheus/overview.md
@@ -21,7 +21,7 @@ This Chapter contains documentation on how to configure OpenNebula to work with
 
 ## How Should I Read This Chapter
 
-Before reading this Chapter, you should have already installed your [Front-end]({{% relref "../../../software/installation_process/manual_installation/front_end_installation.md#frontend-installation" %}}) and [KVM Hosts]({{% relref "../../../software/installation_process/manual_installation/front_end_installation.md#kvm-node" %}}), and have an OpenNebula cloud up and running with at least one virtualization node.
+Before reading this Chapter, you should have already installed your [Front-end]({{% relref "software/installation_process/frontend_installation/manual/frontend_install.md#frontend-installation" %}}) and [KVM Hosts]({{% relref "software/installation_process/frontend_installation/manual/frontend_install.md#kvm-node" %}}), and have an OpenNebula cloud up and running with at least one virtualization node.
 
 This Chapter is structured as follows:
 

diff --git a/content/product/cloud_system_administration/resource_monitoring/overview.md b/content/product/cloud_system_administration/resource_monitoring/overview.md
@@ -21,7 +21,7 @@ This Chapter provides documentation on how different resources are monitored in
 
 ## How Should I Read This Chapter
 
-Before proceeding with this Chapter, ensure you have already installed your [Front-end]({{% relref "../../../software/installation_process/manual_installation/front_end_installation#frontend-installation" %}}), configured [KVM Hosts]({{% relref "../../../software/installation_process/manual_installation/kvm_node_installation#kvm-node" %}}), and set up an OpenNebula cloud with at least one virtualization node.
+Before proceeding with this Chapter, ensure you have already installed your [Front-end]({{% relref "software/installation_process/frontend_installation/manual/frontend_install" %}}), configured [KVM Hosts]({{% relref "/software/installation_process/cluster_installation/kvm_node_installation#kvm-node" %}}), and set up an OpenNebula cloud with at least one virtualization node.
 
 This Chapter is organized as follows:
 

diff --git a/content/product/cluster_configuration/backup_system/overview.md b/content/product/cluster_configuration/backup_system/overview.md
@@ -22,7 +22,7 @@ Define backup datastores by using the available options for backends or datastor
 
 ## Basic Guide Outline
 
-Before reading this guide, you should have installed your [Frontend]({{% relref "front_end_installation" %}}), the [KVM Hosts]({{% relref "kvm_node_installation#kvm-node" %}}) and have an OpenNebula cloud up and running with at least one virtualization node.
+Before reading this guide, you should have installed your [Frontend]({{% relref "frontend_install" %}}), the [KVM Hosts]({{% relref "kvm_node_installation#kvm-node" %}}) and have an OpenNebula cloud up and running with at least one virtualization node.
 
 To configure your backup system, find about datastore driver options to save your VM backups:
 * [Restic backend]({{% relref "restic#vm-backups-restic" %}}) 

diff --git a/content/product/cluster_configuration/backup_system/veeam.md b/content/product/cluster_configuration/backup_system/veeam.md
@@ -151,20 +151,20 @@ onecluster adddatastore <cluster-name> <datastore-name>
 SELinux and AppArmor may cause issues in the backup server if not configured properly. Either disable them or make sure to provide permissions to the datastore directories (``/var/lib/one/datastores``).
 {{< /alert >}}
 
-You can find more details regarding the Rsync datastore in [Backup Datastore: Rsync]({{% relref "../../../product/cluster_configuration/backup_system/rsync.md" %}}).
+You can find more details regarding the Rsync datastore in [Backup Datastore: Rsync]({{% relref "product/cluster_configuration/backup_system/rsync.md" %}}).
 
 
 
 ### 3. Install and configure the oVirtAPI module
 
-In order to install the oVirtAPI module, you need to have the OpenNebula repository configured in the backup server. You can do so by following the instructions in [OpenNebula Repositories]({{% relref "../../../software/installation_process/manual_installation/opennebula_repository_configuration.md" %}}). Then, install the opennebula-ovirtapi package.
+In order to install the oVirtAPI module, you need to have the OpenNebula repository configured in the backup server. You can do so by following the instructions in [OpenNebula Repositories]({{% relref "software/installation_process/frontend_installation/manual/opennebula_repository_configuration.md" %}}). Then, install the opennebula-ovirtapi package.
 
 The configuration file can be found at ``/etc/one/ovirtapi-server.yml``. You should change the following variables before starting the service:
 
 * ``one_xmlrpc``: Address of the OpenNebula Front-end. Please do not include any prefixes such as ``http://``, only the IP address itself is needed.
 * ``endpoint_port``: Port used by the OpenNebula RPC endpoint (defaults to 2633).
 * ``public_ip``: Address that Veeam is going to use to communicate with the ovirtapi server.
-* ``backup_freeze``: (Optional) Controls which filesystem freeze mode OpenNebula requests when performing backups initiated via the oVirtAPI/Veeam integration. Valid values are `NONE`, `AGENT`, and `SUSPEND`. For details on each mode see the Backup Modes section in the backup guide: [Backup Modes]({{% relref "../../../product/virtual_machines_operation/virtual_machine_backups/operations/#backup-modes" %}}).
+* ``backup_freeze``: (Optional) Controls which filesystem freeze mode OpenNebula requests when performing backups initiated via the oVirtAPI/Veeam integration. Valid values are `NONE`, `AGENT`, and `SUSPEND`. For details on each mode see the Backup Modes section in the backup guide: [Backup Modes]({{% relref "product/virtual_machines_operation/virtual_machine_backups/operations/#backup-modes" %}}).
 
 {{< alert title="Important" type="info" >}}
 You may see the 5554 port in the ``public_ip`` variable in the default settings, this is no longer needed so avoid using it. Leave only the IP address in the variable, no port needed.

diff --git a/content/product/control_plane_configuration/data_center_federation/config.md b/content/product/control_plane_configuration/data_center_federation/config.md
@@ -30,7 +30,7 @@ The federation can be set up with MySQL/MariaDB or SQLite as backends, but you c
 
 ## Step 1. Configure the OpenNebula Federation Master Zone
 
-Start by picking an OpenNebula to act as master of the federation. The *master* OpenNebula will be responsible for updating shared information across Zones and replicating the updates to the *slaves*. You may start with an existing installation or with a new one (see the [installation guide]({{% relref "front_end_installation" %}})).
+Start by picking an OpenNebula to act as master of the federation. The *master* OpenNebula will be responsible for updating shared information across Zones and replicating the updates to the *slaves*. You may start with an existing installation or with a new one (see the [installation guide]({{% relref "frontend_install" %}})).
 
 {{< alert title="Note" type="info" >}}
 When installing a new *master* from scratch be sure to start it at least once to properly bootstrap the database.{{< /alert >}} 
@@ -60,7 +60,7 @@ You are now ready to add *slave* Zones.
 
 ## Step 2. Adding a New Federation Slave Zone
 
-- **Slave**: Install OpenNebula on the *slave* as usual following the [installation guide]({{% relref "front_end_installation" %}}). Start OpenNebula at least once to bootstrap the Zone database.
+- **Slave**: Install OpenNebula on the *slave* as usual following the [installation guide]({{% relref "frontend_install" %}}). Start OpenNebula at least once to bootstrap the Zone database.
 - **Slave**: Stop OpenNebula.
 - **Master**: Create a Zone for the *slave* and write down the new Zone ID. This can be done via Sunstone or with the onezone command.
 

diff --git a/content/product/control_plane_configuration/data_center_federation/overview.md b/content/product/control_plane_configuration/data_center_federation/overview.md
@@ -33,7 +33,7 @@ Although a single Sunstone server can connect to different Zones, all the other
 
 ## How Should I Read This Chapter
 
-Before starting, it’s required to have at least two new instances of [OpenNebula Front-end]({{% relref "front_end_installation" %}}) ready to configure as Federation.
+Before starting, it’s required to have at least two new instances of [OpenNebula Front-end]({{% relref "frontend_install" %}}) ready to configure as Federation.
 
 Start by reading the [Federation Configuration]({{% relref "config#federationconfig" %}}) section to learn how to set-up the OpenNebula Federation, and continue with [Federation Usage]({{% relref "usage#federationmng" %}}) to learn how to use the Zones with CLI and Sunstone GUI.
 

diff --git a/content/product/control_plane_configuration/high_availability/overview.md b/content/product/control_plane_configuration/high_availability/overview.md
@@ -16,7 +16,7 @@ OpenNebula provides high availability mechanisms both for the Front-end and for
 
 ## How Should I Read This Chapter
 
-Before starting, you need to have [OpenNebula Front-end]({{% relref "front_end_installation" %}}) running.
+Before starting, you need to have [OpenNebula Front-end]({{% relref "frontend_install" %}}) running.
 
 Read the section [Front-end HA Setup]({{% relref "frontend_ha#frontend-ha-setup" %}}) to learn how to set up a highly available (HA) OpenNebula Front-end. Continue with [Virtual Machines High Availability]({{% relref "vm_ha#ftguide" %}}) if you are interested in a way to provide high availability to your Virtual Machines.