Changes in Software chapter

Signed-off-by: Pedro Ielpi <pielpi@opennebula.io>

Author: pedroielpi3

content/7.0/product/cloud_clusters_infrastructure_configuration/hosts_and_clusters_configuration/overview.md

@@ -12,7 +12,7 @@ weight: "1"
 
 <!--# Overview -->
 
-A **Host** is a server that has the ability to run Virtual Machines and that is connected to OpenNebula’s Front-end server. To learn how to prepare the Hosts, you can read the [Installation]({{% relref "../../../releases/installation" %}}) guide. Hosts are usually grouped in **Clusters**.
+A **Host** is a server that has the ability to run Virtual Machines and that is connected to OpenNebula’s Front-end server. To learn how to prepare the Hosts, you can read the [Installation]({{% relref "../../../software/installation" %}}) guide. Hosts are usually grouped in **Clusters**.
 
 ## How Should I Read This Chapter
 

content/7.0/product/cloud_clusters_infrastructure_configuration/storage_system_configuration/overview.md

@@ -47,7 +47,7 @@ Each datastore supports different features, here is a basic overview:
 
 ## How Should I Read This Chapter
 
-Before reading this chapter make sure you are familiar with Node Deployment from the [Installation]({{% relref "../../../releases/installation" %}}) guide.
+Before reading this chapter make sure you are familiar with Node Deployment from the [Installation]({{% relref "../../../software/installation" %}}) guide.
 
 After that, proceed with the specific Datastore documentation you might be interested in.
 

content/7.0/product/cloud_system_administration/authentication_configuration/overview.md

@@ -41,7 +41,7 @@ This method is designed to delegate the authentication process to high level too
 
 OpenNebula ships with a GUI server - [Sunstone]({{% relref "../../operation_references/opennebula_services_configuration/fireedge#fireedge-setup" %}}). When a user interacts with one of them, the server authenticates the request and then forwards the requested operation to the OpenNebula Daemon. The forwarded requests are encrypted using a symmetric key. The following guide shows how to strengthen the security of these requests using X.509 certificates. This is especially relevant if you are running your server in a machine other than the Front-end.
 
-- [Cloud Servers Authentication]({{% relref "../../../releases/life_cycle_management/building_from_source_code/cloud_auth#cloud-auth" %}})
+- [Cloud Servers Authentication]({{% relref "../../../software/life_cycle_management/building_from_source_code/cloud_auth#cloud-auth" %}})
 
 ## How Should I Read This Chapter
 

content/7.0/product/cloud_system_administration/monitoring_and_alerting/configuration.md

@@ -38,7 +38,7 @@ The firewall on the Front-end (if enabled) must allow incoming TCP and UDP packe
 The monitor daemon (`onemonitord`) is configured in `/etc/one/monitord.conf`. The table below describes the file’s configuration attributes.
 
 {{< alert title="Tip" color="info" >}}
-For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the [Release Notes]({{% relref "../../../releases/release_information/release_notes_enterprise#rn-enterprise" %}}) for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application’s behavior.{{< /alert >}} 
+For a quick view of any changes in configuration file options in maintenance releases, check the Resolved Issues page in the [Release Notes]({{% relref "../../../software/release_information/release_notes_enterprise#rn-enterprise" %}}) for the release. Please note that even in the case of changes (such as a new option available), you do *not* need to update your configuration files unless you wish to change the application’s behavior.{{< /alert >}} 
 
 | Parameter                                                                                   | Attribute                                                                                                                                                                                              | Description                                                                      |
 |---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|

content/7.0/product/cloud_system_administration/monitoring_and_alerting/overview.md

@@ -21,7 +21,7 @@ This chapter provides documentation on how different resources are monitored in
 
 ## How to Use This Chapter
 
-Before proceeding with this chapter, ensure you have already installed your [Front-end]({{% relref "../../../releases/installation/front_end_installation#frontend-installation" %}}), configured [KVM Hosts]({{% relref "../../../releases/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/front_end_installation#frontend-installation" %}}), configured [KVM Hosts]({{% relref "../../../software/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/7.0/product/cloud_system_administration/monitoring_and_alerting/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 "../../../../releases/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/opennebula_repository_configuration#repositories" %}}).
 
 ## 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 "../../../../releases/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/opennebula_repository_configuration#repositories" %}}) guide.
 
 ## Step 2. Install Front-end Packages [Front-end]
 

content/7.0/product/cloud_system_administration/monitoring_and_alerting/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 "../../../../releases/installation/front_end_installation.md#frontend-installation" %}}) and [KVM Hosts]({{% relref "../../../../releases/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/front_end_installation.md#frontend-installation" %}}) and [KVM Hosts]({{% relref "../../../../software/installation/front_end_installation.md#kvm-node" %}}), and have an OpenNebula cloud up and running with at least one virtualization node.
 
 This Chapter is structured as follows:
 

content/7.0/product/operation_references/opennebula_services_configuration/database.md

@@ -252,7 +252,7 @@ Confirm to write to the database [Y/n]: y
 
 ### onedb upgrade
 
-Upgrades database to the new OpenNebula version. This process is fully documented in the [upgrade guides]({{% relref "../../../releases/release_information/upgrade/index#upgrade" %}}).
+Upgrades database to the new OpenNebula version. This process is fully documented in the [upgrade guides]({{% relref "../../../software/release_information/upgrade/index#upgrade" %}}).
 
 <a id="onedb-backup"></a>
 

content/7.0/product/operation_references/opennebula_services_configuration/oneflow.md

@@ -44,7 +44,7 @@ After a configuration change, the OneFlow server must be [restarted]({{% relref
 | `:vm_name_template`                   | Default name for the Virtual Machines created by Oneflow. You can use any of the following placeholders:<br/>`$SERVICE_ID`, `$SERVICE_NAME`, `$ROLE_NAME`, `$VM_NUMBER`.                                                                                                                                                                                                 |
 | `:page_size`                          | Default page size when purging DONE services                                                                                                                                                                                                                                                                                                                             |
 | **Authentication**                    |                                                                                                                                                                                                                                                                                                                                                                          |
-| `:core_auth`                          | Authentication driver to communicate with OpenNebula core<br/><br/>* `cipher` for symmetric cipher encryption of tokens<br/>* `x509` for X.509 certificate encryption of tokens<br/><br/>For more information, visit the [Cloud Server Authentication]({{% relref "../../../releases/life_cycle_management/building_from_source_code/cloud_auth#cloud-auth" %}}) reference. |
+| `:core_auth`                          | Authentication driver to communicate with OpenNebula core<br/><br/>* `cipher` for symmetric cipher encryption of tokens<br/>* `x509` for X.509 certificate encryption of tokens<br/><br/>For more information, visit the [Cloud Server Authentication]({{% relref "../../../software/life_cycle_management/building_from_source_code/cloud_auth#cloud-auth" %}}) reference. |
 | **Logging**                           |                                                                                                                                                                                                                                                                                                                                                                          |
 | `:debug_level`                        | Logging level. Values: `0` for ERROR level, `1` for WARNING level, `2` for INFO level, `3` for DEBUG level                                                                                                                                                                                                                                                               |
 | `:expire_delta`                       | Default interval for timestamps. Tokens will be generated using the same timestamp for this interval of time. THIS VALUE CANNOT BE LOWER THAN EXPIRE_MARGIN.                                                                                                                                                                                                             |

content/7.0/product/operation_references/opennebula_services_configuration/onegate.md

@@ -38,7 +38,7 @@ After a configuration change, the OneGate server must be [restarted]({{% relref
 | `:ssl_server`               | SSL proxy URL that serves the API (set if is being used)                                                                                                                                                                                                                                                                                                                 |
 | **Authentication**          |                                                                                                                                                                                                                                                                                                                                                                          |
 | `:auth`                     | Authentication driver for incoming requests.<br/><br/>* `onegate` based on tokens provided in VM context                                                                                                                                                                                                                                                                 |
-| `:core_auth`                | Authentication driver to communicate with OpenNebula core<br/><br/>* `cipher` for symmetric cipher encryption of tokens<br/>* `x509` for X.509 certificate encryption of tokens<br/><br/>For more information, visit the [Cloud Server Authentication]({{% relref "../../../releases/life_cycle_management/building_from_source_code/cloud_auth#cloud-auth" %}}) reference. |
+| `:core_auth`                | Authentication driver to communicate with OpenNebula core<br/><br/>* `cipher` for symmetric cipher encryption of tokens<br/>* `x509` for X.509 certificate encryption of tokens<br/><br/>For more information, visit the [Cloud Server Authentication]({{% relref "../../../software/life_cycle_management/building_from_source_code/cloud_auth#cloud-auth" %}}) reference. |
 | **OneFlow Endpoint**        |                                                                                                                                                                                                                                                                                                                                                                          |
 | `:oneflow_server`           | Endpoint where the OneFlow server is listening                                                                                                                                                                                                                                                                                                                           |
 | **Permissions**             |                                                                                                                                                                                                                                                                                                                                                                          |