F OpenNebula/one#7563: Installation procedures restructure (#629)

This PR includes overview documentation for the restructuring of the Installation Procedures documentation.

Author: mattrowe-opennebula

assets/images/one_deploy_arch_shared.svg

@@ -29,11 +29,11 @@ For a sequential outline of the tasks involved in designing an OpenNebula cloud,
 
 ## Step 1. Install the Front-end
 
-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.
+The first step is the installation of the OpenNebula Front-end. The [installation process]({{% relref "software/installation_process/frontend_installation/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.
 
-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.
+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/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.
 

content/getting_started/understand_opennebula/cloud_architecture_and_design/cloud_architecture_design.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/frontend_installation/manual/opennebula_repository_configuration" %}}).
+This page describes how to install the OpenNebula Prometheus integration packages available in the [OpenNebula software repositories]({{% relref "software/installation_process/frontend_installation/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/frontend_installation/manual/opennebula_repository_configuration" %}}) 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/opennebula_repository_configuration" %}}) guide.
 
 ## Step 2. Install Front-end Packages [Front-end]
 

content/product/cloud_system_administration/prometheus/install.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/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.
+Before reading this Chapter, you should have already installed your [Front-end]({{% relref "software/installation_process/frontend_installation/frontend_install.md#frontend-installation" %}}) and [KVM Hosts]({{% relref "software/installation_process/frontend_installation/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:
 

content/product/cloud_system_administration/prometheus/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/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.
+Before proceeding with this Chapter, ensure you have already installed your [Front-end]({{% relref "software/installation_process/frontend_installation/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:
 

content/product/cloud_system_administration/resource_monitoring/overview.md

@@ -157,7 +157,7 @@ You can find more details regarding the Rsync datastore in [Backup Datastore: Rs
 
 ### 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/frontend_installation/manual/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/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:
 

content/product/cluster_configuration/backup_system/veeam.md

@@ -24,7 +24,7 @@ Through these guides Virtual Machine or VM is used as a generic abstraction that
 
 ## How Should I Read This Chapter
 
-Before reading this Chapter, you should have already installed your [Front-end]({{% relref "software/installation_process/frontend_installation/manual/frontend_install.md" %}}), the [KVM Hosts]({{% relref "software/installation_process/cluster_installation/kvm_node_installation.md" %}}) or [LXC Hosts]({{% relref "../../software/installation_process/cluster_installation/kvm_node_installation.md" %}}) 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/frontend_install.md" %}}), the [KVM Hosts]({{% relref "software/installation_process/cluster_installation/kvm_node_installation.md" %}}) or [LXC Hosts]({{% relref "../../software/installation_process/cluster_installation/kvm_node_installation.md" %}}) and have an OpenNebula cloud up and running with at least one virtualization node.
 
 ## Hypervisor Compatibility
 

content/product/virtual_machines_operation/_index.md

@@ -1,7 +1,8 @@
 ---
-title: "Installation Process"
+title: "OpenNebula Installation Process"
+linkTitle: "Installation Process"
 date: "2025-02-17"
-description: "Choose the best installation method for your needs -- from automatic installation of a complete OpenNebula cloud, to customized installation of individual components, to compiling from source code for building your own infrastructure and integrations."
+description: "OpenNebula installation processes, including manual and automated options."
 categories:
 pageintoc: "168"
 tags:
@@ -10,12 +11,4 @@ weight: "3"
 
 <a id="package-installation-references"></a>
 
-<a id="ocd"></a>
-
-<a id="vmmg"></a>
-
-<a id="open-cluster-deployment"></a>
-
-<!--# Package Installation References -->
-
-These sections provide details on installing an OpenNebula cloud, beginning with the OpenNebula Front-end and including services and hypervisors. The complete references for configuring OpenNebula services, templates, and hypervisor nodes may be found in [Operation References]({{% relref "../../../product/operation_references/" %}}).
+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.

content/software/installation_process/_index.md

@@ -20,7 +20,7 @@ In this tutorial, we’ll use [OneDeploy](https://github.com/OpenNebula/one-depl
 
 This sample architecture uses a basic network configuration, a flat (bridged) network, where each VM’s IPs is part of the same network as the Hypervisors.
 
-![><](/images/one_deploy_arch_shared.png)
+{{< image path="/images/one_deploy_arch_shared.svg" alt="OneDeploy" align="center" width="80%" mb="20px" border="false" shadow="false">}}
 
 Throughout the tutorial we’ll use three server machines, please be sure to replace these references to your own IP addresses:
 

content/software/installation_process/advanced_installation_with_onedeploy/one_deploy_tutorial_shared_ds.md

@@ -10,3 +10,4 @@ weight: "2"
 
 <a id="cluster-installation"></a>
 
+OpenNebula Clusters are logical groupings of Hosts, datastores and Virtual Networks that provide compute capacity for cloud workloads. To install or automatically provision Clusters with OpenNebula, you must first deploy an OpenNebula Front-end, please refer to the [Front-end Installation Documentation]({{% relref "software/installation_process/frontend_installation/" %}}) for details.