Fix relative links in adhoc tutorials (#600)

Fix relative links in tutorials moved to adhoc section.

content/en/users/tutorials/adhoc/accessing-vm-with-ssh/_index.md

@@ -38,7 +38,7 @@ machine image and is generally different in each operating system image:
   [obtaining images](https://docs.openstack.org/image-guide/obtain-images.html).
 - For custom virtual machine images you need to refer to your virtual machine image
   provider (i.e. it could be something specific like `cloudadm`).
-- For virtual machines deployed with [Infrastructure Manager](../../compute/orchestration/im/)
+- For virtual machines deployed with [Infrastructure Manager](../../../compute/orchestration/im/)
   the default username is `cloudadm`.
 
 > It is also possible to change the username using `cloud-init` with a user-data
@@ -201,9 +201,9 @@ $ ssh centos@192.168.1.3
 
 ## Infrastructure Manager (IM)
 
-The [Infrastructure Manager (IM)](../../compute/orchestration/im/) provides the SSH key that can be used to connect
+The [Infrastructure Manager (IM)](../../../compute/orchestration/im/) provides the SSH key that can be used to connect
 to the virtual machine in the VM
-[info page of the IM-Dashboard](../../compute/orchestration/im/dashboard/#vm-info-page).
+[info page of the IM-Dashboard](../../../compute/orchestration/im/dashboard/#vm-info-page).
 
 The page shows the information related with the virtual machine: the IP, the
 username (usually `cloudadm`), and the SSH key.

content/en/users/tutorials/adhoc/create-your-first-virtual-machine/_index.md

@@ -14,13 +14,13 @@ This tutorial describes how to create your first Virtual Machine in the EGI Fede
 
 ## Step 1: Signing up
 
-Create an EGI account with [Check-in](../../aai/check-in/signup).
+Create an EGI account with [Check-in](../../../aai/check-in/signup).
 
 ## Step 2: Enrolling to a Virtual Organisation
 
 Once your EGI account is ready you need to join a
 [Virtual Organisation (VO)](https://confluence.egi.eu/display/EGIG/Virtual+organisation).
-Here are the steps to [join a VO](../../aai/check-in/joining-virtual-organisation/).
+Here are the steps to [join a VO](../../../aai/check-in/joining-virtual-organisation/).
 Explore the list of available VOs in the
 [Operations Portal](https://operations-portal.egi.eu/vo/a/list).
 We have a dedicated VO called
@@ -31,20 +31,20 @@ access to the _vo.access.egi.eu_ VO with your EGI account by visiting the
 [AppDB](https://appdb.egi.eu/store/vo/vo.access.egi.eu) to see the list of
 Virtual Appliances and Resource Providers participating in the _vo.access.egi.eu_ VO.
 AppDB is one of the service in the
-[EGI Architecture](../../getting-started/architecture/).
+[EGI Architecture](../../../getting-started/architecture/).
 
 ## Step 3: Creating a VM
 
 Once your membership to a VO has been approved you are ready to create your first
 Virtual Machine. There are several ways to achieve this. The simplest way is to
-use a web dashboard like [VMOps Dashboard](../../compute/cloud-compute/monitor) or
-[Infrastructure Manager Dashboard](../../compute/orchestration/im/dashboard).
+use a web dashboard like [VMOps Dashboard](../../../compute/cloud-compute/monitor) or
+[Infrastructure Manager Dashboard](../../../compute/orchestration/im/dashboard).
 On the other hand, advanced users
-may prefer to use the [command-line interface](../../getting-started/cli).
+may prefer to use the [command-line interface](../../../getting-started/cli).
 
 To know more about the [Cloud Compute](https://www.egi.eu/service/cloud-compute/)
-Service in EGI please visit its [dedicated section](../../compute/cloud-compute).
+Service in EGI please visit its [dedicated section](../../../compute/cloud-compute).
 
 ## Asking for help
 
-If you find issues please do not hesitate to [contact us](../../../support/).
+If you find issues please do not hesitate to [contact us](../../../../support/).

content/en/users/tutorials/adhoc/data-transfer-grid-storage/_index.md

@@ -22,17 +22,17 @@ to perform data transfers between two Grid storage.
 ## Prerequisites
 
 As first step please make sure that you have installed the FTS client as
-described in [Data Transfer](../../data/management/data-transfer), and in particular
-[Clients](../../data/management/data-transfer/clients) for the command-line FTS and to have
+described in [Data Transfer](../../../data/management/data-transfer), and in particular
+[Clients](../../../data/management/data-transfer/clients) for the command-line FTS and to have
 your certificate installed in your browser to use
-[WebFTS](../../data/management/data-transfer/webfts) browser based client.
+[WebFTS](../../../data/management/data-transfer/webfts) browser based client.
 
 To access services and resources in the
-[EGI Federated Cloud](../../getting-started), you will need:
+[EGI Federated Cloud](../../../getting-started), you will need:
 
-- An [EGI Check-in](../../aai/check-in) account, you can
-  [sign up here](../../aai/check-in/signup)
-- Enrollment into a [Virtual Organisation](../../aai/check-in/vos) (VO) that has
+- An [EGI Check-in](../../../aai/check-in) account, you can
+  [sign up here](../../../aai/check-in/signup)
+- Enrollment into a [Virtual Organisation](../../../aai/check-in/vos) (VO) that has
   access to the services and resources you need
 
 ## FTS client usage

content/en/users/tutorials/adhoc/data-transfer-object-storage/_index.md

@@ -28,19 +28,19 @@ repository to your configuration and update the client{{% /alert %}}
 ## Prerequisites
 
 As first step please make sure that you have installed the FTS client as
-described in [Data Transfer](../../data/management/data-transfer), and in
-particular [Clients](../../data/management/data-transfer/clients) for the
+described in [Data Transfer](../../../data/management/data-transfer), and in
+particular [Clients](../../../data/management/data-transfer/clients) for the
 command-line FTS and to have your certificate installed in your browser to use
-[WebFTS](../../data/management/data-transfer/webfts) browser based client.
+[WebFTS](../../../data/management/data-transfer/webfts) browser based client.
 
 To access services and resources in the
-[EGI Federated Cloud](../../getting-started), you will need:
+[EGI Federated Cloud](../../../getting-started), you will need:
 
-- An [EGI Check-in](../../aai/check-in) account, you can
-  [sign up here](../../aai/check-in/signup)
-- Enrollment into a [Virtual Organisation](../../aai/check-in/vos) (VO) that has
+- An [EGI Check-in](../../../aai/check-in) account, you can
+  [sign up here](../../../aai/check-in/signup)
+- Enrollment into a [Virtual Organisation](../../../aai/check-in/vos) (VO) that has
   access to the services and resources you need
-- An [Object Storage](../../data/storage/object-storage) for which you need to
+- An [Object Storage](../../../data/storage/object-storage) for which you need to
   have all the credentials available (any S3 compatible storage should work)
 - Permission to add the Object Storage credential to the FTS server or
   alternatively for this operation you may contact support **at** egi.eu.
@@ -58,7 +58,7 @@ As for the "Data transfer with grid storage" tutorial you can look for the
 available storage on
 [VAPOR service](https://operations-portal.egi.eu/vapor/resources/GL2ResVO) while
 the Object Store can be one created as described in the
-[Object Storage](../../data/storage/object-storage) section or trough a provider
+[Object Storage](../../../data/storage/object-storage) section or trough a provider
 such as Amazon, Azure, etc
 
 ### Step 3 Add the Object Storage credential to the FTS server

content/en/users/tutorials/adhoc/htc-job-submission/_index.md

@@ -11,7 +11,7 @@ description: >
 ## Overview
 
 This tutorial describes how to submit
-[High Throughput Compute (HTC)](../../compute/high-throughput-compute) jobs
+[High Throughput Compute (HTC)](../../../compute/high-throughput-compute) jobs
 using command-line.
 
 > This tutorial is meant for somewhat advanced users or the ones willing or
@@ -56,7 +56,7 @@ In order to help with deploying an UI, different solutions are possible:
 - Deploying an UI manually, using the packages available from
   [UMD repositories](https://go.egi.eu/umd). You will need to install at least
   the `ui` meta-package, the
-  [IGTF distribution](../../../providers/operations-manuals/howto01_using_igtf_ca_distribution),
+  [IGTF distribution](../../../../providers/operations-manuals/howto01_using_igtf_ca_distribution),
   and
   [configure the system to use voms-client](#configuring-the-system-to-use-voms-client).
 - Some
@@ -75,7 +75,7 @@ In order to help with deploying an UI, different solutions are possible:
   [ui-deployment](https://github.com/EGI-Federation/ui-deployment) provides a
   [terraform](https://terraform.io) based deployment allowing to deploy a
   `User Interface (UI)` in a
-  [Cloud Compute virtual machine](../../compute/cloud-compute). This integrated
+  [Cloud Compute virtual machine](../../../compute/cloud-compute). This integrated
   deployment is based on the Ansible modules, and should be adjusted to your
   environment and needs.
 
@@ -104,7 +104,7 @@ using the proper `.vomses` and `.lsc` files, based on the information available
 on the VOMS server of the specific VO.
 
 - as an example with `dteam`, you can find the VOMS server address in the
-  [Operations Portal](../../../internal/operations-portal):
+  [Operations Portal](../../../../internal/operations-portal):
   [https://operations-portal.egi.eu/vo/view/voname/dteam](https://operations-portal.egi.eu/vo/view/voname/dteam).
   Then looking at
   [dteam VOMS configuration](https://voms2.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action),
@@ -202,7 +202,7 @@ key usage : Digital Signature, Key Encipherment
 ## Step 3: identifying available resources
 
 It is possible to identify available resources by
-[querying the information system](../../compute/high-throughput-compute/querying-information-system).
+[querying the information system](../../../compute/high-throughput-compute/querying-information-system).
 
 Two Computing Element (CE) "flavours" are used in production:
 
@@ -215,13 +215,13 @@ In this section we will document querying the EGI Information System to retrieve
 information about the available resources.
 
 {{% alert title="Tip" color="info" %}} It's also possible to use
-[VAPOR to query resources using a graphical interface](../../../internal/operations-portal/using-vapor#using-vapor-to-query-resources-using-a-graphical-interface).
+[VAPOR to query resources using a graphical interface](../../../../internal/operations-portal/using-vapor#using-vapor-to-query-resources-using-a-graphical-interface).
 {{% /alert %}}
 
 ### Use case: identifying all the Computing Elements supporting the dteam VO
 
 As documented in the pages covering the
-[querying of the Information System](../../compute/high-throughput-compute/querying-information-system),
+[querying of the Information System](../../../compute/high-throughput-compute/querying-information-system),
 in **GLUE 2.0**, the access granted to a given VO to a compute or storage
 resource, is published using the `GLUE2Share` and `GLUE2Policy` objects. The
 `GLUE2ComputingShare` object specifically documents sharing of compute
@@ -582,7 +582,6 @@ $ glite-ce-job-output "$JOB_ID"
 #### References
 
 - [CREAM User's guide](https://cream-guide.readthedocs.io/en/latest/User_Guide.html)
-- [CREAM User's Guide for EMI-3](https://wiki-igi.cnaf.infn.it/twiki/bin/view/CREAM/UserGuideEMI3)
 
 ### Via the EGI Workload Manager
 
@@ -591,11 +590,11 @@ $ glite-ce-job-output "$JOB_ID"
 > computing workloads on the EGI infrastructure.
 
 Using the
-[Workload Manger web interface](../../compute/orchestration/workload-manager/#the-egi-workload-manager-web-portal)
+[Workload Manger web interface](../../../compute/orchestration/workload-manager/#the-egi-workload-manager-web-portal)
 or the
-[DIRAC command-line interface (CLI)](../../compute/orchestration/workload-manager/#the-dirac-client-tool)
+[DIRAC command-line interface (CLI)](../../../compute/orchestration/workload-manager/#the-dirac-client-tool)
 is documented in the
-[EGI Workload Manager](../../compute/orchestration/workload-manager).
+[EGI Workload Manager](../../../compute/orchestration/workload-manager).
 
 ### Troubleshooting
 
@@ -613,4 +612,4 @@ the CRITICAL button).
 
 ## Asking for help
 
-If you find issues please do not hesitate to [contact us](../../../support/).
+If you find issues please do not hesitate to [contact us](../../../../support/).

content/en/users/tutorials/adhoc/jupyter-datahub-virtual-machine/_index.md

@@ -21,7 +21,7 @@ synchronise images from AppDB but is not part of the federation.
 This tutorial assumes you have:
 
 - A valid EGI account: learn to can create one in
-  [Check-in](../../aai/check-in/signup).
+  [Check-in](../../../aai/check-in/signup).
 - Access to a cloud provider where the
   [Jupyter DataHub VM is available](https://appdb.egi.eu/store/vappliance/jupyter.datahub.vm).
   Alternatively, this VM can be run on your computer using a virtualisation tool
@@ -37,7 +37,7 @@ learn how to start a VM at EGI's Federated Cloud infrastructure.
 
 This VM does not contain any default credentials, in order to access it you need
 a ssh key. Check
-[this FAQ entry](../../compute/cloud-compute/faq/#how-can-i-inject-my-public-ssh-key-into-the-machine)
+[this FAQ entry](../../../compute/cloud-compute/faq/#how-can-i-inject-my-public-ssh-key-into-the-machine)
 for more information. If you are starting this VM on VirtualBox, you will need
 to pass some valid context for cloud-init, see
 [here how to prepare it](https://superuser.com/a/853957).
@@ -47,7 +47,7 @@ accessing the notebooks interface. Make sure your have those ports open on your
 security groups, otherwise you will not be able to reach the Jupyter notebooks.
 
 Once your instance is ready,
-[assign it a public IP](../../compute/cloud-compute/faq/#how-can-i-assign-a-public-ip-to-my-vm)
+[assign it a public IP](../../../compute/cloud-compute/faq/#how-can-i-assign-a-public-ip-to-my-vm)
 so you can reach it from your computer.
 
 ### Step 2: Get a hostname and certificate for your VM
@@ -63,7 +63,7 @@ safer and more secure.
 
 Firstly, you need a valid name for your VM. You can use the
 [FedCloud Dynamic DNS](https://nsupdate.fedcloud.eu) to create a name. See
-[Dynamic DNS docs](../../compute/cloud-compute/dynamic-dns/) for more
+[Dynamic DNS docs](../../../compute/cloud-compute/dynamic-dns/) for more
 information on the service. Once you have your name ready, assign it your VM's
 IP.
 
@@ -136,12 +136,12 @@ $ micromamba install -c conda-forge tensorflow
 ### Step 5: Mount DataHub spaces
 
 Log into [EGI's DataHub](https://datahub.egi.eu/) and
-[create a token](../../data/management/datahub/clients/#generating-tokens-for-using-oneclient-or-apis)
+[create a token](../../../data/management/datahub/clients/#generating-tokens-for-using-oneclient-or-apis)
 for mounting your data in the VM.
 
 You will also need the IP or address of your closest Oneprovider for the spaces
 you are interested in accessing. This information is easily obtainable via
-[DataHub's web interface](../../data/management/datahub/clients/#using-the-web-interface).
+[DataHub's web interface](../../../data/management/datahub/clients/#using-the-web-interface).
 
 Go to your Jupyter session in your browser and edit the `mount.sh` file in your
 home directory. Set the `ONECLIENT_ACCESS_TOKEN` and `ONECLIENT_PROVIDER_HOST`

content/en/users/tutorials/adhoc/oidc-agent-fedcloudclient-terraform/_index.md

@@ -13,25 +13,25 @@ description: >
 
 This tutorial describes how to create a Virtual Machine in the EGI Federation,
 leveraging [oidc-agent](https://indigo-dc.gitbook.io/oidc-agent/) to retrieve
-ODIC tokens from [EGI Check-in](../../aai/check-in),
+ODIC tokens from [EGI Check-in](../../../aai/check-in),
 [fedcloudclient](https://fedcloudclient.fedcloud.eu/) to simplify interacting
-with the [EGI Cloud Compute service](../../compute/cloud-compute),
+with the [EGI Cloud Compute service](../../../compute/cloud-compute),
 [terraform](https://www.terraform.io) and [Ansible](https://www.ansible.com/) to
 simplify deploying an infrastructure.
-[EGI Dynamic DNS](../../compute/cloud-compute/dynamic-dns) is also used to
+[EGI Dynamic DNS](../../../compute/cloud-compute/dynamic-dns) is also used to
 assign a domain name to the virtual machine, which can then be used to get a
 valid TLS certificate from [Let's Encrypt](https://letsencrypt.org/).
 
 ## Step 1: Signing up for an EGI Check-in account
 
-Create an EGI account with [Check-in](../../aai/check-in/signup).
+Create an EGI account with [Check-in](../../../aai/check-in/signup).
 
 ## Step 2: Enrolling to a Virtual Organisation
 
 Once your EGI account is ready you need to join a
 [Virtual Organisation (VO)](https://confluence.egi.eu/display/EGIG/Virtual+organisation).
 Here are the steps to
-[join a VO](../../aai/check-in/joining-virtual-organisation/). Explore the list
+[join a VO](../../../aai/check-in/joining-virtual-organisation/). Explore the list
 of available VOs in the
 [Operations Portal](https://operations-portal.egi.eu/vo/a/list). We have a
 dedicated VO called
@@ -42,7 +42,7 @@ the [enrolment URL](https://aai.egi.eu/registry/co_petitions/start/coef:240).
 Check [AppDB](https://appdb.egi.eu/store/vo/vo.access.egi.eu) to see the list of
 Virtual Appliances and Resource Providers participating in the
 _vo.access.egi.eu_ VO. AppDB is one of the service in the
-[EGI Architecture](../../getting-started/architecture/).
+[EGI Architecture](../../../getting-started/architecture/).
 
 > This tutorial will assume you are using `vo.access.egi.eu`, adapt as required
 > for your specific environment.
@@ -53,8 +53,8 @@ Once your membership to a VO has been approved you are ready to create your
 first Virtual Machine.
 
 The OpenID Connect (OIDC) protocol is used to authenticate users and authorise
-access to [Cloud Compute](../../compute/cloud-compute/) resources that are
-integrated with [EGI Check-in](../../aai/check-in/).
+access to [Cloud Compute](../../../compute/cloud-compute/) resources that are
+integrated with [EGI Check-in](../../../aai/check-in/).
 
 While it's not mandatory, a convenient way to manage the OIDC token is to use
 [oidc-agent](#setting-up-oidc-agent).
@@ -172,7 +172,7 @@ You can retrieve information from the AppDB about the sites supporting the
 ### Deploying the Virtual Machine with terraform
 
 Instead of creating the server manually, it is possible to use
-[terraform with EGI Cloud Compute](../../compute/cloud-compute/openstack/#terraform).
+[terraform with EGI Cloud Compute](../../../compute/cloud-compute/openstack/#terraform).
 
 The
 [Terraform OpenStack provider](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs)
@@ -386,7 +386,7 @@ virtual machine using a fully qualified hostname and allowing to retrieve a
 [Let's Encrypt certificate](https://letsencrypt.org/).
 
 > Please look at the
-> [EGI Dynamic DNS documentation](../../compute/cloud-compute/dynamic-dns/) for
+> [EGI Dynamic DNS documentation](../../../compute/cloud-compute/dynamic-dns/) for
 > instructions on creating the configuration for a new host.
 
 The
@@ -542,4 +542,4 @@ cases, or be used as a source of inspiration:
 
 ## Asking for help
 
-If you find issues please do not hesitate to [contact us](../../../support/).
+If you find issues please do not hesitate to [contact us](../../../../support/).

content/en/users/tutorials/adhoc/vm-datahub/_index.md

@@ -10,7 +10,7 @@ description: >
 
 ## Overview
 
-This tutorial describes the access to [EGI DataHub](../../data/management/datahub) spaces
+This tutorial describes the access to [EGI DataHub](../../../data/management/datahub) spaces
 from a virtual machine. In the following paragraphs you will learn how to
 access data remotely stored in EGI DataHub like if they were local, using
 traditional POSIX command-line commands, by:
@@ -21,8 +21,8 @@ traditional POSIX command-line commands, by:
 ## Prerequisites
 
 In order to access the EGI DataHub data you need an
-[EGI Check-in](../../aai/check-in) account. If you don't have one yet
-you can [Sign up for an EGI account](../../aai/check-in/signup).
+[EGI Check-in](../../../aai/check-in) account. If you don't have one yet
+you can [Sign up for an EGI account](../../../aai/check-in/signup).
 
 ## Oneclient installation
 
@@ -60,7 +60,7 @@ ease the transfer of data.
 ## Getting the token to access data
 
 In order to access data stored in EGI DataHub via oneclient,
-you need to [get an API access token](../../data/management/datahub/api/#getting-an-api-access-token).
+you need to [get an API access token](../../../data/management/datahub/api/#getting-an-api-access-token).
 
 ## Using oneclient