From c30348c3af3a11d32fdf10854d09d002f97ca491 Mon Sep 17 00:00:00 2001 From: Max Wolfs Date: Tue, 26 Nov 2024 13:34:13 +0100 Subject: [PATCH] fix md errors Signed-off-by: Max Wolfs --- docs/turnkey-solution/hardware-landscape.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/turnkey-solution/hardware-landscape.md b/docs/turnkey-solution/hardware-landscape.md index 3338659cb9..5fcd557108 100644 --- a/docs/turnkey-solution/hardware-landscape.md +++ b/docs/turnkey-solution/hardware-landscape.md @@ -5,7 +5,7 @@ sidebar_position: 99 # The SCS Hardware-Landscape -![An image of the SCS hardware landscape rack](images/combined_rack_visual.jpg "The SCS hardware landscape rack"){width=500px} +![An image of the SCS hardware landscape rack](images/combined_rack_visual.jpg) ## General information @@ -69,7 +69,7 @@ The relevant **References** section refers here to the individual documentation adjustments and further developments are managed via GIT merge requests * Almost all installation steps are [documented and automated](https://github.com/SovereignCloudStack/hardware-landscape/blob/main/documentation/System_Deployment.md) based on a pure rack installation (The setup is extensively documented, in particular the few manual steps) - * The entire customized setup of the nodes is [implemented by OSISM/Ansible] + * The entire customized setup of the nodes is [implemented by OSISM/Ansible](https://github.com/SovereignCloudStack/hardware-landscape/tree/main/environments/custom) * All secrets (e.g. passwords) of the environment are stored and versioned in the encrypted Ansible Vault in i the repository (when access is transferred, rekeying can be used to change the access or the rights to it). * A far-reaching or in-depth automation has been created that allows the environment to be re-set up or parts of it to