bring guide about new chaosknoten VMs into doc structure

docs/guides/create-a-new-vm-on-chaosknoten.md

@@ -1,18 +1,22 @@
 ---
-title: New Chaosknoten VM
+title: Create a new VM on Chaosknoten
-summary: How to Create a New VM on Chaosknoten
 ---
 
-# New Chaosknoten VM
+!!! success "Goal"
 
-This guide outlines the steps to take for creating a new VM (`myservice`) on Chaosknoten. It might also act as a useful reference for other environments however.
+    Create a new VM on our Chaosknoten Server with DNS Name, Firewalling and network config.
 
-## IP and DNS
+## 1. Reserve an IP Address
 
-Decide on what kind of network configuration the VM needs. In this guide we assume a public v6 and a non-public v4 in the v4-NAT network. If you have special requirements, refer to TODO for more information on the different kinds of networks available on Chaosknoten.  
+Decide on what kind of network configuration the VM needs.
+In this guide we assume a public v6 and a non-public v4 in the v4-NAT network.
+If you have special requirements, refer to TODO for more information on the different kinds of networks available on Chaosknoten.  
 
 1. Allocate a fresh [v6 in NetBox in the v4-NAT v6-network](https://netbox.hamburg.ccc.de/ipam/prefixes/47/ip-addresses/).
     - The _hostname_ should be the full FQDN, like: `myservice.hosts.hamburg.ccc.de`
+
+## 2. Configure DNS
+
 2. Add a new `AAAA` record pointing to the chosen v6 to the [`hamburg.ccc.de` zone](https://git.hamburg.ccc.de/CCCHH/ansible-infra/src/branch/main/resources/chaosknoten/auth-dns/zones/hamburg.ccc.de.zone).  
   It should look something like this:
   ```
@@ -23,7 +27,7 @@ Decide on what kind of network configuration the VM needs. In this guide we assu
   ansible-playbook -i inventories/chaosknoten playbooks/deploy.yaml -l auth-dns -t knot
   ```
 
-## VM Creation
+## 3. Create A VM in Proxmox
 
 Now that we have a v6, let's create a new VM on Chaosknoten.
 
@@ -49,6 +53,9 @@ Now that we have a v6, let's create a new VM on Chaosknoten.
       ```
       ssh -J chaos@router.hamburg.ccc.de chaos@myservice.hosts.hamburg.ccc.de
       ```
+
+## 4. Enter VM into NetBox
+
 4. Finally add the VM to NetBox
     1. First [add the VM itself](https://netbox.hamburg.ccc.de/virtualization/virtual-machines/).
         - The _Name_ should be the hostname of the VM, so e.g. `myservice`.
@@ -63,7 +70,7 @@ Now that we have a v6, let's create a new VM on Chaosknoten.
     4. Finally assign the IP address created earlier in NetBox to the just created interface by going into the _Assignment_ section of the IP address configuration.
         - Also check _Make this the primary IP for the device/VM_ while doing so.
 
-## Ansible
+## 5. Enroll the VM in ansible
 
 Next up the VM should be added to the Ansible configuration management. While Ansible can and should be used to configure various services and configuration options, this section focuses on the basic setup to be done.
 
@@ -88,7 +95,7 @@ Next up the VM should be added to the Ansible configuration management. While An
 
 Feel free to commit at this point before continuing with further configuration.
 
-## Further Setup
+## 6. Configure the VM further for your needs
 
 With the basic configuration now done, the VM can be set up further. Here are some helpful pointers:
 
@@ -96,4 +103,9 @@ With the basic configuration now done, the VM can be set up further. Here are so
 - Secrets should be stored using SOPS, see: [SOPS: Storing Secrets](./sops-storing-secrets.md)
 - Guidance on setting up a web service can be found in the [Web Service](./web-service.md) guide.
 
-Afterward you should also take care of setting up monitoring for the newly configured service, see: [Monitoring: Gatus](./monitoring-gatus.md)
+Afterward you should also take care of setting up monitoring for the newly configured service, see: [Monitor a new service with Gatus](./monitor-a-new-service-with-gatus.md).
+
+## Closing Up
+
+This section is optional but if there's any way for the reader to verify their goal has been achieved, you should mention it here.
+