nicolas
/
www.itix.fr
mirror of https://github.com/nmasse-itix/www.itix.fr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
Browse Source

internal links with custom title

pull/10/head
Nicolas Massé 1 year ago
parent
4f95fbe558
commit
78c05e788b
4 changed files with 7 additions and 7 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 4
      content/english/blog/deploy-openshift-single-node-in-kvm/index.md
  2. 4
      content/english/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md
  3. 4
      content/french/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md
  4. 2
      themes/itix

4
content/english/blog/deploy-openshift-single-node-in-kvm/index.md
View File

@ -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]({{<relref "/blog/consistent-dns-name-resolution-for-virtual-machines-and-containers/index.md" >}}) for DNS resolution.
Configure {{<internalLink path="/blog/consistent-dns-name-resolution-for-virtual-machines-and-containers/index.md" title="NetworkManager to use dnsmasq" >}} 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]({{<relref "/blog/consistent-dns-name-resolution-for-virtual-machines-and-containers/index.md" >}}), you should be able to reach your OpenShift node by its DNS name.
If you configured NetworkManager and dnsmasq {{<internalLink path="/blog/consistent-dns-name-resolution-for-virtual-machines-and-containers/index.md" title="as explained here" >}}, you should be able to reach your OpenShift node by its DNS name.
Otherwise, use the IP address.
```sh

4
content/english/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md
View File

@ -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 {{<internalLink path="/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8" title="CentOS Stream router" >}} into a VM without performance loss.
To sum up, I need :

4
content/french/blog/homelab-server-2u-short-depth-front-io-ampere-altra-arm64-architecture/index.md
View File

@ -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]({{<relref "/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8" >}}) 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]({{<relref "/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8" >}}) dans une VM sans perte de performance.
La fonction SR-IOV me permettrait de mettre le {{<internalLink path="/blog/fibre-orange-remplacer-livebox-routeur-centos-stream-8" title="routeur CentOS Stream" >}} dans une VM sans perte de performance.
En résumé, j'ai besoin de :

2
themes/itix

@ -1 +1 @@
Subproject commit 73e219f309127a387fdf7580ac2ef2aac03bd23a
Subproject commit 18ab2a17245f97f2ba7b0b477e79ff9afd7e51a3
Write Preview
Loading…
Cancel
Save