From 78c05e788be367698d1337fdf5a350ff62b2163c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicolas=20Mass=C3=A9?= Date: Fri, 12 Jul 2024 16:59:18 +0200 Subject: [PATCH] internal links with custom title --- .../english/blog/deploy-openshift-single-node-in-kvm/index.md | 4 ++-- .../index.md | 4 ++-- .../index.md | 4 ++-- themes/itix | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/english/blog/deploy-openshift-single-node-in-kvm/index.md b/content/english/blog/deploy-openshift-single-node-in-kvm/index.md index 467ef7c..75bd519 100644 --- a/content/english/blog/deploy-openshift-single-node-in-kvm/index.md +++ b/content/english/blog/deploy-openshift-single-node-in-kvm/index.md @@ -21,7 +21,7 @@ This article explores how to deploy OpenShift Single Node (SNO) using KVM on you On your Fedora workstation, make sure you installed the required packages [as explained in the Fedora documentation](https://docs.fedoraproject.org/en-US/quick-docs/getting-started-with-virtualization/). -Configure [NetworkManager to use dnsmasq]({{}}) for DNS resolution. +Configure {{}} for DNS resolution. Choose a base domain name and a cluster name. The base domain does not need to be public or registered somewhere. @@ -143,7 +143,7 @@ Once the installation is complete, download the **kubeadmin** password and make {{< attachedFigure src="assisted-installer-5.png" title="Assisted Installer: the installation is complete." >}} Also, make sure you can login with SSH to your OpenShift node. -If you configured NetworkManager and dnsmasq [as explained here]({{}}), you should be able to reach your OpenShift node by its DNS name. +If you configured NetworkManager and dnsmasq {{}}, you should be able to reach your OpenShift node by its DNS name. Otherwise, use the IP address. ```sh diff --git a/content/english/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md b/content/english/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md index 8f5cc9b..0d29d43 100644 --- a/content/english/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md +++ b/content/english/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md @@ -35,7 +35,7 @@ This **HP DL20 Gen9** server is equipped with : {{< attachedFigure src="hp-dl20-gen9.webp" title="The existing HP DL20 Gen9 server." >}} -This server is currently racked in a 7U, short depth IT rack in the basement of the house and is currently running **CentOS Stream 8** which I have configured as a [router](/fr/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8) and hypervisor (with **libvirt**). +This server is currently racked in a 7U, short depth IT rack in the basement of the house and is currently running **CentOS Stream 8** which I have configured as a router (see {{< internalLink path="/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8" >}}) and hypervisor (with **libvirt**). The hypervisor runs several VMs: @@ -68,7 +68,7 @@ The expansion capabilities of the **HP DL20 Gen9** are quite limited: 2 PCIe x8 The full-height slot is taken by the RAID controller and the half-height slot is taken by the 4-port GbE network card. Last but not least, the motherboard and CPU of the **HP DL20 Gen9** do not support **SR-IOV**. This currently forces me to run network routing functions directly on the hypervisor. -SR-IOV would allow me to put the [CentOS Stream router](/fr/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8) into a VM without performance loss. +SR-IOV would allow me to put the {{}} into a VM without performance loss. To sum up, I need : diff --git a/content/french/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md b/content/french/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md index 5240f98..3825ac7 100644 --- a/content/french/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md +++ b/content/french/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md @@ -35,7 +35,7 @@ Ce serveur **HP DL20 Gen9** est équipé de : {{< attachedFigure src="hp-dl20-gen9.webp" title="Le serveur HP DL20 Gen9 existant." >}} -Ce serveur est actuellement racké dans une baie informatique de 7U de haut, faible profondeur, au sous-sol de la maison et il fait actuellement tourner **CentOS Stream 8** que j'ai configuré en [routeur]({{}}) et hyperviseur (avec **libvirt**). +Ce serveur est actuellement racké dans une baie informatique de 7U de haut, faible profondeur, au sous-sol de la maison et il fait actuellement tourner **CentOS Stream 8** que j'ai configuré en routeur (voir {{< internalLink path="/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8" >}}) et hyperviseur (avec **libvirt**). L'hyperviseur fait tourner plusieurs VM : @@ -68,7 +68,7 @@ Les capacités d'expansion du **HP DL20 Gen9** sont bien limitées : 2 emplaceme L'emplacement pleine hauteur est pris par le contrôleur RAID et l'emplacement demi hauteur est pris par la carte réseau 4 ports GbE. Dernier point, et non des moindres, la carte mère et le CPU du **HP DL20 Gen9** ne supportent pas le **SR-IOV**. Ça m'oblige actuellement à faire tourner les fonctions de routage réseau directement sur l'hyperviseur. -La fonction SR-IOV me permettrait de mettre le [routeur CentOS Stream]({{}}) dans une VM sans perte de performance. +La fonction SR-IOV me permettrait de mettre le {{}} dans une VM sans perte de performance. En résumé, j'ai besoin de : diff --git a/themes/itix b/themes/itix index 73e219f..18ab2a1 160000 --- a/themes/itix +++ b/themes/itix @@ -1 +1 @@ -Subproject commit 73e219f309127a387fdf7580ac2ef2aac03bd23a +Subproject commit 18ab2a17245f97f2ba7b0b477e79ff9afd7e51a3