Remove some links still pointing to wiki.egi.eu

content/en/internal/guidelines-software-development/_index.md

@@ -54,10 +54,10 @@ meant to be exhaustive, further research is welcome. {{% /alert %}}
 - Security best practices must be taken into account
 - Security-related aspects must be considered from the beginning
 - Security issues must be addressed in priority and following the
-  [EGI SVG recommendations](https://wiki.egi.eu/wiki/SVG) and must take into
-  account the points mentioned in the
-  [SVG Secure Coding](https://wiki.egi.eu/wiki/SVG:Secure_Coding) and
-  [Software Security Checklist](https://wiki.egi.eu/wiki/SVG:Software_Security_Checklist)
+  [EGI SVG recommendations](https://go.egi.eu/svg) and must take into account
+  the points mentioned in the
+  [SVG Secure Coding](https://confluence.egi.eu/display/EGIBG/Secure+Coding) and
+  [Software Security Checklist](https://confluence.egi.eu/display/EGIBG/Software+Security+Checklist)
 - The Open Web Application Security Project ([OWASP](https://owasp.org/))
   provides extensive documentation, standards (such as
   [ASVS](https://owasp.org/www-project-application-security-verification-standard/))
@@ -132,4 +132,4 @@ meant to be exhaustive, further research is welcome. {{% /alert %}}
 ## Request for information
 
 You can ask for more information about them by contacting us via
-[our site](https://www.egi.eu/more-information).
+[our site](https://www.egi.eu/contact-us).

content/en/providers/check-in/idp/_index.md

@@ -19,7 +19,7 @@ printed and signed copy should be sent to `operations_at_egi.eu`
 
 To integrate your Identity Provider with the EGI Check-in service, you need to
 submit a [GGUS](https://ggus.eu) ticket indicating your request. The responsible
-support unit is [AAI Support](https://wiki.egi.eu/wiki/GGUS:AAI_SUPPORT_FAQ).
+support unit is [AAI Support](https://confluence.egi.eu/display/EGIPP/GGUS%3A+Check-in+%28AAI%29+FAQ).
 The integration follows a two-step process:
 
 1. Register your Identity Provider and test integration with the development

content/en/providers/check-in/sp/_index.md

@@ -43,7 +43,7 @@ protecting sensitive data generated by the interaction of the user with the
 service.
 
 The policies that the service provider will have to accept are available in the
-[EGI Policies and procedures page](https://wiki.egi.eu/wiki/Policies_and_Procedures)
+[EGI Policies and procedures page](https://go.egi.eu/policies-and-procedures)
 and specifically are:
 
 1. [EGI Security Policy](https://documents.egi.eu/document/3015)
@@ -137,7 +137,7 @@ provide the following information to connect your service to EGI Check-in:
      encoded in base64
 1. Country of the service
 1. Compliance with the
-   [EGI Policies](https://wiki.egi.eu/wiki/Policies_and_Procedures) and the
+   [EGI Policies](https://go.egi.eu/policies-and-procedures) and the
    [GÉANT Data Protection Code of Conduct](https://wiki.refeds.org/display/CODE/Data+Protection+Code+of+Conduct+Home)
 
 The most important URLs for each environment are listed in the table below but

content/en/providers/cloud-compute/openstack/_index.md

@@ -23,8 +23,7 @@ outside your site:
 - Swift (if providing Object Storage)
 
 FedCloud components are distributed through
-[CMD (Cloud Middleware Distribution)](https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution)
-or docker container images available in [dockerhub](https://hub.docker.com/).
+[CMD (Cloud Middleware Distribution)](https://confluence.egi.eu/display/EGIBG/Cloud+Middleware+Distribution)
 These docker containers come pre-packaged and ready to use in the EGI FedCloud
 Appliance so you do not need to install any extra components on your site but
 just run a VM and configure it approprietely to interact with your services.
@@ -59,7 +58,7 @@ EGI distributes the integration components as:
 - A Virtual Appliance (VA) that uses Docker containers to bundle all of the
   components in a single VM and just needs minor configuration to get started
 - RPM and DEB Packages in the
-  [CMD distribution](https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution)
+  [CMD distribution](https://confluence.egi.eu/display/EGIBG/Cloud+Middleware+Distribution)
 
 ### FedCloud Virtual Appliance
 
@@ -68,18 +67,15 @@ The EGI FedCloud Appliance is available at
 as an OVA file. You can easily extract the VMDK disk by untaring and optionally
 converting it to your preferred format with qemu-img:
 
-<!-- markdownlint-disable line-length -->
-
 ```shell
 # get image and extract VMDK
-$ curl $(curl "https://appdb.egi.eu/store/vm/image/fc90d1aa-b0ae-46a0-b457-96f6f7a7d446:7875/json?strict" | jq -r .url) | \
-    tar x "*.vmdk"
+$ curl $(curl "https://appdb.egi.eu/store/vm/image/fc90d1aa-b0ae-46a0-b457-96f6f7a7d446:7875/json?strict" \
+    | jq -r .url) \
+    | tar x "*.vmdk"
 # convert to qcow2
 $ qemu-img convert -O qcow2 FedCloud-Appliance.Ubuntu.*.vmdk fedcloud-appliance.qcow2
 ```
 
-<!-- markdownlint-enable line-length -->
-
 The appliance running at your OpenStack must:
 
 - Have a host certificate to send the accounting information to the accounting

content/en/providers/getting-started/integration_checklist/_index.md

@@ -7,7 +7,7 @@ This page provides an overview of what are the required steps to get a new
 Resource Centre integrated into the EGI Federation.
 
 1. Be aware of the
-   [security policies](https://wiki.egi.eu/wiki/EGI_CSIRT:Policies).
+   [security policies](https://go.egi.eu/policies-and-procedures).
 
 1. Acceptance of the
    [RC OLA](https://documents.egi.eu/public/ShowDocument?docid=31) (agreed with
@@ -35,7 +35,7 @@ Resource Centre integrated into the EGI Federation.
 
 1. Security:
 
-   - HTC: [pakiti](https://wiki.egi.eu/wiki/EGI_CSIRT:Pakiti_client) is
+   - HTC: [pakiti](../../../internal/security-coordination/monitoring/pakiti) is
      installed and the outcome of the EGI CSIRT assessment is positive;
    - Cloud: the
      [EGI security Survey](https://www.surveymonkey.com/r/Cloud_Security_Questionnaire_for_Resource_Centres)
@@ -56,7 +56,7 @@ Resource Centre integrated into the EGI Federation.
    [Accounting Portal](https://accounting.egi.eu/).
 
    - Accounting probes and [APEL SSM](https://github.com/apel/ssm) are properlly
-   installed and configured:
+     installed and configured:
      - HTC: [APEL client](https://github.com/apel/apel)
      - Cloud: [cASO](https://github.com/IFCA/caso).
 
@@ -68,7 +68,10 @@ Resource Centre integrated into the EGI Federation.
      [added to the fedcloud-catchall-operations repository](../../cloud-compute/openstack/#catch-all-operations)
 
 1. Middleware: latest version of technology products are installed using the
-   [UMD/CMD release](https://wiki.egi.eu/wiki/Middleware).
+   [UMD](https://confluence.egi.eu/display/EGIBG/Unified+Middleware+Distribution)
+   and
+   [CMD](https://confluence.egi.eu/display/EGIBG/Cloud+Middleware+Distribution)
+   releases.
 
 1. Software distribution:
    - HTC (Optional): [CVMFS](https://github.com/cvmfs-contrib/egi-cvmfs)

content/en/providers/getting-started/operations_start_guide/_index.md

@@ -7,36 +7,37 @@ type: docs
 
 The Operations Start Guide will help you start with EGI Operations duties. It
 covers the responsibilities of the various parties involved in the running of
-the [EGI infrastructure](https://ims.egi.eu/display/EGIG/EGI+Infrastructure) and
-guide how to join operations. As a newcomer, you need to understand the
+the
+[EGI infrastructure](https://confluence.egi.eu/display/EGIG/EGI+Infrastructure)
+and guide how to join operations. As a newcomer, you need to understand the
 structure of the infrastructure and roles of operators at different levels.
 Reading the whole document will give you a complete overall picture of daily
 operations within EGI.
 
 ## Resource Centres and Resource Infrastructures
 
 Resources are geographically distributed and are contributed by
-[Resource Centres](https://ims.egi.eu/display/EGIG/Resource+Centre). A Resource
-Centre is the smallest resource administration domain within EGI. It can be
-either localized or geographically distributed. A Resource Centre is also known
-as a _site_. It provides a minimum set of local or remote IT Services, such as
-High Throughput Compute (HTC), Cloud Compute, Storage and Data Transfer,
+[Resource Centres](https://confluence.egi.eu/display/EGIG/Resource+Centre). A
+Resource Centre is the smallest resource administration domain within EGI. It
+can be either localized or geographically distributed. A Resource Centre is also
+known as a _site_. It provides a minimum set of local or remote IT Services,
+such as High Throughput Compute (HTC), Cloud Compute, Storage and Data Transfer,
 compliant to well-defined IT Capabilities necessary to make resources accessible
 to authorised users. Users can access the services using common interfaces.
 
 The EGI Federation is a
-[Resource Infrastructure](https://ims.egi.eu/display/EGIG/Resource+Infrastructure)
+[Resource Infrastructure](https://confluence.egi.eu/display/EGIG/Resource+Infrastructure)
 federating Resource Centres to constitute a homogeneous operational domain, and
 the
-[Resource Infrastructure Provider](https://ims.egi.eu/display/EGIG/Resource+Infrastructure+Provider)
+[Resource Infrastructure Provider](https://confluence.egi.eu/display/EGIG/Resource+Infrastructure+Provider)
 is the legal organisation that is responsible of establishing, managing and of
 operating directly or indirectly the operational services to an agreed level of
 quality needed by the Resource Centres and the user community. It holds the
 responsibility of integrating them in EGI to enable uniform resource access and
 sharing for the benefit of their consuming end users. Examples of a Resource
 infrastructure Provider are the
-[European Intergovernmental Research Organisations (EIRO)](https://ims.egi.eu/display/EGIG/European+Intergovernmental+Research+Organisation)
-and the [NGIs](https://ims.egi.eu/display/EGIG/NGI).
+[European Intergovernmental Research Organisations (EIRO)](https://confluence.egi.eu/display/EGIG/European+Intergovernmental+Research+Organisation)
+and the [NGIs](https://confluence.egi.eu/display/EGIG/NGI).
 
 In Europe, Resource Centres are required to be affiliated to the respective
 NGIs, which (a) have a mandate to represent their national users community in
@@ -102,7 +103,7 @@ operate supported middleware versions. This implies upgrading it regularly.
 Emergency releases are treated in a special way. Resource Centre Administrators
 **MUST** react to security issues that are at a global level, but affect their
 site. See
-[SEC03 EGI-CSIRT Critical Vulnerability Handling](https://wiki.egi.eu/wiki/SEC03_EGI-CSIRT_Critical_Vulnerability_Handling).
+[SEC03 EGI-CSIRT Critical Vulnerability Handling](https://go.egi.eu/sec03).
 
 #### Resource Centre Operations Manager
 
@@ -121,12 +122,12 @@ subscribed to the relevant mailing lists.
 #### Resource Centre Security Officer
 
 The person responsible for keeping the site compliant with the
-[EGI security policies](https://wiki.egi.eu/wiki/EGI_CSIRT:Policies). They are
-the primary contact for the [NGI Security officer](#ngi-security-officer) and
+[EGI security policies](https://go.egi.eu/policies-and-procedures). They are the
+primary contact for the [NGI Security officer](#ngi-security-officer) and
 [EGI Computer Security Incident Response Team (CSIRT)](#egi-csirt). The Site
 Security Officer deals with security incidents and shall respond to enquiries in
 a timely fashion as defined in the collection of
-[security procedures and policies](https://wiki.egi.eu/wiki/EGI_CSIRT:Policies).
+[security procedures and policies](https://go.egi.eu/policies-and-procedures).
 
 ### Regional level
 
@@ -200,7 +201,7 @@ coordinating the operations of the infrastructure across the project.
 contact point at project level.
 
 - [EGI-CSIRT site](https://csirt.egi.eu)
-- [EGI-CSIRT profile according to RFC-2350](https://wiki.egi.eu/wiki/EGI_CSIRT:RFC_2350)
+- [EGI-CSIRT profile according to RFC-2350](https://confluence.egi.eu/display/EGIBG/EGI+CSIRT+-+RFC+2350)
 - [EGI-CSIRT Terms of References](https://csirt.egi.eu/files/2020/11/EGI-CSIRT-ToR_V2_20190819.pdf)
 
 ##### EGI-CSIRT's IRTF
@@ -223,24 +224,23 @@ on a weekly rota basis.
 
 #### EGI Foundation SDIS team
 
-The [EGI Foundation](https://ims.egi.eu/display/EGIG/EGI+Foundation) Service
-Delivery and Information Security (SDIS) team, formerly known as the EGI
+The [EGI Foundation](https://confluence.egi.eu/display/EGIG/EGI+Foundation)
+Service Delivery and Information Security (SDIS) team, formerly known as the EGI
 Operations team, is responsible of
 [coordinating and supporting the operational activities](https://confluence.egi.eu/display/EGIPP/EGI+Infrastructure+operations+oversight)
 of all the EGI Infrastructure.
 
 #### VO
 
 A
-[Virtual Organisation (VO)](https://ims.egi.eu/display/EGIG/Virtual+organisation)
+[Virtual Organisation (VO)](https://confluence.egi.eu/display/EGIG/Virtual+organisation)
 is a group of users and, optionally, resources, often not bound to a single
 institution or national borders, who, by reason of their common membership and
 in sharing a common goal, are given authority to use a set of resources. Each VO
 member signs the VO Acceptable Usage Policy (AUP) (during registration) which is
 the policy describing the goals of the VO thereby defining the expected and
 acceptable use of the resources by the users of the VO. User documentation can
-be found [in the users section](../../../users/) and
-[in the EGI Wiki](https://wiki.egi.eu/wiki/User_Documentation).
+be found [in the users section](../../../users/).
 
 #### VO manager
 
@@ -281,7 +281,7 @@ Please use this resource and contact your CA if your certificate does not work.
 
 As soon as you try to access an EGI service with your federated identity, you
 will be requested to register an account in EGI Check-in if not existing yet.
-The [Check-in sign up guide](../../../users/check-in/signup/) explains how to
+The [Check-in sign up guide](../../../users/aai/check-in/signup) explains how to
 sign up for an EGI account. If you already own an account, you will be simply
 asked to login through EGI Check-in.
 
@@ -337,7 +337,7 @@ be subscribed to noc-managers mailing list `noc-managers@mailman.egi.eu`.
 Procedures and policies are accessible on the
 [EGI Policies and Procedures space](https://confluence.egi.eu/display/EGIPP/EGI+Federation+Procedures).
 Additional documentation relevant to EGI operations is available at
-[EGI Documentation wiki page](https://wiki.egi.eu/wiki/Documentation).
+[EGI Documentation wiki page](../../../../en)
 
 ## Tools
 

content/en/providers/operations-manuals/howto02_site_certification_required_documentation/_index.md

@@ -30,15 +30,13 @@ understood.
 - [PROC12 Production Service Decommissioning Procedure](https://confluence.egi.eu/display/EGIPP/PROC12+Production+Service+Decommissioning):
   Procedure document describing the steps required to decommission a production
   service.
-- [Helpdesk](../../../internal/helpdesk) and
-  [FAQs](https://wiki.egi.eu/wiki/GGUS:FAQ): A collection of documentation
-  relevant to the EGI Helpdesk (GGUS). The User Guide and FAQ for direct site
-  notification are probably the most helpful.
+- [Helpdesk](../../../internal/helpdesk): A collection of documentation
+  relevant to the EGI Helpdesk (GGUS).
 
 ## Tools
 
 - [Configuration Database (GOCDB)](../../../internal/configuration-database)
-- [Operations Portal](ttp://operations-portal.egi.eu)
+- [Operations Portal](https://operations-portal.egi.eu)
 - ARGO Monitoring:
   [RCs status](https://argo.egi.eu/egi/report-status/Critical/SITES),
   [A/R reports](https://argo.egi.eu/egi/report-ar/Critical/SITES): The ARGO

content/en/providers/operations-manuals/man02_service_intervention_management/_index.md

@@ -30,7 +30,7 @@ the planning of the outage, we have two types of intervention:
 Interventions are recorded through the
 [Configuration Database](../../../internal/configuration-database). For more
 information, have a look at the
-[description](https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Downtimes).
+[description](../../../internal/configuration-database/downtimes).
 
 ### Scheduled interventions
 

content/en/users/aai/check-in/vos/voms/_index.md

@@ -247,7 +247,7 @@ existing VOs
    **Again, this is usually guided by the EGI support team. You should already
    have a meeting with them to discuss your requirements. They will help you to
    get resources from EGI providers, and sign
-   [SLA](https://wiki.egi.eu/wiki/EGI_OLA_SLA_framework#Service_Level_Agreemens)
+   [SLA](https://confluence.egi.eu/display/EGISLM/EGI+OLA+SLA+framework)
    with you.**
 
 1. Request your VO membership at VO VOMS page. You will have to enter required

content/en/users/data/storage/block-storage/_index.md

@@ -64,11 +64,6 @@ of a provider, from a [command-line interface](#manage-from-the-command-line)
 (CLI), or via the
 [OpenStack Block Storage API](https://docs.openstack.org/api-ref/block-storage/).
 
-{{% alert title="Note" color="info" %}} Please refer to
-[OCCI How-To](https://wiki.egi.eu/wiki/HOWTO11_How_to_use_the_rOCCI_Client#How_to_create_block_storage.3F)
-for details about using the legacy OCCI interface to manage block storage.
-{{% /alert %}}
-
 ## Manage from the command-line
 
 Multiple command-line interfaces (CLIs) are available to manage block storage: